Scheduled Replenishment Attribute Updates Remove Deactivate Date
(Doc ID 3065536.1)
Last updated on JANUARY 02, 2025
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 19.3 to 19.3 [Release 19.3]Information in this document applies to any platform.
Symptoms
Scheduled replenishment attribute updates remove Deactivate date
ERROR
-----------------------
deactivate date is removed
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Future dated replenishment attribute change for MIN_STOCK and MAX_STOCK submitted with an 11/1 effective date.
2. SKU/Loc deactivated effective immediately or sometime prior to pending replenishment attribute update from step 1.
3. After 11/01 batch, system has processed the scheduled entry from Step 1. Min/Max values are updated and Deactivate date is wiped out. Updated Min/Max is fine, but Deactivate date should stay as 10/27/24 from step 2.
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 |