Skip to main content

Contract Projects Lifce Cycle

Contract Projects Lifce Cycle

Oracle Projects comes with 3 basic type of projects namely Indirect, Capital and Contract Projects. Here we will look at the Contract Projects.
Contract Projects are typically used in the Professional Services industry wherein the Vendor provides services to the end clients. Vendor invoices the clients and recognizes the revenue.
Create a Contract Project in Oracle Projects for the Customer
Contract Projects are Client Facing Projects wherein the both the parties ( Vendor and the Client) agree on certain terms and sign the contract. This contract is the basis for the Project. In Projects Module we create a Project of the Contract Project type for a particular customer.
Create an Agreement for the Project Customer
After the Contract Project is created, we will need to create an Agreement for the customer with the agreed upon amount and terms.
Fund the Project using the Client Agreement
Once the agreement is created in the system, using the agreement we need to fund the Contract Project. Note that one agreement can fund multiple projects. Typically when a Client has multiple projects going on with the same vendor. The funding created is in draft mode and has to be baselined.
Revenue Recognition
Revenue First and Bill Next
In Some companies, the revenue is recognized as and when needed irrespective of whether the customer has been invoiced or not. In those cases, we generate revenue and interface it to GL ( this is what it means revenue recognition).
Process Flow:
Generate Revenue -> Review Revenue -> Release Revenue -> Interface Revenue to GL -> Generate Invoice -> Approve/Release Invoice -> Interface Invoice to AR -> In AR, run Auto Invoice Import -> In Projects, Run the Tieback Invoice Process.
 Bill First and Revenue Next
In some companies, the revenue is not recognized until the customer has been billed. In this case, the invoice will be generated first and send to AR. Then the revenue is generated. To achieve this we will need to create Automatic Revenue Events for the interfaced billed amount. This can be done using Projects Billing Extensions ( for more info, check out the Projects interface/Client Extensions Guide).
Process Flow:
Generate Invoice -> Approve/Release Invoice -> Interface Invoice to AR -> In AR, run Auto Invoice Import -> In Projects, Run the Tieback Invoice Process -> Generate Revenue -> Review and Release Revenue -> Interface Revenue to GL
Ok, now its quiz time!
Contract Projects are Client facing projects. These projects generate revenue and bill the customers.
Invoices generated in Oracle projects are interfaced to AR. From AR it is sent to the customers.
It is generating revenue for a project and then interface the revenue to GL.

Comments

  1. Oracle Apps R12 and Fusion Cloud Self Paced Training Videos by Industry Experts. Please Check https://www.oracleappstechnical.com

    ReplyDelete

Post a Comment

Popular posts from this blog

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...

Public API’s for FA Transactions

Public API’s for FA Transactions So far Oracle FA is have all the good things except the lack on reporting.Oracle FA is now offer lot of public API's that can be used to interfacing with third party or Oracle application other modules. Here are some of transaction's API's:   Additions API if you have requirement to add assets directly via PL/SQL then use  FA_ADDITION_PUB.DO_ADDITION. If you have selected the Allow CIP Assets check box on the Book Controls window of a tax book when adding CIP assets using the Additions API, the this API automatically adds those CIP assets to that tax book at the same time that they are added to the corporate book. Adjustments API you can make cost adjustments to your assetsdirectly via PL/SQL using  FA_ADJUSTMENT_PUB.DO_ADJUSTMENT  for any  process adjustment. Detail can be found in appendix H) You can use this API if you have a custom interface that makes it difficult to use with the existing Oracle Assets interfaces for adjusti...

AP Table Relation Oracle Apps

AP Table Relation Oracle Apps ORACLE PAYABLE TABLE RELATION Source Table Dependent Table Condition AP_INVOICE_LINES_ALL AIL ZX_LINES_SUMMARY ZLS AIL.invoice_id = ZLS.trx_id and  ZLS.application_id  = 200 and  ZLS.entity_code  = 'AP_INVOICES' and  ZLS.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.summary_tax_line_id = ZLS.summary_tax_line_id AP_INVOICE_LINES_ALL AIL ZX_LINES ZL AIL.invoice_id = ZL.trx_id and  ZL.application_id  = 200 and  ZL.entity_code  = 'AP_INVOICES' and  ZL.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.line_number = ZL.trx_line_number AP_INVOICE_DISTRIBUTIONS_ALL AID ZX_REC_NREC_DIST ZD AID.invoice_id = ZD.trx_id and  ZD.application_id  = 200 and  ZD.entity_code  = 'AP_INVOICES' and  ZD.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and...