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.

You can use the default row 10. This will populate the correct header row automatically on validation/upload.

Blanket/Contract 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

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

Purchase Requisitions

Download only returns requisitions that I have prepared.

This is the default security. If you wish to see other requisitions, then you need the aggregate privilege Requisition Management Using REST Service (ORA_POR_USE_REST_SERVICE_MANAGE)

Purchase Requisitions

Download returns no records.

If you do not have the privilege to view others requisitions and you have not prepared any requisitions, then your download will be empty.

Expected Shipments/
Receiving Transactions

Import error:
'QUANTITY: RCV_SHIP_QTY_OVER_TOLERANCE: You must enter a quantity that’s less than the tolerance quantity of xxx. The current quantity entered is xxx.

This error message indicates that the quantity you are trying to receive for an item is too high and exceeds the defined receiving tolerance.
Resolve:
* Correct the quantity. If the quantity you entered was a mistake, simply change it to the correct quantity using the Update action.
* Adjust the tolerance: If the quantity you are receiving is correct and you need to receive this much, you’ll need to adjust the receiving tolerance settings. This is typically done by a Procurement Administrator.
* Create a New Purchase Order: In some cases, if the quantity received is a significant increase from the original order, the correct business process might be to create a change order on the existing purchase order or a new purchase order altogether to reflect the new, larger quantity.

Expected Shipments/
Receiving Transactions

Import error:
'INTERFACE_TRANSACTION_ID: RCV_SPLIT_LOT_SERIAL_ERROR: The lot or serial number lines couldn’t be split. See the inventory log for more details. Generally, this indicates an issue during a receiving transaction where the system is unable to correctly process or allocate quantities of items that are controlled by lot numbers or serial numbers.

Common Causes:
Quantity Mismatch:
Serial Controlled Items: You might be trying to receive a quantity of serial-controlled items, but the number of serial numbers provided doesn’t match the quantity being received. For example, if you’re receiving 5 units of a serial-controlled item, but only provide 3 serial numbers, or provide 7.

Lot Controlled Items: Similar to serial numbers, there might be an issue with how the received quantity is being associated with the lot numbers. For instance, if you’re trying to receive 10 units into two lots, but the sum of quantities for those lots doesn’t equal 10.

Invalid Lot/Serial Numbers: The lot or serial numbers being provided might not conform to the defined format or existing records.

Attempting to use a serial number that is already associated with another item or shipment.