SD / O2Cadvanced

SD Availability Check Part 8: aATP Backorder Processing — Segments, Strategies and Reconfirmation

Key takeaway

Run backorder processing in S/4HANA: BOP segments that group requirements by rules, confirmation strategies (Win, Gain, Redistribute, Fill, Lose), BOP variants, simulation and scheduled runs, monitoring results and integrating BOP with allocation and release for delivery.

Explanation

📌 KEY POINTS
✅ BOP segments group requirements with filter conditions (e.g. key accounts, region, order type) and sort criteria.
✅ Each segment gets a confirmation strategy: Win (must be fully confirmed as requested), Gain (keep and improve), Redistribute (may gain or lose), Fill (keep what is possible, no improvement), Lose (release confirmations).
✅ A BOP variant combines segments in priority order; runs are simulated, then scheduled.
✅ Results and changes per item are monitored in Fiori; unexpected losses can be analysed.
⚠️ Putting too many requirements into "Win" makes the run fail or starve everyone else.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 7 covered alternatives. Now systematic redistribution with aATP.

━━━━━━━━━━━━━━━━━━━━
▶ 1. SEGMENTS

Filter: characteristics such as customer, customer group, sales org, order type, delivery priority.
Sorting inside the segment (e.g. requested date, priority).

━━━━━━━━━━━━━━━━━━━━
▶ 2. CONFIRMATION STRATEGIES

Win: highest priority, full confirmation on requested date.
Gain: never lose, improve if possible.
Redistribute: can gain or lose.
Fill: keep confirmation if possible, never improved.
Lose: give up confirmations (e.g. low priority, blocked customers).

━━━━━━━━━━━━━━━━━━━━
▶ 3. VARIANTS AND RUNS

Variant = scope (materials/plants) + segment order + strategies.
Simulate, review, then schedule (e.g. nightly).
Parallel processing for large volumes.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MONITORING

Results per run: gained, lost, unchanged items.
Drill-down to the reason.
KPIs: fill rate by segment, order confirmations changed.

━━━━━━━━━━━━━━━━━━━━
▶ 5. INTEGRATION

Respects product allocation and supply protection.
After BOP: deliveries created by delivery due list; release for delivery when stock is short.
Communicate changed confirmations (output).

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

Agree segment rules and strategies with sales and supply chain.
Configure segments and a variant.
Simulate on real data; review losses.
Schedule the run and monitor KPIs.

✅ CHECKPOINT: after a supply cut, key-account orders keep full confirmation and low-priority orders lose theirs, as simulated.

Code example

ABAP Code

===== STEP 1: segments (example) =====Segment KEY_ACCOUNTS : customer group = 01                 sort: requested dateSegment STANDARD     : sales org 1000, all other customers sort: delivery priority, order dateSegment BLOCKED      : credit block or delivery block set ===== STEP 2: variant =====Variant ZBOP_DE : plant 1000, material group FG*  1. KEY_ACCOUNTS → Gain (or Win for contractual commitments)  2. STANDARD     → Redistribute  3. BLOCKED      → Lose ===== STEP 3: operation (apps, names per release) =====Configure BOP Segment → Configure BOP Variant → Schedule BOP Run (simulate first) → Monitor BOP Run

Real project scenario

A consumer goods company defined a "Win" segment for all customers flagged "important" — 40% of volume. During a shortage, the BOP run could not satisfy all Win requirements, and results were unusable. Redesign: Win only for contractually guaranteed deliveries (3%), Gain for strategic accounts, Redistribute for the rest, Lose for blocked customers. Simulations became predictable, and fill rate for strategic accounts stayed above target during the next shortage.

Common mistakes

Too broad Win segments.
Running BOP without simulation.
Segments based on data that isn't maintained (e.g. customer groups).
Ignoring blocked orders consuming supply.
No communication of changed confirmations.

Best practices

Keep Win for contractual commitments only.
Base segments on maintained master data.
Simulate before each production run change.
Monitor KPIs per segment.
Release confirmations of blocked orders with Lose.

Interview angle

Questions: "How does aATP BOP work?", "Explain the confirmation strategies", "How would you design segments?"
Strong answer: segments with filters and sorting, strategies Win/Gain/Redistribute/Fill/Lose, variants in priority order, simulation and scheduled runs, monitoring, integration with allocation, supply protection and release for delivery.

Practice this lesson

Quick check

1. Which aATP BOP confirmation strategy never lets a requirement lose confirmation but allows improvements?

2. What is a BOP segment in aATP?

3. Why should the Win strategy be used sparingly in BOP variants?

Interview questions

1. You are running backorder processing (BOP) across thousands of open sales order items after a major stock receipt. Walk through how BOP reallocates confirmed quantities and what schedule line determination factors influence which orders get priority.

Answer it in your own words first, then compare.

2. Design an aATP backorder processing setup for a company with contractual commitments, strategic accounts, normal customers and credit-blocked orders.

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.