Ansicht
Dokumentation

EXIT_/SAPAPO/SAPLATPT_005 - Obsolete - APO-ATP: Handling of Data at End of Check

General Material Data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Functionality

In this user exit, data from the ATP check can be changed or stored in the APO database, for example.

It is called at the end of the ATP check, after the display, but before the ATP BAPI shift.

Example

If you want to use the user exit to write ATP check data to the APO database, as soon as the current Logical Unit of Work (LUW) is ended with COMMIT, you should do the following:

• Add a form routine into the function group XATPTUSER that can be called by PERFORM ON COMMIT and in which the requested data is written to the relevant DB tables.

• Insert a routine call by PERFORM ON COMMIT in this user exit. The level is insignificant.

• Set the field SETDELTA to the value 'Y' in the interface parameter CS_ATPGLOBPAR. This means that if the LUW ends with COMMIT, an RFC call takes place from SAP R/3 to APO (function module BAPI_TRANSACTION_COMMIT), that causes an SAP commit in SAP APO. As a result, the call carried out by ON COMMIT is executed by the aforementioned FORM routine and the data is written to the database.

Notes

• No further automatic ATP check takes place in APO after the user exit.

• If the results of the ATP check are changed in this user exit, neither the temporary quantity assignments nor the ATP tree structures are adjusted.

• No SAP commit may be created in the user exit.

Further information

Enhancement APOAT005

Parameters

CS_ATPGLOBPAR
CT_CMPDEL
CT_CMP_CHAR
CT_DELRES
CT_INTREQ
CT_INTREQGRP
CT_INTREQITM
CT_INTRES
CT_INTSUBGRP

Exceptions

INTERNAL_ERROR

Function Group

XATPTUSER

rdisp/max_wprun_time - Maximum work process run time   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 3091 Date: 20240523 Time: 081856     sap01-206 ( 41 ms )