Show TOC

Background documentationPossible 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 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.

End of the caution.

Prerequisites

You make settings for posting requirements in Customizing for Customer Relationship Management under Start of the navigation path Basic Functions Next navigation step Availability Check Next navigation step Availability Check Using SAP APO Next navigation step Business Add-Ins Next navigation step Business Add-In for Posting Requirements in SAP APO End of the navigation path. 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 Recommendation

Do not change the standard system setting.

End of the recommendation.

Caution 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.

End of the caution.

Integration

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:

  • Automatic confirmation by SAP ERP is not allowed.

  • The confirmation schedule lines are not transferred back to SAP CRM. Therefore, inconsistencies between SAP CRM and SAP ERP are likely to occur.

The following settings must be made:

  • The requirements must be posted by the replicated order in SAP ERP. You can find more information on this under Availability Check in SAP APO, Planning in SAP ERP.

  • Ensure that you do not specify the SAP APO release in Customizing for Customer Relationship Management under Start of the navigation path Basic Functions Next navigation step Availability Check Next navigation step Availability Check Using SAP ECC Next navigation step Define Middleware Parameters: Availability Check Using SAP ECC End of the navigation path. For information about setting up a connection to SAP APO in SAP CRM, see Set Up Logical Systems and RFC Connections. Step 4 in section In SAP CRM explains how you define the SAP APO release. If this entry is available for SAP APO, you must remove it.

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