SAP CRM triangle scenario

A sales order is created in an SAP CRM system and the availability check is carried out in SAP APO. When the sales order is saved, data is written to the SAP APO database. An ERP system accesses this data during order creation, after the order has been transferred from the SAP CRM system to the ERP system. If the sales order is saved and updated in the ERP system, the associated data is deleted from the database.

Backorder processing in SAP APO

In backorder processing, the ATP tree structure is written to the SAP APO database as passive . This is necessary, since an order item can be included several times in backorder processing and the result is not updated immediately.

If backorder processing takes place for order items that have been checked within a multilevel ATP check, the data is copied from the passive ATP tree structure into the active ATP tree structure during the update. If backorder processing is deleted, the relevant passive ATP tree structure is also deleted. However, the active one must be available for a later conversion in PP/DS. If this conversion takes place, the active ATP tree structure is also deleted.

Cross-system third-party order processing (ALE)

In this scenario, a sales order (2) is generated using ALE in the delivery system when the sales order (1) is saved in the sales system. When the sales order (1) is saved, an ATP tree structure is created in the SAP APO database. It contains the check results from the ATP check of the sales order (1).

When the sales order (2) is created, SAP APO is called to read the check results stored in the ATP tree structure. The sales order (2) is thereby confirmed.

If the sales order (2) has been updated in the delivery system, the ATP tree structure is deleted.

Multilevel ATP check

For the multilevel ATP check, the data that refers to the checked components is not transferred to the ERP system. The data must be available for the later conversion into procurement proposals in PP/DS. If a conversion has been carried out through PP/DS, the ATP tree structure is deleted.

Rules-based ATP with stock transfer and consolidation

The data for a later conversion into stock transport requisitions must be available for a stock transfer that is processed for a location determination using the rules-based ATP check. If a conversion has taken place, the ATP tree structure is deleted.

If the update is canceled

If the data in the SAP APO database is not deleted

If the system displays performance problems due to the volume of data being too large

You can use the ATP tree structure display, above all, to check how the complex confirmation situation (quantities, dates, substitutions) looks after a multilevel ATP check.