Advanced ATP Replacing Classic Availability Check
S/4HANA introduces Advanced ATP (aATP) as an embedded successor to the classic availability check and to standalone GATP/APO. Classic checking groups and checking rules still function, so nothing is forced to change on day one, but product allocation, backorder processing, rule-based substitution and alternative-based confirmation only exist in aATP, and any prior APO-based GATP integration must be resolved before the technical conversion can complete.
This page covers how the classic ECC availability check, driven by checking group and checking rule against VBBE requirements, differs from S/4HANA's Advanced ATP, and what that means for reports, interfaces, batch jobs and planner habits during a conversion. It focuses on the pre-conversion gate around existing GATP/APO integration and the practical failures teams hit once product allocation or the new backorder processing app enters the picture.
Published 16 Sept 2026· 1,161 words
Classic ECC behaviour
In ECC the availability check runs against a checking group set in the material master (MRP 3 view) combined with a checking rule tied to the transaction (sales order, delivery, stock transfer). Configuration under the OVZ family of IMG nodes controls scope of check, replenishment lead time, checking horizon and which stock, requirement and receipt categories participate. Each schedule line confirmation creates or updates an entry in table VBBE, the sales requirements table, which downstream reports and interfaces read to know what is confirmed versus open. Backorder processing runs as a background rescheduling job that re-sorts confirmations across competing orders by priority, typically scheduled overnight or at month end. Quantity allocation for scarce materials, where it existed at all, was either a bespoke ABAP solution built on top of VBBE, or delegated entirely to a separate SAP APO system connected via CIF, with its own planning book and characteristics-based ATP logic running outside the ECC system.
S/4HANA behaviour
Advanced ATP ships embedded in S/4HANA rather than as a separate APO instance, and it coexists with the classic check rather than replacing it outright. Checking group and checking rule configuration still exist and still work exactly as before for materials that are not switched on to advanced functions. What is new and only available under aATP is product allocation (a rules-driven quota mechanism replacing bespoke allocation logic), a dedicated backorder processing application, rule-based ATP substitution for product or location swaps, alternative-based confirmation for multi-item or multi-location fulfilment, and supply protection to reserve stock for priority segments. These functions use temporary quantity assignments recorded separately from the classic VBBE-based confirmation logic, and they are exposed through Fiori apps rather than the old backorder rescheduling report. Activation is granular: a plant/material combination can stay on the classic check indefinitely. Any prior standalone APO GATP landscape is not migrated automatically — the CIF integration to that external system has to be dismantled or the scope moved into embedded aATP, because a lingering APO connection is one of the items the conversion pre-check flags as blocking.
Project impact
The disruption is uneven: materials left on the classic check feel almost nothing, while any material moved onto product allocation or advanced backorder processing changes behaviour for planners, batch jobs and custom code simultaneously.
- Custom ABAP reports and interfaces that read VBBE directly to determine open versus confirmed quantity go stale for any material under product allocation or alternative-based confirmation, because those mechanisms record commitments as temporary quantity assignments outside the classic table structure.
- Any existing CIF connection to a standalone APO GATP system needs to be decommissioned or replaced before cutover; leaving it in place is a known blocker in the conversion readiness check, not a cosmetic warning.
- Batch jobs scheduled around the old backorder rescheduling report stop being the whole picture once the new backorder processing app is adopted for a subset of materials, so month-end rescheduling can silently miss those materials if the job wasn't split.
- New Fiori apps for product allocation and backorder processing carry their own authorization objects; users who only had the old transaction-based authorizations lose functional access on go-live weekend unless roles are extended in advance.
- Planners used to reading CO09 as the single source of truth need a second screen for allocation-relevant materials, and reconciling the two views under load is a common source of confusion in the first weeks after go-live.
Migration actions
The sequence matters because one item is a hard gate and the rest are configuration and testing decisions that can be phased.
- Run the ATP-related simplification item check as part of conversion readiness; this is a gate, not a cleanup task — an active standalone GATP/APO integration or an unresolved legacy quantity allocation setup must be addressed before the technical conversion proceeds.
- Decide per plant/material whether classic checking group logic remains sufficient or whether product allocation, rule-based substitution or alternative-based confirmation is needed; default to classic where nothing forces a change.
- For any prior APO-based GATP scope, either decommission the CIF link and rebuild the equivalent logic in embedded aATP, or formally retire the functionality if the business no longer needs it.
- Rebuild custom user exits or BAdI implementations that hook into the classic availability check against the current enhancement spots; old user exits tied to the ECC check are not guaranteed to fire the same way once aATP scope is active.
- Reconcile every custom report or interface that reads VBBE or old confirmation structures against the new temporary quantity assignment logic for materials under advanced functions.
- Test backorder processing end to end using the actual target tool (classic report or new app) at realistic order volumes, not a handful of test orders.
- Extend authorization roles for the new apps before go-live and retrain planners on where allocation-relevant confirmations now show up.
Whose problem this is
Functional: an SD consultant with GATP background owns checking rule scope, product allocation design and backorder strategy. Technical: basis and integration own dismantling any legacy APO CIF connection and activating the relevant scope. The go/no-go decision on the simplification-item gate belongs to the conversion project lead, since it blocks the technical cutover, not just a later configuration task.
Common pitfalls
Most of the damage from this change surfaces only under real volume or at month end, not in a quiet functional test.
- A test system with a handful of orders never reproduces the load pattern that exposes performance issues in aATP's real-time recalculation; problems appear only during peak order intake or mass backorder runs in production.
- Old rescheduling batch jobs get switched off during technical cutover on the assumption the new app replaces them entirely, leaving a subset of materials unrescheduled until someone notices deliveries aren't confirming.
- Custom code that assumes VBBE is the complete confirmation picture keeps compiling and running without error, it just reports wrong numbers for materials under product allocation.
- A dangling CIF connection to a decommissioned or soon-to-be-decommissioned APO system throws intermittent connection errors in test that get waved off as 'environment issue' instead of being tracked back to the actual gate item.
- Authorization gaps for the new Fiori apps are discovered by end users on the go-live weekend rather than in a role workshop, because the old transaction-based roles gave no signal that anything was missing.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-s4hana-changes/advanced-atp-replaces-the-classic-availability-checkERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.