Product allocation: rules that hold in a shortage

A worked example. Week 32: 1,000 units of a product family are available. Customers have ordered 1,400.

Without rules

Orders are confirmed first come, first served. The webshop and two distributors ordered early and take 700 units. Key accounts, who order later in the week, get 300 of the 600 they need. On Friday the escalations start, and someone moves stock by hand.

With allocation agreed in S&OP

Customer groupOrderedAllocationConfirmedRelease rule
Key accounts60050%500Unused quota released on Wednesday
Distributors50035%350Released to key accounts first
Webshop30015%150Not released
Total1,400100%1,000

Nobody gets everything. But everybody knows on Monday what they will get, and sales can tell customers the same story. That is the point.

The three design choices

LevelCustomer group or key account; family or SKU. Coarse is easier to maintain.
PeriodWeekly is common. Daily only when supply really changes daily.
ReleaseWhen unused quota frees up, and for whom.

Advanced ATP in S/4HANA (and GATP in APO before it) supports all three. The hard part is the agreement, not the configuration.

Zakaria Rziki, founder of SCP-Network

Zakaria Rziki

Founder of SCP-Network. SAP supply chain planning architect since 2010: APO, IBP, S/4HANA, OMP and Kinaxis.

Follow on LinkedIn

Join the planner network

New notes like this one, planner sessions and roles we hear about. A few emails a year. Privacy statement.





More from Insights

All Insights on SAP supply chain planning