SD Availability Check Part 5: aATP Product Availability Check in S/4HANA

📌 KEY POINTS
✅ aATP is the S/4HANA availability check; its core, the product availability check (PAC), still uses checking group, checking rule and scope of check.
✅ Additional functions: product allocation (PAL), alternative-based confirmation (ABC), backorder processing (BOP), supply protection (SUP), release for delivery.
✅ Calculations run on HANA with better performance and parallelization than classic ATP.
✅ Most additional functions are configured and operated through Fiori apps.
⚠️ aATP functions must be deliberately designed and activated — migrating to S/4HANA alone does not give you allocation or BOP segments.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–4 described classic concepts. Now the S/4HANA implementation.

━━━━━━━━━━━━━━━━━━━━
▶ 1. PRODUCT AVAILABILITY CHECK (PAC)

• Same scope logic (OVZ9) and requirements settings.
• Faster, with better handling of large volumes.
• Used in orders, deliveries and stock transport orders.

━━━━━━━━━━━━━━━━━━━━
▶ 2. ADDITIONAL FUNCTIONS

• Product allocation: quotas by customer/region/channel over periods (Part 6).
• Alternative-based confirmation: other plants/products (Part 7).
• Backorder processing with segments and strategies (Part 8).
• Supply protection: reserve supply for groups of customers.
• Release for delivery: decide which confirmed orders get released when stock is short.

━━━━━━━━━━━━━━━━━━━━
▶ 3. SEQUENCE OF CHECKS

• Product allocation check and PAC combine; ABC tries alternatives; BOP redistributes later.
• Configuration defines which functions apply per checking group/rule and scenario.

━━━━━━━━━━━━━━━━━━━━
▶ 4. APPS AND MONITORING

• BOP configuration and runs, product allocation planning, supply protection, release for delivery.
• Availability overview in Fiori; classic transactions still exist for some functions.

━━━━━━━━━━━━━━━━━━━━
▶ 5. MIGRATION CONSIDERATIONS

• Classic rescheduling (V_V2) remains available but BOP is the target.
• Classic product allocation is replaced by aATP product allocation.
• Global ATP (APO GATP) scenarios move to aATP.

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

1. Validate classic configuration (checking groups, rules, scope) in S/4HANA.
2. Identify business needs for PAL, ABC, BOP, SUP.
3. Configure and activate the needed functions.
4. Set up monitoring apps and roles.

✅ CHECKPOINT: you can explain for each aATP function which business problem it solves and whether your project needs it.

A company converted to S/4HANA expecting "aATP" to solve allocation of scarce products automatically. After go-live, order confirmation behaved exactly as before — only the PAC was active. A follow-up project designed BOP segments (key accounts first), supply protection for a hospital channel and product allocation for a constrained product line, each owned by supply chain with Fiori monitoring. The business value arrived only with this explicit design.

• Assuming aATP functions are active after conversion.
• Configuring allocation or BOP without business rules.
• Ignoring classic scope settings that aATP still uses.
• No monitoring roles for aATP apps.
• Porting APO GATP logic 1:1.

• Treat aATP functions as a design project with business owners.
• Keep PAC configuration clean first.
• Introduce PAL/ABC/BOP/SUP where business value is clear.
• Set up monitoring apps and KPIs.
• Redesign GATP scenarios rather than copying.

Questions: "What is aATP?", "Which functions does aATP offer?", "What changes versus classic ATP?"
Strong answer: PAC as core with checking group/rule/scope, plus PAL, ABC, BOP, supply protection and release for delivery; HANA performance; Fiori apps; functions must be designed and activated; classic rescheduling and allocation map to aATP equivalents.