Study guide
6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check
SAP S/4HANA Sales C_TS462
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure
1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration
2 Chapter 2: The Order-to-Cash Process and Sales Master Data
2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling
3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements
3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries
4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs
4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders
5 Chapter 5: Pricing and the Condition Technique
5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement
6 Chapter 6: Availability Check (ATP) and Delivery Scheduling
6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements
7 Chapter 7: Delivery Processing and Embedded EWM
7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries
8 Chapter 8: Billing and Integration with Financial Accounting
8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options
9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output
9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables
10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core
10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels
11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition
11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM
6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check
Key Takeaways Explain This Topic AI
The Available-to-Promise (ATP) check evaluates time-phased stock, planned receipts, and committed issues to provide reliable delivery promises.
The ATP determination logic is governed by the configuration triad: Checking Group (Material Master), Checking Rule (Calling Application), and Scope of Check (Transaction OVZ9).
Checking Group 01 accumulates requirements into daily totals, whereas Checking Group 02 creates individual line item requirements for discrete traceability.
The Scope of Check (OVZ9) precisely controls which inventory categories (safety stock, stock in transfer, quality inspection) and receipts/issues are included in availability calculations.
Replenishment Lead Time (RLT) defines the procurement or manufacturing horizon; when checking with RLT, orders with dates beyond the horizon are confirmed in full regardless of current stock.
Last updated: October 2026
Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check
In modern supply chain management and Order-to-Cash (O2C) processing, promising an accurate delivery date to a customer is a critical commercial commitment. An enterprise cannot afford to overpromise inventory, risking stockouts and delayed shipments, nor can it hold excessive safety stock that drives up working capital. The Available-to-Promise (ATP) check in SAP S/4HANA reconciles these competing objectives by calculating real-time, time-phased product availability during sales document entry and logistics execution.
Unlike a static stock lookup (such as viewing unrestricted stock in transaction MMBE ), the ATP check is dynamic. It evaluates not only the current physical stock in the warehouse, but also future anticipated receipts (purchase orders, production orders, planned orders) and future confirmed commitments (sales orders, deliveries, reservations) across a timeline. This guarantees that stock allocated to an existing customer cannot be mistakenly re-promised to another.
The ATP Configuration Triad: Checking Group, Checking Rule, and Scope of Check
The ATP calculation engine is controlled by an interlocking three-part configuration model known as the ATP Configuration Triad : [ Material Master: MARC-MTVFP ] [ Calling Application / Transaction ]
- Checking Group Checking Rule
- (e.g., 01 or 02) (e.g., A or B)
- │ │
- └──────────────────────┬───────────────────────┘
- ▼
- [ Customizing Table T441V / OVZ9 ]
- Scope of Check
- (Controls Stocks, Planned Receipts, and Committed Issues)
- 1. The Checking Group (Material Master)
The Checking Group is maintained on the material master record within the Sales: General/Plant Data view and the MRP 3 view (field MARC-MTVFP ). It defines:
Requirement Accumulation : Whether customer requirements are passed to Material Requirements Planning (MRP) as individual records or consolidated daily/weekly buckets.
01 — Daily Requirements : Demands from multiple sales orders on the same calendar day are consolidated into a single daily total. This reduces the number of planning records but obscures individual document traceability.
02 — Individual Requirements : Each sales order line item generates an independent requirement record. This provides discrete document pegging, allowing planners to identify exactly which sales order consumed which receipt.
KP — No Check : Availability check is deactivated entirely (common for non-stock consumables or bulk commodity packaging).
Lock Behavior : Whether the material's inventory record is locked with quantity reservation during sales order creation to prevent concurrent over-allocation.
2. The Checking Rule (Calling Application)
The Checking Rule is hardcoded or assigned to the specific business transaction calling the ATP engine. It identifies the operational stage of the document:
A — Sales Order Processing (SD sales order creation and modification via VA01 / VA02 ).
B — Outbound Delivery Processing (Shipping execution via VL01N / VL02N ).
PP — Production Order Component Check (Shop floor availability check via CO01 / CO02 ).
Why Checking Rules Differ Between Sales Orders and Deliveries
The separation of Checking Rules between sales orders ( A ) and outbound deliveries ( B ) is an essential architectural design in SAP:
During Sales Order Entry (Rule A ) : The customer order may be placed weeks or months before the delivery date. The business can reasonably include planned receipts, planned orders, purchase requisitions, and can check against the Replenishment Lead Time (RLT) because the manufacturing plant has sufficient time to produce or acquire new inventory.
During Outbound Delivery Creation (Rule B ) : The warehouse is preparing to physically pick, pack, and stage the goods within hours or days. At this execution stage, long-term purchase requisitions and planned production orders are useless—only physically available unrestricted stock, quality inspection stock nearing release, or immediate inbound shipments can be permitted. Replenishment Lead Time is deactivated.
The Scope of Check: Transaction OVZ9
The combination of the Checking Group (from the material) and the Checking Rule (from the transaction) forms the access key for the Scope of Check in transaction OVZ9 (table T441V ). The Scope of Check dictates exactly which stock categories, receipt elements, and demand elements are included in the ATP calculation. The values in the table below are an example configuration; each company sets its own scope. The official course example, for instance, includes purchase orders but excludes stock in quality inspection.
Configuration Parameter (OVZ9) Example: Sales Order Rule (02 + A) Example: Delivery Rule (02 + B) Functional Impact
Include Safety Stock Excluded Excluded Safety stock is reserved as an emergency buffer. If checked, safety stock can be consumed by customer orders.
Include Stock in Transfer Included Included Stock currently physically moving between company plants ( T-Stock ).
Include Quality Inspection Stock Conditionally Included Excluded Stock undergoing lab inspection ( Q-Stock ). Included in orders if release is guaranteed; excluded in delivery picking.
Include Blocked Stock Excluded Excluded Defective, expired, or quarantine stock. Almost universally excluded from both orders and deliveries.
Include Restricted-Use Stock Excluded Excluded Batch inventory with status 'restricted' in batch management.
Include Purchase Orders Included Conditionally Included Confirmed external purchase orders with scheduled delivery dates from suppliers.
Include Purchase Requisitions Included Excluded Unapproved internal purchase requests; viable for forward order planning, invalid for delivery picking.
Include Planned Orders Included Excluded Planned manufacturing runs generated by MRP; excluded at delivery stage.
Include Production Orders Included Conditionally Included Released shop-floor manufacturing orders with firm production finish dates.
Include Reservations Included Included Warehouse manual reservations or maintenance demands that reduce available inventory.
Check Without Replenishment Lead Time Not Set (Check WITH RLT) Set (Check WITHOUT RLT) Controls whether infinite availability is assumed beyond the procurement/production lead time.
Important
If an enterprise includes Quality Inspection stock in the Scope of Check for Sales Orders ( A ), the sales representative can confirm orders against goods currently in the laboratory. However, if the Scope of Check for Deliveries ( B ) excludes Quality Inspection stock, the delivery cannot be created until Quality Management posts the usage decision ( QA11 ) moving stock from inspection to unrestricted.
Cumulative ATP Quantities Calculation Logic
The fundamental calculation of ATP at any given point in time t t t is expressed by the baseline formula: ATP Quantity ( t ) = Usable Physical Stock + ∑ Planned Receipts ( t ) − ∑ Confirmed Commitments ( t ) \text{ATP Quantity}(t) = \text{Usable Physical Stock} + \sum \text{Planned Receipts}(t) - \sum \text{Confirmed Commitments}(t) ATP Quantity ( t ) = Usable Physical Stock + ∑ Planned Receipts ( t ) − ∑ Confirmed Commitments ( t )
However, a simple period-by-period check can lead to severe shortages if future commitments are ignored. SAP uses Cumulative ATP Logic (with calculation of missing parts) to ensure that confirming a new order in an earlier timeline bucket does not create an unfulfillable deficit for an already-confirmed order in a later timeline bucket.
Worked Example: The Danger of Non-Cumulative Checking
Consider a manufacturing plant with the following inventory situation for high-performance industrial pumps:
- Current On-Hand Stock (Day 1) : 50 units
- Confirmed Order 1 (Due Day 3) : 30 units (Confirmed)
- Inbound Purchase Order Receipt (Due Day 10) : 40 units
- Confirmed Order 2 (Due Day 12) : 50 units (Confirmed)
Now, a new customer calls on Day 1 requesting 30 units for delivery on Day 5 :
Naive (Non-Cumulative) Period Calculation at Day 5 :
Stock on Day 1 = 50 units.
Order 1 consumed 30 units on Day 3 → \rightarrow → Remaining physical stock = 20 units.
Naive evaluation might see 20 units available, or if checking against Day 10 receipts, falsely assume plenty of stock exists.
Cumulative ATP Analysis Across the Timeline :
- Timeline Bucket Receipts (+) Commitments (-) Running Balance
- Day 1 (Initial Stock) +50 — 50
- Day 3 (Order 1 Confirmed) — -30 20
- Day 10 (PO Receipt) +40 — 60
- Day 12 (Order 2 Confirmed) — -50 10
The running balance is not the cumulative ATP quantity. For ATP, each confirmed requirement reduces the ATP quantity of the stock or receipt closest to it when looking into the past (official S46001 content): Order 2 (Day 12) uses the 40 units of the Day 10 receipt and 10 units of stock, and Order 1 (Day 3) uses 30 units of stock. That leaves an ATP quantity of 10 units on the stock and none on the receipt, so the cumulative ATP quantity is 10 units from Day 1 onward , and still 10 units after Day 10.
Look at what each element really covers. Order 2 needs 50 units on Day 12, but the purchase order brings only 40, so 10 units of the Day 1 stock must stay reserved for Order 2. Of the 50 units in stock, 30 are committed to Order 1 and 10 to Order 2, which leaves 10 units free. The receipt on Day 10 cannot help a requirement on Day 5, because a requirement can only use stock and receipts dated on or before its own requirement date.
Under Cumulative ATP Logic , the system therefore confirms only 10 units for Day 5. Because the cumulative ATP quantity is 10 units on every later date as well, the remaining 20 units stay unconfirmed until new receipts are planned (or, when checking with replenishment lead time, a date after the lead time is reached). Confirming 30 units would have taken stock that Order 2 depends on.
Replenishment Lead Time (RLT) in ATP Processing
The Replenishment Lead Time (RLT) is the total duration required to manufacture or externally procure a material if no stock or planned receipts are available. In customizing ( OVZ9 ), the flag Check Without Replenishment Lead Time dictates how the ATP engine behaves when demand extends beyond this horizon.
Check WITH RLT (Flag Unchecked)
Standard for Sales Orders (Checking Rule A ) .
If the customer's Requested Delivery Date falls after the expiration of the Replenishment Lead Time, the system assumes infinite availability .
The system confirms 100% of the requested quantity on the requested delivery date, even if on-hand inventory is zero and no purchase orders exist!
Business Rationale : The enterprise has adequate time to purchase raw materials or execute production before the goods are scheduled to leave the plant.
Check WITHOUT RLT (Flag Checked)
Standard for Deliveries (Checking Rule B ) and Constrained/MTO Scenarios .
The system confirms orders only if physical stock or actual scheduled receipts (firm POs, production orders) exist.
If stock is zero and no receipts exist, the confirmed quantity remains 0 , regardless of how far into the future the requested delivery date lies.
Business Rationale : Essential for scarce, allocation-controlled materials or high-value engineered goods where production cannot begin without manual planning intervention. Timeline: Today (Day 0) ─────────────────── RLT Boundary (Day 20) ──────────────────> Future
[ Inside RLT ] [ Beyond RLT ]
With RLT: Check against physical stock & firm receipts. INFINITE AVAILABILITY!
Shortages cause delayed confirmation. Orders confirmed in full.
Without RLT: Check against physical stock & firm receipts. STILL LIMITED TO REAL STOCK!
No stock = 0 confirmed. No stock = 0 confirmed.
How SAP Calculates Replenishment Lead Time
The calculation of RLT depends on the material's procurement type in the Material Master:
1. Manufactured Materials (Internal Production — Procurement Type E )
If the Total Replenishment Lead Time ( MARC-WZEIT ) is maintained in the MRP 3 view, the system takes this fixed number of calendar/work days directly.
If MARC-WZEIT is blank, the system dynamically calculates the lead time using parameters from the Work Scheduling / MRP 2 views: RLT = In-House Production Time (MARC-DZEIT) + Goods Receipt Processing Time (MARC-WEBAZ) \text{RLT} = \text{In-House Production Time (MARC-DZEIT)} + \text{Goods Receipt Processing Time (MARC-WEBAZ)} RLT = In-House Production Time (MARC-DZEIT) + Goods Receipt Processing Time (MARC-WEBAZ)
2. Externally Procured Materials (Trading Goods — Procurement Type F )
For trading goods purchased from external suppliers, RLT is calculated dynamically by summing three parameters: RLT = Purchasing Processing Time + Planned Delivery Time (MARC-PLIFZ) + GR Processing Time (MARC-WEBAZ) \text{RLT} = \text{Purchasing Processing Time} + \text{Planned Delivery Time (MARC-PLIFZ)} + \text{GR Processing Time (MARC-WEBAZ)} RLT = Purchasing Processing Time + Planned Delivery Time (MARC-PLIFZ) + GR Processing Time (MARC-WEBAZ)
Purchasing Department Processing Time : Working days required by purchasing to create and send the purchase order (maintained per plant in the plant parameters for materials planning).
Planned Delivery Time : Calendar days required by the vendor to supply the goods after PO receipt ( MARC-PLIFZ or Purchasing Info Record).
Goods Receipt (GR) Processing Time : Work days required by the receiving warehouse to unpack, inspect, and place goods into unrestricted inventory ( MARC-WEBAZ ).
- What the Official ATP Course Adds
- Requirement Date and Check Level
The availability check does not use the requested delivery date directly. Scheduling first calculates the material availability date (the date the goods must be ready for shipping), and that date is the requirement date of the item. The check then runs in the delivering plant of the item. If a storage location is in the item, the check also runs at storage location level, and the level with the lower cumulative ATP quantity decides the result. Sales orders normally have no storage location (classic ATP cannot determine one automatically), while deliveries usually do. With aATP activated, Alternative-Based Confirmation can determine and substitute plants and storage locations automatically.
Shortage Check
Because the basic check only compares a new requirement with cumulative ATP quantities, moving receipts into the future can leave already confirmed orders short. A shortage check can be activated in the checking group. With value 3 , for example, unconfirmed requirements also reduce the cumulative ATP quantity when a new order is created, while only confirmed quantities count in change mode.
Which App Shows Availability?
Statements about availability can only be based on the cumulative ATP quantity . The Availability Overview app shows it. The Monitor Stock/Requirements List , Stock - Single Material , and Check Material Coverage apps show stocks and requirements but not the cumulative ATP quantity, so they should not be used to decide whether a new requirement can be confirmed.
Delivery Agreements
When items are not available as requested, the delivery agreements decide what happens:
Complete delivery (header): the whole order waits until all items can be delivered. It is proposed from the sold-to party's business partner master.
Partial delivery (item): available items or quantities can go ahead. It is proposed from the sold-to party or, with higher priority, from the customer-material info record.
Both can be changed manually in the order.
ATP and Transfer of Requirements Work Together
If customer requirements are relevant for MRP, the next MRP run creates purchase requisitions or planned orders for a shortage. Those receipts help the order only if they are in the scope of check, and even then the saved order is not rechecked automatically: backorder processing is needed to improve its confirmation. With aATP and PP/DS, Supply Creation-Based Confirmation creates the receipt elements directly from the availability check and confirms against them immediately, without an MRP run.
High-Frequency Exam Traps and Best Practices
Tip
Transaction CO09 (Availability Overview) is the primary diagnostic transaction for ATP issues. Unlike MMBE (which only shows static physical stock), CO09 displays the time-phased ledger of all receipts, requirements, confirmed quantities, and the running cumulative ATP balance for a material-plant combination under a specific checking rule.
Trap: Conflating Checking Group with Checking Rule : Remember that the Checking Group is an attribute of the Material ( MARC ), while the Checking Rule is an attribute of the Transaction ( A for sales order, B for delivery). Neither can determine the scope of check alone.
Trap: Assuming RLT applies to Deliveries : Outbound deliveries should never check with Replenishment Lead Time. A delivery represents imminent physical execution; confirming an outbound delivery based on future procurement lead time causes shipping blockages and picking failures.