Ansicht
Dokumentation

/SAPTRX/BAPI_EH_ADDEVENTMSG_02 - Post event message(s) to the Event Manager -- SAP EM 4.01

Fill RESBD Structure from EBP Component Structure General Material Data
This documentation is copyright by SAP AG.

Functionality

The event message described in this document is part of SAP Event Management. For more information, see the SAP Help Portal (http://help.sap.com/) -> mySAP Business Suite-> SAP Supply Chain Management-> SAP Event Management.

This method is used for sending event messages to SAP Event Management (SAP EM). Event messages are used for the communication of event-related information from any source, for example, a tracking service provider, a carrier, a customer, and so on, to SAP EM.

Users need authorization to send messages. The authorization is given by the system administrator in transaction /SAPTRX/AUTHSND. Here the sender code set and sender code ID must be maintained for the authorized senders. Only event messages coming from maintained senders are processed.

A set of tables containing the event message data is given to the method as input, the data structure is converted into the appropriate structure of the event message database tables, then saved in the database, and processed further by SAP EM.

The following is the minimum required data contained in the header table:

The event identification

The tracking IDs that identify the event handler

Sender data for the authority check

Date and time

You use the optional input indicator SIMULATE to step through event message processing without updating the database (for test purposes). The possible values are X (true) or ' '(false).

You use the optional input indicator BLOCKONERRORIN to block the processing if the event message contains invalid data. SAP EM only processes event messages with valid data. The possible values are X (true) or ' '(false).

You use the optional input indicator SKIPCHECK to avoid event message validation. This improves performance in all cases where it is not necessary to validate the event messages, for example, machine-generated event messages. The possible values are X (true) or ' '(false).

You use the optional input indicator SYNCHRONOUS to set the synchronous processing mode rather than the standard asynchronous mode. You use the asynchronous mode mostly for debugging and test purposes. The possible values are X (true) or ' '(false).

You use the optional input indicator BUFFER_MODE to control the buffering of event messages. Event messages are saved in the database, but not processed. The possible values are:

Blank

This is the default value. The Customizing tables are checked to determine whether the event messages must be buffered.

All event messages are buffered and there is no check in the Customizing tables.

No event messages are buffered and there is no check in the Customizing tables. You use this indicator to improve the performance by avoiding database table checks.

You use the optional input indicator EH_GENERATION_MODE to control the function of generating event handlers via the event message by means of a plug-in function. The possible values are:

Blank

This is the default value. The Customizing tables are checked to determine the event handler generation.

All event messages generate event handlers and there is no check in the Customizing tables. In this case, the name of the function module used to generate the event handlers must be given in input variable EH_GENERATION_FUNCTION.

No event messages generate event handlers and there is no check in the Customizing tables. You use this indicator to improve the performance by avoiding database table checks.

You use the input variable EH_GENERATION_FUNCTION to specify the function module used to generate event handlers in cases where the indicator EH_GENERATION_MODE has the value A .

You use the optional input indicator PREPROCESS_MODE to control the function of preprocessing event messages (modifications, non-standard checks) by means of a plug-in function. The possible value are:

Blank

This is the default value. The Customizing tables are checked to determine the preprocessing.

All event messages are preprocessed and there is no check in the Customizing tables. In this case, the name of the function module used to preprocess the event message must be given in input variable PREPROCESS_FUNCTION. You use this indicator to improve the performance by avoiding database table checks.

You use the input variable PREPROCESS_FUNCTION to specify the function module used to preprocess event messages in cases where the indicator PREPROCESS_MODE has the value A .

There is only one output parameter: The indicator ERROROCCURRED that shows that processing has been stopped because of syntax errors. It can be returned only if the optional input indicator BLOCKONERRORIN has been set to true (X). The possible values are X (true) or ' '(false).

Parameters

BLOCKONERRORIN
BUFFER_MODE
EH_GENERATION_FUNCTION
EH_GENERATION_MODE
ERROROCCURRED
EXTENSIONIN
EXTENSIONOUT
PREPROCESS_FUNCTION
PREPROCESS_MODE
RETURN
SIMULATE
SKIPCHECK
SYNCHRONOUS
TRACKADDRESS
TRACKCONFIRMSTATUS
TRACKEEMODIFY
TRACKFILEBIN
TRACKFILECHAR
TRACKFILEHEADER
TRACKFILEREF
TRACKINGHEADER
TRACKLOCADDITIONALID
TRACKLOCATION
TRACKLOCATIONDESCR
TRACKMEASURESULTS
TRACKPARAMETERS
TRACKPARTNERADDID
TRACKPARTNERID
TRACKREFERENCES
TRACKSTATUSATTRIB
TRACKTEXTHEADER
TRACKTEXTLINES

Exceptions

Function Group

TRX/SAPLEH_BAPIS

BAL Application Log Documentation General Material Data
This documentation is copyright by SAP AG.

Length: 9926 Date: 20240426 Time: 163237 sap01-206 ( 125 ms )