Repl Attribute Maintenance Screen Deletes The Deactivate Date Column When The Activate Date Is Modified
(Doc ID 2344745.1)
Last updated on JULY 15, 2020
Applies to:
Oracle Retail Merchandising System - Version 14.0.3 and laterInformation in this document applies to any platform.
Symptoms
A replenishment mass item update for items with a deactivate_date set due to a clearance price change nulls out the deactivate_date if the new activate_date is past the deactivate_date.
This allows the replenishment system to generate orders for items that are on clearance (clear_ind in item_loc = 'Y').
Steps to reproduce :
1.Identify 2 items/loc in Repl_item_loc where Clear_ind in item_loc = ‘N’ and deactivate date is null.
2.Create a clearance for this item/loc with start_date as vdate.
3.Verify the deactivate date is populated in Rpm_item_loc and clear_ind for the item/loc in the ITEM_LOC table is updated.
4.Create a skulist for these two items.
5.Navigate to RMS ---Items --> Replenishment --->Replenishment Scheduled update screen.
6.Select all stores and provide the skulist that is created and update with the new activate date.
7.Verify the REPL_ATTR_UPDATE_HEAD table.
8.Run the replenishment batch RPLATUPD
prepost $UP rplatupd pre
rplatupd $UP
prepost $UP rplatupd post
9.Verify that the deactivate column is removed for the item/loc.
10.When the replenishment batches are run the order is created for the clearance item/location which is incorrect.
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 |