Ansicht
Dokumentation

/SAPTRX/EH_ADDEVENTMSG_02 - Post event message(s) to the Event Manager -- SCM 5.0

RFUMSV00 - Advance Return for Tax on Sales/Purchases General Data in Customer Master
This documentation is copyright by SAP AG.

Functionality

You can use this function module to send event messages to SAP Event Management (SAP EM) allowing parallel processing. Event messages are used to communicate event-related information from any source, for example, a tracking service provider, a carrier, a customer, and so on, to SAP EM.

Prerequisites

You need authorization to send event messages. This authorization is given by the system administration via transaction /SAPTRX/TSC0AUTHSND, where the code set code ID for the authorized senders must be maintained. 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 it is saved to the database, and processed further by SAP EM.

At least the following data must be contained in the header table:

The event identification

The tracking IDs that identify the event handler

Sender data for the authorization check

Date and time

Parallel processing of event messages is only possible if at least one of the following input variables is filled:

RFCSERVERGROUP (name of RFC server group)

PACKAGE_SIZE (number of messages processed in one logical unit of work)

PBT_WPS_TO_USE (number of work processes)

Input Parameters

SIMULATE

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

BLOCKONERRORIN

You use the optional input indicator BLOCKONERRORIN to block processing if the event message has invalid data. Only event messages with valid data are processed. Possible values are X (true) or blank (false).

SKIPCHECK

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 messages. Possible values are X (true) or blank (false).

SYNCHRONOUS

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

BUFFER_MODE

You use the optional input indicator BUFFER_MODE to control the buffering of the event message. The event messages are saved to the database but not processed. Possible values are:

Blank (default)

Customizing tables are checked to determine whether the event messages must be buffered.

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

No event messages are buffered. There is no check in the Customizing tables. Using this indicator can improve the performance because database table checks are avoided.

EH_GENERATION_MODE

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

Blank (default)

Customizing tables are checked to determine the event handler generation.

All event messages generate event handlers. 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 entered in the variable EH_GENERATION_FUNCTION

No event messages generate event handlers. There is no check in the Customizing tables. Using this indicator can improve performance because database table checks are avoided.

EH_GENERATION_FUNCTION

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

PREPROCESS_MODE

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 module. Possible values are:

Blank (default)

Customizing tables are checked to determine the preprocessing.

All event messages are preprocessed. 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 entered in the variable PREPROCESS_FUNCTION. Using this indicator can improve performance because database table checks are avoided.

PREPROCESS_FUNCTION

You use the input variable PREPROCESS_FUNCTION to specify the name of the function module used to generate event handlers in cases where the indicator PREPROCESS_MODE has value A.

RFCSERVERGROUP

You use the optional input variable RFCSERVERGROUP to specify a valid server group in which all the work processes that are used for sending event messages run.

PACKAGE_SIZE

You use the optional input variable PACKAGE_SIZE to define the number of event messages processed in one logical unit of work (LUW).

PBT_WPS_TO_USE

You use the optional input variable PBT_WPS_TO_USE to define the maximum number of work processes that the system uses to process all the event messages sent by one call of this function module.

Output Parameter

ERROROCCURRED

The indicator ERROROCCURRED shows that processing has been stopped because of syntax errors. It can only be returned if the optional input indicator BLOCKONERRORIN has been set to true (X). Possible values are X (true) or blank (false).

Parameters

BLOCKONERRORIN
BUFFER_MODE
EH_GENERATION_FUNCTION
EH_GENERATION_MODE
ERROROCCURRED
EXTENSIONIN
EXTENSIONOUT
PACKAGE_SIZE
PBT_WPS_TO_USE
PREPROCESS_FUNCTION
PREPROCESS_MODE
RETURN
RFCSERVERGROUP
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

ROGBILLS - Synchronize billing plans BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.

Length: 11922 Date: 20240419 Time: 035319 sap01-206 ( 125 ms )