Oracle Procurement Troubleshooting
The following issues relate to unexpected results in Oracle ERP Cloud after uploading using the More4Apps Integrators:
|
Issue
|
Detail
|
|
Purchase Order has ‘Incomplete’ status in Oracle.
|
The purchase order quantities do not match the lines, schedules, and distributions.
A Charge Account has not been provided.
Project Details have not been provided.
The Approval Action was set to ‘Do Not Approve’.
|
|
Purchase Order has ‘Pending Approval’ status in Oracle.
|
Check the Approval Action in the sheet was set accordingly.
Options include:
Bypass Approval - Submits the purchase order automatically.
Do Not Approve - Sets the purchase order to Incomplete.
Submit for Approval - Will submit the purchase order as Pending Approval.
The approval process may still be running. Try again later.
|
|
Standard Purchase Order Change Order from update not appearing in Oracle
|
Approval action set to ‘Bypass Approval’. The change order will apply to the PO and no Change Order number will be in Oracle Cloud.
|
|
User does not have access to Approve purchase orders
|
Ensure the user has the Import Purchasing Document Bypassing Approval Oracle privilege.
|
|
Cancelled Order Status remains ‘Open’
|
The change order created may not have been submitted. This can occur based on the configuration of the change order processes in Oracle. Check the change order in the Oracle UI to see why the order was not submitted or failed.
|
|
Get an “orphaned” type error like ““Section xxx record in row xx is orphaned. Possible causes include a missing parent record or blank row gaps(s) above the current record”.
|
The integrator was expecting just a header level field rather than one for each line. This is applicable to the requisition columns Generate Tax and Accounting and Submit for Approval. The solution is to ensure that you only have a Yes on the header row.
Note: you can use the default row 10. This will populate the correct header row automatically on validation/upload.
|
|
Our setup allows for Touchless PO creation, and we use BPA/CPA’s. Why does my requisition line not match a BPA line/CPA?
|
The BPA match occurs during submit for approval, has the requisition line been approved?
Have you downloaded the requisition after creation? The Source Agreement and PO fields are only downloaded after creation.
Does the line have the correct supplier item, description, and category to match exactly to the BPA line?
You can run the diagnostics test “Touchless PO Creation” in cloud to ascertain the reason it was not matched to a BPA/CPA
|
