Availability Check Calling PP/DS 
Use
You carry out an availability check in APO and want production to take place if the requirement cannot be covered.

Production Planning and Detailed Scheduling (PP/DS) can be called directly.
Prerequisites
Settings in APO (Global ATP)

Note that the location must be a production plant. Testing of the locations only takes place if you enter the substitute locations in the location determination procedure.
Settings in PP/DS
You selected tab page PP/DS in the location-specific product master data. You must have configured automatic planning for the multi-level availability check. You must also define here where the bill of material should be exploded.
See also:
Maintaining Check Instructions Maintaining Location Determination Activities Production Planning and Detailed Scheduling Settings for PP/DS Automatic Planning
Settings in the R/3 System
Process

If the date corresponds to the requested delivery date you branch immediately to the sales order. If the date does not correspond to the requested delivery date you branch firstly to the APO availability check: delivery proposal. You confirm the delivery proposal (for example, one-time delivery, complete delivery or delivery proposal) and go to the sales order entry again in the R/3 System.
You can determine the rule for adopting the results of the availability check in the R/3 System in Customizing for Sales and Distribution in IMG under Basic Functions ® Availability Check and Transfer of Requirements ® Availability Check ® Availability Check with ATP Logic or Against Planning ® Define default settings.
See also:
Reactions to the Availability Check

If you cancel the sales order entry in the R/3 System the temporary objects are deleted.

If plans (or orders) were created, changed or deleted in APO, the new datasets (=results) are stored on the one hand as a date and on the other hand logged as an event in the event channel. That is, the information about the data changed is passed on to the event channel as an event. The event is not the data record itself, rather the link to it. An event always contains information on:
These planned orders are transferred in this case via a direct retransfer to the R/3 System, that is, new events (information about the data changed) are transferred automatically to the R/3 System via the system-defined standard settings in APO. The R/3 System takes the data directly via the event channel or indirectly via a table entry on the R/3 side. The data is extracted from liveCache, converted into interface structures and sent to the respective target system. For newly-created planned orders on the APO side the R/3 System returns the assigned GUID and the external number to APO.
Additional information is available in the integration documentation.
See also:
Capable-To-Promise (CTP)