Please note the below flow is for 11i
PA – AP Flow:
Here iam considering the AP invoice integration with Oracle Projects. I will explain about the Expense Reports flow in another topic.
This integration involves 2 sub processes given below:
- Interfacing Supplier Invoice From Oracle Payables To Oracle Projects
- Interfacing Supplier Invoice Adjustments From Oracle Projects To Oracle Payables
Interfacing Supplier Invoice From Oracle Payables To Oracle Projects:
This process involves :
- Creating the invoice.
- Approve the invoice.
- Account for the invoice in payables.
- Run the ‘Interface Supplier Costs’ process in Oracle Projects which interfaces the invoices from AP to PA.
Interfacing Supplier Invoice Adjustments From Oracle Projects To Oracle Payables:
This process involves:
- Adjust the supplier invoice interfaced to Oracle Projects by either splitting the quantity or transferring an invoice from one project/task to another.
- Execute the PRC: Distribute Supplier Invoice Adjustment Costs process in Oracle Projects.
- Run the PRC: Interface Supplier Invoice Adjustment Costs to Payables process in Oracle Projects.
Important Project Related Fields in AP:
- Project Name – Project Name to which the Invoice is accounted in Payables.
- Task Number – Task Number of the Project to which the invoice is accounted. Note: If the Task is not chargeable, the system displays the following error message: APP-PA-19270 The Task is Not Chargeable. The same error will be received if the Chargeable Flag is not checked while defining Tasks in Projects Setup or if the task is a Parent Task. Expenditures cannot be created at the Parent Task level.
- Expenditure Types – Expenditure Type of the invoice. This is based on the projects expenditure types (pa_expenditure_types table)
- Expenditure Item Date – The date of the invoice expenditure item to be created in Projects.
- Expenditure Organization – Active Project Expenditure/Event Organization against which the invoice has to be mapped.
The Expenditure Org can be find in PA_ALL_Organizations table with pa_org_use_type = ‘EXPENDITURES’. For any organization to be a Expenditure Organization, it has to be classified in HR as ‘Expenditure/Event Organization’.
- Quantity – Based on the Expenditure Type definition, quantity is verified by checking the PA_QUANTITY column in the AP_INVOICE_DISTRIBUTIONS_ALL. If the COST_RATE_FLAG column in PA_EXPENDITURE_TYPES table is set to Y, then the quantity field in the Payables Invoice Workbench needs to be filled in.
Once all the requisite information has been entered and the invoice distribution saved, the system checks whether the values given in the Project, Task, Expenditure Type and Expenditure Organization fields are active as of the Expenditure Item Date.
The following columns in the AP_INVOICE_DISTRIBUTIONS_ALL table are relevant for project-related supplier invoices:
- PROJECT_ACCOUNTING_CONTEXT – This column is set to Yes if the Project ID column is filled.
- ASSET_ADDITION_FLAG – If the project-related invoice distribution is charged to a Capital Project, then the ASSET_ADDITION_FLAG is set to P when the PA_ADDITION_FLAG is set to Y, Z or T.
To avoid the same invoice distribution being interfaced to both Projects and Fixed Assets, you must interface any project-related invoice distribution to Oracle Projects before you interface it to Oracle Assets.
- PA_ADDITION_FLAG- The PA_ADDITION_FLAG tracks the status of project-related supplier invoice distribution lines and expense report distribution lines. For supplier invoice distributions entered via Oracle Payables, the PA_ADDITION_FLAG is set to N if the distribution is project-related, otherwise it is set to E and it is updated by Oracle Projects when the distribution is processed by the Oracle Projects Interface Supplier Invoice process. Oracle Projects sets the PA_ADDITION_FLAG to Y or Z after the item is successfully processed, or may be set to a rejection code if the line is rejected during transfer to Projects. For supplier invoice adjustment lines interfaced from Projects to Payables (which must net to zero with another line), the value for the PA_ADDITION_FLAG is set to T. Listed below are the Quick Codes available for the PA_ADDITION_FLAG:
- B No open PA period
- C Task does not allow charges
- D Outside project dates
- E Non-project related invoice distributions
- I Outside task dates
- J Project level transaction controls violated
- K Task level transaction controls violated
- M Invalid project/task combination
- N New line not yet processed by Oracle Projects
- P Project is closed
- Q Transaction control extension violated
- S Temporary status used during processing
- T Adjustment line transferred from Oracle Projects
- V Invalid data (catch-all error)
- X Burdening error
- Y Transferred to Oracle Projects
- Z Net zero adjustment line. Never transferred to PA
If an item is rejected, you must correct the rejection reason and re-run the interface process.
- Once the Invoice is interfaced to Projects, the following tables are populated with appropriate values:
The interrelationship between the relevant Payables and Projects tables are as follows:
It is possible to map between the TRANSFER_STATUS_CODE column in the PA_COST_DISTRIBUTION_LINES_ALL table and the PA_ADDITION_FLAG column in the AP_INVOICE_DISTRIBUTIONS_ALL table. TRANSFER_STATUS_CODEs available in the PA_COST_DISTRIBUTION_LINES_ALL table for supplier invoices are:
- V- Interface from Oracle Payables – Upon creation set to Received
- P – Pending – Upon execution of Distribute Cost Process after Supplier Invoice Adjustments
- G – If payables rules do not allow adjustments to the invoice (example: if the invoice is cancelled), then distribute supplier invoice adjustments program would create the CDL and set the value to (G), these lines will always reside in Oracle Projects and will not be transferred to Oracle Payables
- A – Transfer Costs – If successfully transferred to Oracle Payables, set to Accepted
- X – Rejected in transfer to Oracle Payables, set to Rejected in Transfer