Expected Event Reporting 

Use

By reporting events you can:

●     Forward information in a timely way to all partners involved in the business process

●     Check if the partners involved in the business process keep to planned or agreed deadlines

You use this function within an implementation project as an additional means to report the following for an expected event to SAP Event Management (SAP EM):

●     Date

●     Time

●     Time zone

●     Status reason (for example, recipient not available)

Transaction /SAPTRX/MI02 is not found in the SAP Easy Access screen. Instead, you call it up directly in the system.

Prerequisites

●     SAP EM has created event handlers.

●     SAP EM has created predefined expected events (expected event list) for each of these event handlers.

If you have defined a location and location matching for an expected event, the system automatically uses the location of the expected event when reporting this event. Therefore, when you match the expected and the reported locations, the result is always “TRUE”.

For more information about defining expected events, see the Implementation Guide (IMG) for Event Management ® Event Handlers and Event Handler Data ® Expected Events ® Define Expected Event Profiles.

If you have defined partner matching for an expected event, the system cannot apply it for this form of event reporting. In this case, we recommend that you report events using the Web interface.

For more information about defining expected events, see the Implementation Guide (IMG) for Event Management ® Event Handlers and Event Handler Data ® Expected Events ® Define Expected Event Profiles.

Activities

...

...

       1.      Choose transaction /SAPTRX/MI02.

       2.      Specify the following to identify an existing event handler:

                            a.      The tracking ID code set and tracking ID code ID, if they are unique

                            b.      In addition, the service provider tracking ID code set and service provider tracking ID code ID, if the tracking ID code set and the tracking ID code ID are not unique

●      The tracking ID code ID is case sensitive.

●      The tracking ID code set is not case sensitive.

●      You must also specify leading zeros for the tracking ID code ID.

       3.      Choose Go.

       4.      SAP EM determines the expected events that belong to the event handler and displays the following:

○     The internal event code text

○     The predefined location, if required

○     The following for the expected event, if required:

■      Planned date

■      Planned time

■      Planned time zone

○     The following for the event message, if required:

■      Actual date

■      Actual time

■      Actual time zone

       5.      Enter the following to confirm an expected event:

○     Date

○     Time

○     Time zone

○     Internal code for the event reason

You define internal event reasons in Customizing for SAP EM.

For more information about defining internal codes for event reasons, see the Implementation Guide (IMG) for Event Management ® Event Handlers and Event Handler Data ® Codes ® Event Codes ® Define Internal or External Reasons for Events.

The system displays the event reason in the event handler list when you query SAP EM, for example, or you use the event reason within conditions in the rule set of an event handler.

       6.      Select your confirmations.

       7.      Choose Post selected messages.

SAP EM displays a confirmation screen.

       8.      Choose Send.

The system sends the event confirmation to SAP EM.

       9.      SAP EM determines the event handler that belongs to the event message and updates the event handler data.