Updating the Primary Supplier Using the API Does Not Update the Unit Cost in Item Location
(Doc ID 2986918.1)
Last updated on NOVEMBER 14, 2023
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 23.1 to 23.1 [Release 23.1]Information in this document applies to any platform.
Symptoms
Actual Behavior
---------------
User is using a custom Apex solution that submits item-location updates via an API call (PUT /services/item/locations/update), but it does not update the unit_cost of the item in item_loc_soh. When using the UI for updating the primary supplier, the unit cost gets updated.
Expected Behavior
-----------------------
Web Service should behave the same as the UI and update the UNIT_COST
Steps to Reproduce
-----------------------
The issue can be reproduced at will with the following steps:
1) Using an item that is sourced from multiple suppliers with different costs, call Item Location Update (PUT /services/item/locations/update) to update primary supplier.
2) Validate that the primary supplier has been updated. -- this is working.
3) Validated that the unit cost of the item location has been updated to the cost for the new primary supplier (item-supp-country or item-supp-country-loc if available). - this is the failure.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |