LAST_DELIVERY_DATE Is Greater Than NEXT_DELIVERY_DATE In Replenishment Calculation Generating Zero SAFETY_STOCK
(Doc ID 2295839.1)
Last updated on OCTOBER 15, 2020
Applies to:
Oracle Retail Merchandising System - Version 13.2.8 and laterInformation in this document applies to any platform.
Symptoms
When running the replenishment calculation in Retail Merchandising System(RMS), no SAFETY_STOCK is being generated in REPL_RESULTS table when LAST_DELIVERY_DATE is greater than NEXT_DELIVERY_DATE for replenishment method "Dynamic", stock category "Warehouse" and service level type "Simple Sales" (SS).
LAST_DELIVERY_DATE should not be greater than NEXT_DELIVERY_DATE in order to generate SAFETY_STOCK in REPL_RESULT table.
Steps to reproduce:
- Create new item and define its replenishment details: Stock Category "Warehouse Stocked", Order Control "Manual", Replenishment Method "Dynamic", Service Level Type "Simple Sales", Replenishment Cycle "Every Week - Tuesday and Thursday", Warehouse to Location "2"
- Set the delivery schedule: "Every Week - Tuesday, Thursday and Saturday"
- Make sure there are item forecast records in daily_item_forecast table for the item in question
- Change VDATE to first review_date of the item
- Run replenishment batches: rplatupd, rilmaint, repladj, ociroq, reqext, rplext, supsplit, rplbl, supcnstr, rplsplit, rplapprv and notice the results. Notice that NEXT_DELIVERY_DATE is less than LAST_DELIVERY_DATE, and the SAFETY_STOCK is zero.
- Change VDATE to second review_date of the item
- Run replenishment batches: rplatupd, rilmaint, repladj, ociroq, reqext, rplext, supsplit, rplbl, supcnstr, rplsplit, rplapprv and notice the results. Notice that NEXT_DELIVERY_DATE is grater than the LAST_DELIVERY_DATE, and the SAFETY_STOCK is grater than zero.
- Change VDATE to third review_date of the item
- Run replenishment batches: rplatupd, rilmaint, repladj, ociroq, reqext, rplext, supsplit, rplbl, supcnstr, rplsplit, rplapprv and notice the results. Notice that NEXT_DELIVERY_DATE is less than LAST_DELIVERY_DATE, and the SAFETY_STOCK is zero.
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 |