LAST_DELIVERY_DATE Is Grater Than NEXT_DELIVERY_DATE In Replenishment Calculation Generating Zero SAFETY_STOCK

Last updated on AUGUST 15, 2017

Applies to:

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 grater than NEXT_DELIVERY_DATE for replenishment method "Dynamic", stock category "Warehouse" and service level type "Simple Sales" (SS).
LAST_DELIVERY_DATE should not be grater than NEXT_DELIVERY_DATE in order to generate SAFETY_STOCK in REPL_RESULT table.

Steps to reproduce:

1. 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"
2. Set the delivery schedule: "Every Week - Tuesday, Thursday and Saturday"
3. Make sure there are item forecast records in daily_item_forecast table for the item in question
4. Change VDATE to first review_date of the item
5. 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.
6. Change VDATE to second review_date of the item
7. 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.
8. Change VDATE to third review_date of the item
9. 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