My Oracle Support Banner

Replenishment Did Not Considered Priority Group (Doc ID 2727881.1)

Last updated on MAY 16, 2022

Applies to:

Oracle Retail Merchandising Foundation Cloud Service - Version NA and later
Information in this document applies to any platform.

Symptoms

Replenishment did not considered priority group.

Replenishment attributes was activated for warehouse(WH) stocked.
All 6 stores(3 stores with priority 1 and 3 with priority 2) have net inventory of zero.
WH has 100 available inventory.
Max qty for priority 1 stores are 31 each.
Max qty for priority 2 stores are 21 each.

Expectation is that the priority group 1 should get fully distributed for 93 units.
The remainder of 7 units should be distributed to priority 2 stores.

Actual result was that all 6 stores had prorated distribution.
 

Steps to reproduce:


1. Setup priority group
2. Priority 1 : Store 1, 2, 3.
3. Priority 2 : Store 4,5,6.
4. Activated replenishment attributes.
5. Run Replenishment batches

./prepost $UP rplatupd pre
./rplatupd $UP
./prepost $UP rplatupd post
./rilmaint $UP
./prepost $UP rilmaint post
./prepost $UP replroq pre
./replroq.ksh
./reqext.ksh $UP Y
./prepost $UP rplext pre
./rplext.ksh $UP Y N



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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.