sd

1. Global Available-to-Promise
Purpose
You create a sales order in the R/3 System and carry out an availability check in APO. Global ATP does not only
function for APO relevant material. APO relevance does not mean that the material must be planned in APO. If
material is flagged as APO-relevant via the CIF integration model the advanced functionality of the global ATP can be
used.
For more information on orders in SAP APO see Sales Orders and Deliveries.
Advanced Functionality
The basic methods (product availability check, product allocation as an application of the check against plans,
check against forecasting) can be combined as advanced methods in any way required. For further information
see Combination of Basic Methods.
You can carry out checks with neutral results. For further information see Maintain Check Instructions.
You can display messages (alerts) if, for example, there is a shortage.
You can carry out rules-based availability checks. For further information see Rules-Based Availability Check.
When a sales order is created in the R/3 System, all rules that you defined in APO can be used.
When a sales order is created, the item is subdivided if alternative products/locations are proposed.
Several items can result from one order item. The main item contains the entry and the sum of the
confirmed quantities. The subitems contain the substituted products and locations with their confirmed
quantities.
Availability check calling Production Planning and Detailed Scheduling (PP/DS)
If material is not available, planned orders are created from APO in the R/3 System. For further information see
Capable-To-Promise (CTP).
Check using alternative material (100% alternative) is supported in production order processing (PP).
It is an advanced method that enables you to choose one or more products automatically from a list of
products in one check step. An availability check is carried out for all requirements. The product with the
highest priority is selected, whose requirements can be 100% confirmed by the requirements date.
You can carry out backorder processing for APO relevant products in APO. For further information see
Backorder Processing.
Prerequisites
You have successfully installed an R/3 System for Release: 3.1I, 4.0B, 4.5B and 4.6 C.
You successfully installed an APO system.
You installed a 4.5 GUI in the R/3 System.
You installed the R/3-Add-on APO CIF in the R/3 System.
You made the default settings for the CIF integration function.
The target system client of the RFC destination must correspond to the client in APO in which you

2. made the Customizing settings for the condition technique. Otherwise the check does not determine a
valid rule strategy.
You generated and activated integration models.
For further information see the documentation Integration of APO and R/3.
Rules-Based Availability Check
In the detailed display of transaction VOV8 a business event must be entered for the rules-based availability check.
Maintain the business event in R/3 Customizing (transaction OVRX). In IMG: Sales and Distribution → Basic
Functions → Availability Check and Transfer of Requirements → Availability Check → Rules-based Availability
Check → Define business transaction → ..... → Assign business transaction to an order type.
Requirements type with correct requirements class
The requirements class in the R/3 System must have the same value as the check mode in APO.
When you have created the check mode in APO, you should enter it for the corresponding product in the location-
specific product master. If a check mode is not provided by the calling application, the check mode that you defined
in the location-specific product master is taken into account. If the calling system is an SAP R/3 System, the
requirements class is transferred as the check mode by the SD applications. No other applications transfer check
modes.
In a rules-based availability check the system reads the check mode in the location-specific product
master for the subsequent requirements (substitutions).
Quantity Lock in the R/3 System
You should set the quantity lock for the availability check in the R/3 System so that the ATP check can deliver
consistent results in APO. You set the quantity lock in R/3 Customizing for Sales and Distribution via Basic
Functions → Availability Check and Transfer of Requirements → Availability Check → Availability Check with ATP
Logic or Against Planning → Define check ing groups. For further information see Maintain Global Settings.
See also:
R/3 documentation SD, Controlling the Availability Check in Sales and Distribution Processing.
APO Settings
Ensure that the ATP time series’ in Model Management and Version Management are updated. Otherwise you
cannot work with the product availability check in APO.
You can only set this indicator in an active version (000). You cannot change this setting subsequently. To reset this
indicator you must delete the active version and recreate. From SAP Easy Access select Master Data → Planning
Version Management → Model and Version Management.
For further information see Creating model.
See also:
Settings for Global ATP
Data Flow
General Data Transfer from the R/3 System to APO

3. You transfer data initially from the R/3 System to APO. You generated and activated a general integration model.
Master data (locations / products)
The master data must be transferred from the R/3 System in an initial run. During this process the OLTP data
is collected in a consistent data container that is transferred to APO. Data changes are filtered later into the
master data or transaction data and transferred automatically through an active data channel that uses ALE or
BAPI technology.
Transaction data (stock and requirements information)
An order created in the R/3 System is passed on to APO and converted into separate time series’.
Procurement, transportation and planned orders that are created in APO are returned to the OLTP system as
corresponding planned orders.
Planned orders (that APO has created) are converted to production orders in the R/3 System.
Transfer of ATP Customizing from the R/3 System to APO
You transfer ATP Customizing from the R/3 System to APO once. The settings in APO that have no equivalent in the
R/3 System must be maintained in APO.
Before you transfer the Customizing data, ensure that the import of ATP Customizing (including
Customizing for product allocation) is permitted in APO. For further information see Maintain Global
Settings.
The APO settings and their equivalents in SD in the R/3 System are listed below. Other R/3 applications have their
own Customizing equivalents.
Customizing Equivalents
APO R/3 (SD)
Business Event (/SAPAPO/ATP02) is filled at runtime Checking rule
from the R/3 System with the value of the checking rule.
ATP Group (/SAPAPO/ATP01) Checking group
Cumulation
Reaction to shortfall quantity
If you transfer ATP Customizing during the initial supply,
the ATP group is filled in the location-specific product
master.
The ATP group is always adopted from the product
master at runtime.
Check mode (/SAPAPO/ATP06) Requirements type with requirements class
Assignment mode
Production type
If you transfer ATP Customizing during the initial supply,
the check mode is supplied with the values from the R/3
System.

4. Note:
As of R/3 PlugIn 2000.1 the requirements
class (via the strategy group in the
material master) is transferred to the APO
product master (tab page ATP).
Is filled from the R/3 System at runtime or taken from
the product master.
You must enter the check mode in the location-specific
product master. The requirements class is only adopted
from SD. No other R/3 applications transfer
requirements classes. In this case the check mode is
read in the product master. This also applies in rules-
based ATP with product substitutions. The check mode
is also read here in the product master for the
subsequent requirements (substitutions).
Check instructions (/SAPAPO/ATP07) Requirements class
Which basic methods are processed and in Schedule line category
which order
Check (neutral results)
Rules-based check
Start/immediately
ATP alert active?
Start production
Time of production
The check instructions are maintained in APO.
.
Check control (/SAPAPO/ATP03) Scope of check (T441V)
Checking for sublocations
Checking for versions
Using checking horizon
Checking for APS deltas
Considering past receipts
Checking horizon for goods receipt
Categories (/SAPAPO/ATP03) MRP elements
There are also non-SAP categories
Category type
Sort
Map R/3 MRP element
Scope of check (/SAPAPO/ATP04) Scope of check (T441V)

5. Is always assigned to a check control
Collection of SAP categories and non-SAP
categories
Checking horizon You can reflect the replenishment lead time using this.
See also:
Product Availability Check using the Checking Horizon
Maintenance in APO
Check mode
This must be entered in the location-specific product master.
The calendar for the checking horizon and the base unit of measure must be entered in the location-specific
product master.
The check instructions must be maintained in APO.
Check control and scope of check must be maintained in APO.
See also:
Product Allocations During Sales Order Entry
Flexible Planning in R/3 and Product Allocations in APO
Rules-based ATP (R/3 and APO)
Availability Check Calling PP/DS
Processing Backorders