Interfaces in SAP Event Management

Use

You use interfaces to send data to and from SAP Event Management, for example:

To send event messages
To get event handler data
To create or update event handlers

In the standard case, this occurs as follows:

The interfaces named below or the user interface send the event messages to SAP Event Management.
The user interface gets the event handler data from SAP Event Management.
The application interface creates or updates the event handlers in SAP Event Management.

You use the available Business Application Programming Interfaces (BAPIs) of the event handler business object (type /SAPTRX/EH) or you use the function modules directly via Remote Function Call (RFC). You can also send event messages, and create or update event handlers using IDocs. You cannot read event handler data using IDocs.

The following table describes the various options that you have to send data to and from SAP Event Management:

Description	IDoc Type	RFC	BAPI
Sending event messages	EVMSTA02	/SAPTRX/BAPI_EHADDEVENTMSG_02	EventHandler.AddEventMessages02
Fetching event handler data	No IDoc available	/SAPTRX/BAPI_EH_GET_DATA	EventHandler.GetData
Creating or updating event handlers	EHPOST01	/SAPTRX/BAPI_EH_POST	EventHandler.PostEventHandler

Note Note

For more information about RFC function modules and BAPIs, see SAP Library on SAP Help Portal:

End of the note.

http://help.sap.com SAP NetWeaver Application Platform ABAP Technology ABAP Programming and Runtime Environment (BC-ABA) External Programming Interfaces RFC Programming in ABAP
http://help.sap.com SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Business Services Enhancements, Modifications … (CA-BFA)

Prerequisites

To use the interfaces, you must have installed the relevant Plug-In versions of the SAP R/3 Plug-In and the SAP Basis Plug-In. Up to PI 2004.1, you must install the relevant SAP R/3 Plug-In separately. If you have installed SAP ECC 6.0, the corresponding functions are available automatically.

For more information about connecting business objects with the relevant Plug-In versions, see SAP Service Marketplace at http://service.sap.com/scm SAP Supply Chain Management Supply Chain Event Management Detailed Information Connecting SAP Application Objects to SAP EM , in the appendix .

Recommendations for Optimizing the Process Flow for Sending Data to and from SAP Event Management

Choosing the input channel

If you use an interface from an SAP system, we recommend that you use the RFC connection as the input channel. Since the BAPI and IDoc implementations are based on the relevant function module that underlies the RFC, an RFC call is the most efficient calling method.

Inputting event messages: setting input parameters

If you have chosen an RFC connection or a BAPI as the input channel for event messages, you can use parameters to control the way messages are processed. The following table provides an overview of the parameters:

Parameter Name	Parameter and Usage Description	Parameter Values	Means of Processing Event Message
SIMULATE	Indicator: simulation mode (system saves event message or does not save event message to database; for test purposes)	(blank) X	No simulation Simulation
BLOCKONERRORIN	Indicator: block processing if syntax error occurs (system only processes event messages with valid data)	(blank) X	Do not block processing Block processing
SKIPCHECK	Indicator: syntax check not performed	(blank) X	Perform check Skip check
SYNCHRONOUS	Processing in synchronous mode instead of default mode (in most cases, for debugging and test purposes)	(blank) X	Asynchronous Synchronous
BUFFER_MODE	Mode for buffering event messages: Controls buffering of event messages (system saves event message to database, but does not process it). The system uses this parameter to check event messages for their relevance to buffering (evaluation in Customizing table). Depending on the evaluation, the system buffers or does not buffer the event message. Only when the evaluation changes does the system also change the type and scope (buffer all or no event messages) of buffering. For more information, see below.	(blank) A N Do not buffer event messages (no check)	Check event messages for buffering Buffer all event messages (no check in Customizing table) Do not buffer any event messages (no check in Customizing table)
EH_GENERATION_MODE	Mode for generating event handlers: The system uses this parameter to check whether event messages are relevant for generating an event handler in SAP Event Management (evaluation in the Customizing tables). Only when the evaluation changes does the system also change the type and scope (all or no event messages generate an event handler) of generating the event handler. For more information, see below.	(blank) A N No generation of event handlers	Check event messages for EH generation Each event message generates an event handler (no check in Customizing table). In this case, you must specify the name of the function module that generates the event handlers in variable EH_GENERATION_FUNCTION. No event messages generate an event handler (no check in Customizing table).
PREPROCESS_MODE	Mode for preprocessing event messages: The system uses this parameter to check whether it preprocesses event messages (evaluation in Customizing tables). For more information, see below.	(blank) A N No preprocessing of event messages	Check event messages for preprocessing Preprocess all event messages (no check in Customizing table) Do not preprocess any event messages (no check in Customizing table)

Parameter Name

Parameter and Usage Description

Parameter Values

Means of Processing Event Message

SIMULATE

Indicator: simulation mode (system saves event message or does not save event message to database; for test purposes)

(blank)

No simulation

Simulation

BLOCKONERRORIN

Indicator: block processing if syntax error occurs (system only processes event messages with valid data)

(blank)

Do not block processing

Block processing

SKIPCHECK

Indicator: syntax check not performed

(blank)

Perform check

Skip check

SYNCHRONOUS

Processing in synchronous mode instead of default mode (in most cases, for debugging and test purposes)

(blank)

Asynchronous

Synchronous

BUFFER_MODE

Mode for buffering event messages:

Controls buffering of event messages (system saves event message to database, but does not process it). The system uses this parameter to check event messages for their relevance to buffering (evaluation in Customizing table). Depending on the evaluation, the system buffers or does not buffer the event message. Only when the evaluation changes does the system also change the type and scope (buffer all or no event messages) of buffering.

For more information, see below.

(blank)

Do not buffer event messages (no check)

Check event messages for buffering

Buffer all event messages (no check in Customizing table)

Do not buffer any event messages (no check in Customizing table)

EH_GENERATION_MODE

Mode for generating event handlers:

The system uses this parameter to check whether event messages are relevant for generating an event handler in SAP Event Management (evaluation in the Customizing tables). Only when the evaluation changes does the system also change the type and scope (all or no event messages generate an event handler) of generating the event handler.

For more information, see below.

(blank)

No generation of event handlers

Check event messages for EH generation

Each event message generates an event handler (no check in Customizing table).

In this case, you must specify the name of the function module that generates the event handlers in variable EH_GENERATION_FUNCTION.

No event messages generate an event handler (no check in Customizing table).

PREPROCESS_MODE

Mode for preprocessing event messages:

The system uses this parameter to check whether it preprocesses event messages (evaluation in Customizing tables).

For more information, see below.

(blank)

No preprocessing of event messages

Check event messages for preprocessing

Preprocess all event messages (no check in Customizing table)

Do not preprocess any event messages (no check in Customizing table)

We recommend that the system processes event messages in the asynchronous mode (SYNCHRONOUS indicator has the default value blank ).

If you set the indicator for buffering event messages, generating event handlers, or for preprocessing event messages to N , you can improve performance. In this way, you avoid the system reading unnecessary database tables. To do this, you must know at least one of the following for your event messages:

That they do not need buffering
That they do not generate event handlers
That they do not need special preprocessing functions

If you set the SKIPCHECK indicator to X , you can improve performance. To do this, you must ensure that your event messages do not contain any syntax errors.

Sending a large number of file attachments with event messages can lead to problems with archiving data. In this case, we recommend that you save the files to hard disk rather than the database (transaction /SAPTRX/TSC0MBF).

You can define that SAP Event Management processes event messages using inactive event handlers (transaction /SAPTRX/TSC0MBF). This can lead to inconsistencies when you archive event messages. You can avoid these inconsistencies by ensuring that such event messages only reach SAP Event Management if the corresponding event handler has not yet been deleted.

Note Note

For more information about saving event messages to the hard drive and processing event messages using inactive event handlers, see SAP Service Marketplace at http://service.sap.com/SCM SAP Supply Chain Management Supply Chain Event Management Detailed Information SAP EM 4.0/4.1 Event Message Input.

End of the note.

Inputting event messages: mass processing

If you work with a large number of event messages, we recommend that you call an RFC connection for entire packages of event messages instead of one RFC connection for each individual event message. In this way, you can improve system performance.

If you work with particularly large packages, we recommend that you use parallel processing.