Ansicht
Dokumentation

MWMTO002 - Enhancements at end of transfer order confirmation

With this user exit, you can update your own data at the end of the transfer order confirmation.

The customer is performed at the end of function module L_TA_QUITTIEREN in SAPLL03T. This means that the source code can run both asynchronously in the update program and online. For this reason, all error messages must be issued as abend messages to guarantee a correct termination with rollback. Furthermore, you must not use any key words such as COMMIT WORK, ROLLBACK WORK, LEAVE, or the like (neither directly nor indirectly when calling other function modules). Therefore, you must never start a transfer order creation via a function module. If the call is performed asynchronously, you cannot access data of other user exits of the TO processing there were collected online.

The user exit in the program is function module EXIT_SAPLL03T_002. In order to be able to use the user exit, you must create Include ZXLTOU02 and activate the enhancement with transaction CMOD. As parameters, you can use the TO header (import parameter I_LTAK_VB) and the items (table parameter T_LTAP_VB). All database changes due to the transfer order have already been performed. The TO items to be confirmed are confirmed. With the switches PQUIT and PQUIA, you can determine the items that were confirmed because of this update call.
T_LTAP_VB-PQUIT = ' ' => THe item is not yet confirmed.
T_LTAP_VB-PQUIT = 'X' => The item is confirmed.
T_LTAP_VB-PQUIA = ' ' => The item has not yet been confirmed.
T_LTAP_VB-PQUIA = 'X' => The item has already been confirmed
before.
With this user exit, you can update your own tables or trigger follow-up actions. Although changes to table T_LTAP_VB are without any meaning, they should still not be made.