Availability Check

Lessons in this topic

• Backorder Processing, Rescheduling, and Cross-Module Integration in Availability CheckCovers backorder processing, rescheduling of confirmed quantities, and how ATP integrates with MM procurement and PP production to resolve supply-demand mismatches in production support scenarios.
• Scope of Check: Checking Groups, Checking Rules, and Replenishment Lead TimeExplains how checking groups and checking rules combine to define the scope of check, and how replenishment lead time (RLT) and checking horizon influence ATP results.
• Architecting Availability Check at Scale: Classic ATP, aATP, and Landscape Trade-offsEvaluate architectural decisions for Availability Check design across ECC, S/4HANA embedded aATP, and decentralized aATP, covering performance, governance, migration, and operational controls at enterprise scale.
• Configuring Availability Check: Checking Groups, Scope of Check, and Document FlowLearn how checking groups, checking rules, and scope of check are configured together, and how ATP results flow from sales order to delivery in real transactions.
• Why Availability Check Matters: Business Purpose and Core ConceptsUnderstand what Availability Check (ATP) does, why it exists, and the basic terms every SD consultant must know before touching configuration.

Interview questions covered

• 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.
• Explain how backorder processing (via rescheduling) reallocates confirmed quantities across competing sales orders when new stock becomes available.
• When a sales order item carries a delivery block, does the system still perform ATP checking and transfer requirements to MRP, and what are the implications for planning?
• In a make-to-order (MTO) scenario, how do you configure the availability check so that ATP considers only the specific sales order stock rather than general plant stock?
• What is backorder processing in SD and how does it relate to ATP and requirements transfer?
• In a multi-level document flow (quotation to sales order to delivery to billing), the sales order shows confirmed schedule line quantities that match the ATP check performed at order creation, but MD04/stock-requirements list shows a different open requirement quantity for the same item. As lead architect across an ECC and S/4HANA landscape, walk through your diagnostic approach to reconcile ATP confirmation, transfer of requirements, and document flow visibility.
• An MTO sales order's schedule line shows zero confirmed quantity even though stock exists, and downstream delivery creation is blocked. How would you investigate whether incompletion procedure settings are contributing to this?
• As a solution architect, how would you design the availability check strategy for a global rollout where some plants use classic ATP (checking groups/rules) while a newly implemented plant is on S/4HANA's advanced ATP (aATP) with product allocation, ensuring sales document types behave consistently for order entry users?
• Walk through how requirements transfer and ATP checking work for a standard sales order item using SAP standard availability check (checking group/checking rule), including which tables and background processes are involved from order entry to requirement visibility in MRP.
• A customer's high-priority order for an MTO material is stuck unconfirmed because stock was consumed by earlier orders with lower priority. How would you approach backorder processing to reallocate confirmed quantities correctly?
• Walk through how the availability check determines confirmed schedule lines when checking rule, checking group, and replenishment lead time interact, and what happens if backward scheduling pushes the requested date before today.
• What is Product Allocation in SAP SD, and how does it restrict order confirmation during periods of constrained supply?
• During a make-to-order order entry, the availability check returns a confirmed date far beyond the requested delivery date, and the order still saves without any incompletion warning. What would you check to explain why incompletion did not flag this?

Related topics