Last_update_datetime Is Not Updating On ITEM_LOC For Stores
(Doc ID 3062463.1)
Last updated on DECEMBER 06, 2024
Applies to:
Oracle Retail Merchandising System - Version 16.0.3 to 16.0.3 [Release 16.0]Information in this document applies to any platform.
Symptoms
On : 16.0.3 version, Other
Last_update_datetime is not updating on ITEM_LOC for stores
When primary_cost_pack is updated at wh from RMS application for a component, it's being copied to the stores sourced by the same wh for the corresponding component but last_update_datetime is not being updated at item/store record though there is a change in primary_cost_pack field. Last_update_datetime is being updated at item/wh.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Identify a component item ranged to a WH
2. Check the last_update_datetime in item_loc for for the component at stores source by the WH
3. On RMS application, go to “item locations” screen.
4. Change the primary_cost_pack to a different pack and click “save and close”
5. Now go to item_loc for the item/wh record, we can observe new primary_cost_pack, last_update_datetime and last_update_id are updated
6. At stores source by the wh for the same item, we can the new primary_cost_pack updated but last_update_datetime is not changed.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot of any update being made to item, wrt primary_cost_pack.
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 |
Cause |
Solution |
References |