Procurement Module Troubleshooting
The following issues relate to unexpected results in Oracle ERP Cloud after uploading using the More4apps Integrators:
|
Integrator(s)
|
Issue
|
Detail
|
|
Standard Purchase Orders
|
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’.
|
|
Standard Purchase Orders
|
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 Orders
|
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.
|
|
Standard Purchase Orders
|
User does not have access to Approve purchase orders
|
Ensure the user has the Import Purchasing Document Bypassing Approval Oracle privilege.
|
|
Cancel Purchase Orders
|
Cancelled Order Status remains ‘Open’
|
The change order created may not have been submitted or may still be in the approval process. 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.
|
|
Purchase Requisitions
|
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.
|
|
Blanket Purchase Agreements
|
During an Action Update the Refresh process returns the Import error PO_POWS_NO_UPDATE_PENDING_CO: You can't perform this action because a pending change order exists, is returned.
|
This indicated that there is already a change order on the Agreement that needs to be approved or deleted before you can process the integrators change. This must be done in the UI manually. Then you will need to reload the update from the beginning. e.g. remove id’s from interface_header_id, interface_line_id, Interface_line_location_id, interface_Item_attribute id
|
