User exit EXIT_SAPMM06E_013 : Updating data in the purchasing document.

Updated May 18, 2018

The user exit EXIT_SAPMM06E_013 to update customer-specific data in the purchasing document is keyed while updating the document prior to the command COMMIT WORK. All the data related to the document update is then transferred.

The purchasing document number which is termed as EBElN is probably not filled in some of the tables that have been transferred through the interface of function module (XEKPO, XEKET). The document number is determined only after these internal tables are created when a purchasing document is created.

The standard system does not provide post-provisioning of the tables that have the documents. Therefore, when a document is created , it is possible that these tables are transferred along with the document number.

Comments

13 Jun 2016 4:58 pm Sonia Barwar Helpful Answer

This can however be regarded as the side effects of various update modules.
When any document is changed, the document number is already known.
In this instance, the subsequent field of the internal tables us populated when the user exit command EXIT_SAPMM06E_013 is keyed in.

13 Jun 2016 4:59 pm Abhijeet Mudgal Helpful Answer

The best way to work around this is to assume that field EBELN is not populated within the internal tables (XEKPO, XEKET).
But if there is a need of this field then, if there is a need it must be keyed in the user exit in the internal tables.
The document number can then be obtained from the import parameter I_EKKO.
A possibility for this is displayed with the example of tables XEKPO and XEKET:
* NUMMER EINKAUFSBELEG SITZT NICHT, NACHTRAGEN
XEKPO-EBELN = I_EKKO-EBELN.
MODIFY XEKPO TRANSPORTING EBELN
WHERE EBELN IS INITIAL.
* NUMMER EINKAUFSBELEG SITZT NICHT, NACHTRAGEN
XEKET-EBELN = I_EKKO-EBELN.
MODIFY XEKET TRANSPORTING EBELN
WHERE EBELN IS INITIAL.