SD / O2Cadvanced

SD Availability Check Part 6: Product Allocation in Advanced ATP

Key takeaway

Use product allocation to share constrained supply fairly: allocation objects and characteristics (customer, region, channel), periods and planned quantities, sequences combining several constraints, assignment to products and checks, consumption and monitoring — and when allocation is the wrong tool.

Explanation

📌 KEY POINTS
✅ Product allocation limits how much of a product each group (customer, region, channel) can be confirmed per period — regardless of total stock.
✅ An allocation object defines the characteristics and period (e.g. week); planning data holds the allowed quantities per characteristic value combination.
✅ Sequences combine several allocations (e.g. region quota and customer quota) that must all be respected.
✅ Orders consume allocation; unused allocation can be released or reassigned by planners.
⚠️ Allocation restricts confirmation even when stock exists — badly maintained quotas block sales unnecessarily.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 5 introduced aATP. Now fair-share rules for constrained products.

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHEN TO USE IT

New product launch, supply shortage, regulatory quotas.
Goal: fairness or strategic allocation, not stock-level checking.

━━━━━━━━━━━━━━━━━━━━
▶ 2. OBJECTS

Product allocation object: characteristics (e.g. sales org, customer group, country) and period type.
Planning data: allocated quantity per period and characteristic combination.
Sequence: which allocation objects apply, with constraint behavior.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ASSIGNMENT

Assign sequences to products (and plants).
Activation per checking group/rule context as configured.

━━━━━━━━━━━━━━━━━━━━
▶ 4. RUNTIME

Order entry checks PAC and allocation; confirmed = minimum of both.
Consumption visible per characteristic and period.
Unconfirmed quantities can be reconfirmed by BOP when allocation changes.

━━━━━━━━━━━━━━━━━━━━
▶ 5. OPERATION

Planners maintain quotas in the planning data app (or upload).
Monitor consumption; release or reallocate unused quantities.
End allocation when shortage ends.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Define the business rule (who gets how much, per period).
Create the allocation object and characteristics.
Maintain planning data.
Assign to products; test orders across groups.
Monitor consumption weekly.

✅ CHECKPOINT: region North cannot confirm beyond its weekly quota even though the plant has stock.

Code example

ABAP Code

===== STEP 1: product allocation design (example) =====Allocation object  ZREGION_WEEK : characteristics Sales org, Country | period: weekPlanning data      KW40: DE = 500 PC, FR = 300 PC, IT = 200 PCSequence           ZSEQ1 : ZREGION_WEEK (constraint) → optional customer-level object ===== STEP 2: assignment =====Assign sequence ZSEQ1 to product NEW-100 in plant 1000 ===== STEP 3: runtime =====Order DE 600 PC in KW40 → confirmed 500 (allocation), 100 unconfirmed or later periodPlanning data app: consumption DE 500/500, FR 120/300 → planner may shift quantities ===== STEP 4: typical apps (names per release) =====Configure Product Allocation | Manage Product Allocation Planning Data | Monitor Product Allocation

Real project scenario

During a launch of a new animal-health vaccine with limited supply, the first region to order consumed 70% of stock within two days. For the next batch, the company introduced product allocation by country and week, with quotas based on launch plans. Planners reallocated unused quotas every Monday. All countries could launch on time, and the allocation was switched off after supply stabilized.

Common mistakes

Using allocation as a permanent stock check.
Quotas not maintained for new periods → everything unconfirmed.
Too many characteristics, making quotas unmanageable.
No reallocation of unused quantities.
Forgetting to end allocation after the shortage.

Best practices

Use allocation for clear constraint scenarios with owners.
Keep characteristic combinations simple.
Maintain quotas ahead of periods.
Reallocate unused quantities regularly.
Combine with BOP for reconfirmation.

Interview angle

Questions: "What is product allocation?", "How does it differ from ATP?", "How would you allocate a new product launch?"
Strong answer: quotas per characteristics and period limiting confirmation regardless of stock; allocation objects, planning data, sequences, assignment; confirmation is minimum of PAC and allocation; planners maintain and reallocate; BOP reconfirms.

Practice this lesson

Quick check

1. Global supply is sufficient, but one region's orders stop confirming. Product allocation is active. What is the likely cause?

2. When is product allocation the right tool?

3. What does a product allocation object mainly define?

Interview questions

1. What is Product Allocation in SAP SD, and how does it restrict order confirmation during periods of constrained supply?

Answer it in your own words first, then compare.

2. A new vaccine has limited supply for the first three months, and the first region to order would consume most of it. How would you use product allocation?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.