Oracle Projects Invoice Flow

This article gives a basic understanding of the Oracle Projects Invoice Flow: Oracle Projects Invoice Flow: Below are Steps that needs to be followed for successfully creating a Projects Invoice and interfacing it to Oracle Receivables. 1. Creation of Contract Project (Mandatory) 2. Assign a Customer for the Project (Mandatory) 3. Create an Agreement with the Customer (Mandatory) 4. Fund the Project through the Customer Agreement (Mandatory) 5. Create an Approved Revenue Budget for the Project (optional). 6. Baseline the Funding (Mandatory). 7. Generate Draft Revenue (Optional). 8. Generate Draft Invoice (Mandatory). 9. Approve and Release the Draft Invoice (Mandatory). 10. Interface Draft Invoices to Oracle Receivables. (Mandatory) 11. Tieback invoices back to Oracle Projects. (Mandatory).

1. Creation of Contract Project: Create a Project of 'Contract' Project Type. Only Contract Projects can be associated with a Customer. Create WBS Structure for the Project. Identify the Project Manager. Assign Team members if needed. Tech info: Tables/Views involved: PA_PROJECTS_ALL - Projects Table

the customer cannot be billed past the funded amount in the agreement for that project. Tech info: Tables/Views involved: PA_AGREEMENTS_ALL . 2. This can be done using the Agreements Form. Similarly if the Hard Limit is set for the invoice. If the Hard Limit is set for Revenue. Create an Agreement for the Customer: A Funding Agreement needs to be created for the Customer with the Terms and the Agreement Amount. If a customer agreement already exists for this customer. Here you can specify the 'Hard Limts' . 4. Assign a Customer for the Project: Assign a Customer to the Project and the 'Bill to ' Address for the customer. you can use the same agreement to fund this project. Revenue cannot be generated past the funded amount for the project. Tech info: Tables/Views involved: PA_PROJECT_CUSTOMERS .Agreement Header Information.Tasks Associated with the Projects (WBS Information) PA_PROJECT_PLAYERS . so that the customer can be billed. Fund the Project through the Customer Agreement: Fund the Project using the Customer agreement created in Step 4.Contains the Key Member Assoications with the Project including the Project managers.Project Types Information PA_TASKS . . This can be done using the Fundings Section in the Agreement Form.PA_PROJECT_TYPES .Projects-Customers Association 3. Also you can assign Billing and Shipping Contacts for the Customer in the Customers Options in the Projects Form.

this step is mandatory. Oracle Projects creates an internal Approved Revenue Budget with the budget amount equal to the Funding amount and baselines both the Budget and Funding. then an approved revenue budget for the project has to be created with the funding amount. 7. Create an Approved Revenue Budget for the Project: This Step is optional. baselines the funding automatically.Project Funding Information.Line level details. Generate Draft Revenue: This step is optional depending on the Distribution Rule for the invoice. Baselining this budget. If revenue needs to be generated for multiple projects. If the invoice distribution rule is WORK.Budget header info PA_BUDGET_LINES : Budget Line level info 6. if the 'Baseline Funding without Budget' option is set at the Project level. Tech info: Tables/Views involved: PA_BUDGET_VERSIONS .Revenue Header info PA_DRAFT_REVENUE_ITEMS .Tech info: Tables/Views involved: PA_SUMMARY_PROJECT_FUNDINGS . If this option is not set. The process "PRC: Generate Draft Revenue for a single Project" is run for the Project. Baseline the Funding: If 'Baseline Funding without Budget' is set then the funding can be baselined without the Approved Revenue Budget. 5. run the "PRC: Generate Draft Revenue for range of Projects" process giving the Project Number ranges. Tech info: Tables/Views involved: PA_DRAFT_REVENUES_ALL . .

Approve and Release the Draft Invoice: The invoices needs to be approved and released in order to interface them to AR. If you want to generate invoices for multiple projects. Tech info: Tables/Views involved: PA_DRAFT_INVOICES_ALL . 10. Generate Draft Invoice: Run the Process "PRC:Generate Draft Invoice for a single Project". in AR. the " Autoinvoice import"process need to be run so that it will create AR invoices from the interface records. Tech info: Tables/Views involved: RA_INTERFACE_LINES_ALL 11.Revenue distribution lines for the Expenditure items PA_CUST_EVENT_RDL_ALL . approve and release it. Once this process is run. The approval workflow can also be customized to have a multi-level approval mechanism. Generally an invoice accountant will review the invoice. Tieback invoices back to Oracle Projects . run "PRC: Generate Draft Invoice for a range of Projects" giving the Project number ranges.Draft invoice header information PA_DRAFT_INVOICE_ITEMS . This process will populate the AR interface table. This will generate draft invoices only for that project. But it all depends on the business scenario.Revenue distribution lines for the events 8. Alternatively the Automatic Approval and release client extension can be used to automatically approve and release the invoices.Item level information 9. giving the Project number as parameter. This can be done in the Invoice Review Form.PA_CUST_REV_DIST_LINES_ALL . Interface Draft Invoices to Oracle Receivables Run the "PRC: Interface invoices to Receivables" process in order to interface the released projects invoices to AR.

Once the Autoinvoice import is successfully run. the "PRC: Tieback Invoices from Receivables" process is run to update the status of the invoice import in AR to the Projects Invoices .

Sign up to vote on this title
UsefulNot useful