Possible System Landscapes for ATP Check Using SAP APO
The following system landscapes are possible when you perform the ATP check (availability check) using SAP APO:
Caution
The function for availability check in SAP APO and planning in SAP ERP has been superseded by availability check and planning in SAP APO.
You make settings for posting requirements in Customizing for Customer Relationship Management under . In the standard system, requirements are posted in SAP APO when sales orders are saved in SAP CRM. Of course, regardless of how the BAdI is set up, it is always possible to process products in the sales order that are not relevant for the availability check.
Recommendation
Do not change the standard system setting.
Caution
If the requirements in SAP APO are posted by the replicated sales order in SAP ERP, problems and inconsistencies between the systems can result. Under certain circumstances, the availability check must be triggered manually by the program. For example, when an availability check is carried out for a sales order in SAP CRM and it is then locked for transfer. When it is unlocked and changed at a later stage, any corresponding changes in requirements are not transferred to SAP ERP, which could lead to inconsistencies with the previous availability check.
The following system landscapes are supported:
System Landscape |
Requirements Posted in SAP APO When Sales Orders are Saved in This System |
Remarks |
|---|---|---|
Availability Check in SAP APO |
SAP CRM |
Supported |
Availability Check in SAP APO |
SAP ERP |
Supported |
Availability Check in SAP ERP |
SAP ERP |
The restrictions are as follows:
The following settings must be made:
|
The following system landscapes are not supported:
System Landscape |
Requirements Posted in SAP APO When Sales Orders are Saved in This System |
|---|---|
Availability Check in SAP ERP |
SAP CRM |
Availability Check in SAP APO and SAP ERP |
SAP CRM |
Availability Check in SAP APO and SAP ERP |
SAP ERP |