Ansicht
Dokumentation

EXIT_SAPLEINN_003 - Customer Enhancements for IDoc-Processing for Contracts (Inbound)

EXIT_SAPLEINN_003 - Customer Enhancements for IDoc-Processing for Contracts (Inbound)

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

Functionality

This function module is a user exit within the framework of inbound IDoc processing for contracts. The customer has the option of invoking this function module to populate fields on the screens to be processed during the standard creation of the batch input session for posting a contract. This may be the case, for example, if the customer transmits additional data in the IDoc to that provided for in the standard system.

The user exit enables the data to be posted. The function module is invoked prior to exiting a screen. At this point, the customer can populate fields that are not populated in the standard system. When the function module is called, IDoc data is passed on (control record IDOC_CONTROL and the data records IDOC_DATA). You can tell from the message category (field IDOC_CONTROL-MESTYP) whether a new contract is involved (message category BLAORD) or a change to an existing one (message category BLAOCH). The field string EKKO_DATA contains the document header data, whereas table EKPO_DATA contains the data on the document items. Data on the item currently being processed is contained in the header string for table EKPO_DATA..

Table BDC_DATA contains the data on the batch input session.

When a new contract is created, the user exit is invoked on the following screens: header data - 200 and 201, item data - 211 and 212. All screens are from the module SAPMM06E.

When a contract is changed, the following screens are processed: header data - 205 and 201, item data - 211 and 212. All screens are from the module SAPMM06E.

The number of the screen currently being processed is passed on in the parameter DYNPRO_NUMBER and the module name in the parameter PROGRAM.

If the item currently being processed already exists in the system, the parameter ITEM_EXIST is set to 'X'. If the item being created is new, the parameter ITEM_EXIST has the content SPACE.

If an error occurs, so that no further processing is possible, the parameter SUBRC must be set to '4' and the error message should be passed on in the field string ERROR_MESSAGE. In this case, error handling is triggered for the intermediate document.





Parameters

BDC_DATA
DYNPRO_NUMBER
EKKO_DATA
EKPO_DATA
ERROR_MESSAGE
IDOC_CONTROL
IDOC_DATA
ITEM_EXIST
PROGRAM
SUBRC

Exceptions

Function Group

XM06

BAL Application Log Documentation   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 2550 Date: 20240523 Time: 081820     sap01-206 ( 68 ms )