Study guide

6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements

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.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements

Key Takeaways Explain This Topic AI

Advanced ATP (aATP) must be activated (and licensed) in SAP S/4HANA Cloud Private Edition and on-premise; when it is active, classic backorder transactions CO06, V_RA, and V_V2 can no longer be used.

aATP backorder processing assigns each requirement in a BOP segment one of the confirmation strategies Win, Gain, Improve, Redistribute, Fill, Lose, or Skip.

Product Allocation (PAL) manages constrained supply by restricting order confirmations to predefined customer or regional quotas, regardless of warehouse stock levels.

Alternative-Based Confirmation (ABC) can substitute the delivering plant or storage location automatically when the original one cannot confirm the requirement.

Transfer of Requirements (TOR) links sales orders to MRP through requirement types (OVZH) and requirement classes (OVZG); the requirement type is found first from the strategy group, then from item category and MRP type (OVZI).

Last updated: October 2026

Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements

In SAP ERP, rescheduling sales orders relied on classic backorder transactions such as V_V2 , which rechecked documents largely in their entry sequence, and a different plant had to be entered manually. In SAP S/4HANA, Advanced Available-to-Promise (aATP) is the business function that adds product allocation, alternative-based confirmation, configurable backorder processing, and further functions to the availability check. In SAP S/4HANA Cloud Private Edition and on premise it must be activated and requires an additional license; in SAP S/4HANA Cloud Public Edition, aATP is the only code line.

The official course is based on a system with aATP activated, so its terminology (BOP segments, variants, and confirmation strategies) appears in the course examples.

Classical ERP ATP vs. S/4HANA Advanced ATP (aATP)

Architecture / Capability Classical ATP in SAP ERP (ECC) Advanced ATP (aATP) in SAP S/4HANA

Data Storage Architecture Writes individual requirements to VBBE and summarized requirements to the totals table VBBS . Requirements are kept in VBBE ; the totals table VBBS is no longer used, and totals are calculated when needed.

Backorder Rescheduling Transactions CO06 , V_RA , and V_V2 BOP segments, BOP variants, and confirmation strategies ( Win , Gain , Improve , Redistribute , Fill , Lose , Skip ); results in Monitor BOP Run

Alternative Sourcing The user replaces the plant manually in the item. Alternative-Based Confirmation (ABC) can replace the plant or storage location automatically, controlled in the Manage Substitutions - Locations app.

Quota & Rationing Management Classic product allocation based on LIS info structures Product Allocation (PAL) , configured and planned in SAP Fiori apps

User Experience SAP GUI transactions ( VA02 , CO09 , V_V2 , V_RA ). Modern SAP Fiori Launchpad apps (Configure BOP Segment, Configure BOP Variant, Monitor BOP Run).

The Core Capabilities of SAP S/4HANA aATP

Advanced ATP is not a single feature. Besides backorder processing, its capabilities include product allocation, alternative-based confirmation, release for delivery, and supply creation-based confirmation (with PP/DS). Two of them in detail:

1. Product Allocation (PAL)

When market demand outstrips available production capacity (such as during new product launches, raw material shortages, or seasonal demand surges), an enterprise must avoid allowing a single high-volume customer to order the entirety of warehouse inventory, starving other key accounts. Product Allocation (PAL) enforces planned distribution quotas:

Allocation Dimensions : Quotas can be maintained along multi-tiered dimensions, including Sales Organization, Distribution Channel, Customer Group, Individual Strategic Customer, or Geographic Region.

Time Buckets : Allocations are defined in discrete time intervals (weekly, monthly, quarterly).

ATP Gating : During sales order entry, the ATP check evaluates both physical stock and the customer's remaining allocation balance. Even if 10,000 units sit in the warehouse, if the buyer's weekly quota is 500 units and they have already consumed 400, the sales order will only confirm 100 units.

2. Alternative-Based Confirmation (ABC)

In traditional order processing, if the requested delivering plant has zero stock, the order line item remains unconfirmed unless a customer service representative manually changes the plant or splits the line. Alternative-Based Confirmation (ABC) automates this decision in real time:

Plant Substitution : If Plant 1010 has insufficient inventory, ABC evaluates alternate distribution centers (e.g., Plant 1020 or Plant 1030) based on predefined substitution rules.

Storage Location Substitution : Diverts orders between automated high-rack storage and manual pick locations.

Maintenance : Substitution strategies for locations are maintained in the Manage Substitutions - Locations app.

Backorder Processing (BOP) and the Confirmation Strategies

Backorder processing exists for three reasons named in the official course. First, a saved order is never rechecked by itself, even when new receipts arrive. Second, the availability check works on a first come, first served basis, so an important order entered later may find no stock. Third, an order confirmed against a planned receipt keeps an unrealistic date if that receipt moves. Backorder processing revises existing confirmations to solve these problems.

In aATP, a run is built from three objects:

BOP segment : a saved selection that decides which requirements are selected and in which priority sequence they are processed.

Confirmation strategy : assigned to each segment in the Configure BOP Variant app; it decides how the requirements of that segment are treated.

BOP variant : defines which segments are included in a run and with which strategies. Variants are scheduled as background jobs, and results are checked in the Monitor BOP Run app.

The official course lists these confirmation strategies:

Strategy What Happens to the Assigned Requirements

Win Fully confirmed on the requested date (or immediately, if the requested material availability date is in the past)

  • Gain Keep at least their current confirmation and improve it if possible
  • Improve Try to keep their confirmation and improve it, but could also lose it
  • Redistribute Can get a better, equal, or worse confirmation
  • Fill Get no additional quantity and no earlier date; their confirmation stays equal or gets worse
  • Lose Lose their current confirmation and are not confirmed
  • Skip Keep their current confirmation and are not included in the availability check

Tip

Exam trap : Fill does not protect a confirmation. It only prevents the requirement from gaining quantity; if stock is needed for higher-priority segments, a Fill requirement can end up with a worse confirmation. The strategy that freezes a confirmation without checking it is Skip .

A typical design assigns Lose to a low-priority segment: its confirmations are released, the cumulative ATP quantity increases, and a segment with Improve or Win can then use that quantity.

Transfer of Requirements (TOR) and S/4HANA Simplification

Transfer of Requirements (TOR) is the integration bridge between Sales and Distribution ( SD ) and Material Requirements Planning ( PP-MRP / MM ). When a customer places a sales order, the demand must be transmitted to the manufacturing and purchasing departments so replenishment orders can be triggered.

The Requirement Type and Requirement Class Architecture

The configuration chain governing TOR runs through two fundamental entities: Item Category (e.g., TAN) + MRP Type (e.g., PD)

  • │
  • ▼
  • Requirement Type (e.g., 011 - Delivery Requirement)
  • │
  • ▼ (requirement class assigned to the type)
  • Requirement Class (e.g., 041 - Order/Delivery Requirement)

├── Availability check active?

├── Requirements transfer active?

└── Further settings (e.g., allocation, costing)

Requirement Type Determination (in this order):

From the strategy group in the material's MRP 3 view (through the main planning strategy); if none is found, from the MRP group.

Otherwise from the item category and the material's MRP type (transaction OVZI ), and finally from the item category alone.

Requirement Class Configuration (requirement types in OVZH , requirement classes in OVZG ) :

The Requirement Type points directly to a Requirement Class (table T459K ).

The Requirement Class contains the primary operational switches:

Availability check : Activates or deactivates the ATP check for sales documents.

Requirements transfer : Activates or deactivates passing sales requirements to MRP.

Both checks can additionally be switched off at schedule line category level.

S/4HANA Simplification: No Totals Table VBBS

In classic SAP ERP, individual requirements were stored in VBBE , while summarized requirements (checking groups with daily or weekly totals) were stored in the totals table VBBS . Writing totals records created lock contention during parallel order entry. In SAP S/4HANA, VBBS is no longer used: requirements are stored as individual records in VBBE , and totals are calculated when they are needed.

Loading diagram... aATP Backorder Processing: Segments, Variants, and Confirmation Strategies