Ansicht
Dokumentation
Changed ATP Tree Structure Data Model (enhanced) ( RELNAPO_310_ATP_BF_03 )
PERFORM Short Reference RFUMSV00 - Advance Return for Tax on Sales/PurchasesThis documentation is copyright by SAP AG.
Short text
Changed ATP Tree Structure Data Model (enhanced)
Use
The data model of the ATP tree structure has been fundamentally enhanced for 3.1. Therefore ATP tree structures that possibly exist can not be transferred after a release upgrade from SAP APO 3.0 to SAP APO 3.1.
This release information describes the prerequisites and actions to be carried out with regard to the component Global ATP for a release upgrade from SAP APO 3.0 to SAP APO 3.1, if you are using ATP tree structures in one of the following scenarios:
- Cross-system third-party order processing (ALE) using persistent temporary quantity assignments (see also persistency indicator)
- ATP check from a connected SAP CRM system (up to and including SAP CRM 3.0) using persistent temporary quantity assignments
Effects on Existing Data
Depending on the scenario, you carry out the following actions:
- Backorder processing
- No open backorder processing (that is, backorder processing that is not yet updated) can be transferred and updated later in release 3.1. For that reason, all existing backorder processings should be deleted. From the SAP Easy Access screen select Global ATP -> Backorder Processing -> Delete Backorder Processing. Leave all selection fields initial and deselect the Test indicator.
- Cross-system third-party order processing (ALE)
- All ALE third-party processes must be completed. The sales order in the sales system must be saved and created completely in the delivery system and updated. In this regard, order IDocs that are not yet transferred or are stopped must be sent before the release upgrade. Otherwise, the order loses its ATP confirmation in the delivery system.
- CRM scenario
- All orders in SAP CRM for which an ATP check has been carried out in SAP APO must be saved and transferred to the connected system and updated there. In this regard, orders that have not yet been transferred must be sent before the release upgrade. Otherwise the order acquires no ATP confirmation in the OLTP system.
All ATP tree structures that still possibly exist must then be deleted. Select transaction SE38 and enter the program name /sapapo/dm_atree_remove_trees. Leave all selection fields initial and execute the report.
The preparations for the release upgrade with regard to the ATP tree structures are thereby completed.
Effects on Data Transfer
Effects on System Administration
Effects on Customizing
Further Information
Fill RESBD Structure from EBP Component Structure Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 3402 Date: 20240427 Time: 025136 sap01-206 ( 63 ms )