In Change API, Secondary Quantity Is Not Updated Correctly (Doc ID 2071909.1)

Last updated on JUNE 01, 2016

Applies to:

Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Purchasing Processes

ACTUAL BEHAVIOR
---------------
For an item setup with 'Default' for the Defaulting (Dual Control) attribute, when the quantity and secondary quantity of the SHIPMENT are updated using the PO_CHANGE_API1_S.update_po, the passed in secondary quantity is not updated at the line level. Instead the secondary quantity at the line level gets calculated based on the Unit of Measure (UOM) conversion setup.

Similarly for the same item, when the quantity and secondary quantity of the LINE are updated using the PO_CHANGE_API1_S.update_po, the passed in secondary quantity is not updated at the shipment level. Instead the secondary quantity at the shipment level gets calculated based on the UOM conversion setup.

EXPECTED BEHAVIOR
-----------------------
Expect the passed in secondary quantity be updated at the shipment and line level. The secondary quantities of the line and shipment should be equal after the update.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Setup an Item with 'Default' defaulting (dual control) and secondary uom
2. Create PO
3. Update PO using PO_CHANGE_API1_S.update_po

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
If quantities on PO Line and PO Shipment don't match then PO never gets closed after invoicing. This requires manual work from the business team and they are spending lot of time manually updating it from front end.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms