USEREXIT_DELETE_DOCUMENT This user-exit can be used to delete data in additional tables when a sales document is deleted.

This form is called in dialog at the end of form BELEG_LOESCHEN For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted. The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN. When a delivery is deleted, you can delete your own dependent data using this FORM routine.

http://www.bravotube.net/videos/foreign-brunette-teen-gets-fucked-by-tutor/ Call The FORM routine is called from FORM routine BELEG_LOESCHEN (SAPMV50A) when the document can be deleted completely. Immediately after FORM routine USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database.

Data access You can access the delivery data that has already been deleted logically within the FORM

routine: Structure LIKP contains the delivery header to be deleted.

The internal table XLIPS contains the current status of the items to be deleted, including the last changes made by the user before the deletion. All items have the change indicator 'D'. The internal table YLIPS contains the database status of all delivery items in this special case. The internal table for the item status XVBUP does not contain any items of the current delivery anymore, the database status of the item status can only be determined from the internal table YVBUP. In the internal table for the header status of the delivery XVBUK there is also no entry anymore for the current delivery. The current status information (database status) can be taken from table YVBUK. The internal table with the partner data XVBPA is also empty. The database status of the partner data is in the internal table YVBPA. The internal tables of delivery processing must not be manipulated in this exit under any circumstances so as to avoid data inconsistencies. Output of messages The output of error messages and user dialogs is only possible with restrictions in FORM routine USEREXIT_DELETE_DOCUMENT. No messages of type E or W can be output. This results in runtime error DYNPRO_MSG_IN_HELP as of Release 4.0. Other notes The deletion of the delivery can no longer be prevented at this point by returning to the dialog, since all the delivery data has already been deleted logically. If the deletion of the delivery has to be prevented by the user for certain reasons, an error message of the type A should be output