Possible System Landscapes for ATP Check Using SAP APO 

The following system landscapes are possible when you perform the ATP check using SAP APO:

●     Availability Check and Planning in SAP APO

●     Availability Check in SAP APO, Planning in SAP ECC

In theory, it is possible to set up other system landscapes. This topic describes the system landscapes that are possible and those which are not supported.

In the standard system, requirements are posted in SAP APO when the sales order is saved in CRM Online. We strongly recommend that you keep this setting.

You can change this setting in a business add-in (BAdI) in Customizing for Customer Relationship Management under Basic Functions ® Availability Check ® Availability Check Using SAP APO ® Business Add-Ins ® Business Add-In for Posting Requirements in SAP APO.

Of course, regardless of how the BAdI is set, it is always possible to process products in the sales order that are not relevant for ATP check.

 

The following system landscapes are supported:

System Landscape	Requirements posted in SAP APO when the sales order is saved...	Remarks
ATP check in SAP APO	...in CRM Enterprise	supported
ATP check in SAP APO	…in SAP ECC	supported
ATP check in SAP ECC	…in SAP ECC	The following restrictions apply: ●     Automatic confirmation by SAP ECC is not allowed. ●     The confirmation schedule lines are not transferred back to CRM Enterprise. Therefore, inconsistencies between CRM Enterprise and SAP ECC are likely to occur. The following settings must be made: The requirements must be posted by the replicated order in SAP ECC. You can find more information on this under Availability Check in SAP APO, Planning in SAP ECC The SAP APO release should not be specified. (This setting is located in the IMG for Customer Relationship Management under Basic Functions ® Availability Check ® Availability Check Using SAP ECC ® Define Middleware Parameters: Availability Check Using SAP ECC). Set Up Logical Systems and RFC Connections, Section In CRM Enterprise, Step 4 explains how the SAP APO release is defined. If this entry is present for SAP APO, you have to remove it.

 

The following system landscapes are not supported:

System Landscapes	Requirements posted in SAP APO when the sales order is saved...	Remarks
ATP check in SAP ECC	...in CRM Enterprise	not supported
ATP check in SAP APO and SAP ECC	...in CRM Enterprise	not supported
ATP check in SAP APO and SAP ECC	…in SAP ECC	not supported

 

We strongly recommend that the requirements are posted in SAP APO by the sales order in CRM Enterprise.

If the requirements in SAP APO are posted by the replicated sales order in SAP ECC, problems and inconsistencies between the systems can result. Under certain circumstances, the ATP check must be triggered manually by the program. One example is when an ATP check is carried out for a sales order in CRM Enterprise and then locked for transfer. When it is unlocked and changed at a later stage, any changes in requirements are not transferred to SAP ECC, which could lead to inconsistencies with the previous ATP check.