Event 

Definition

An event is an incident that has occurred.

Examples of events include:

●      Production start

●      Delivery at the customer

●      Delayed arrival of a truck

●      Damage to a delivery

Use

●      SAP Event Management can point out critical situations within your supply chain in good time, by comparing expected events with the actual events, and can then, for example, actively notify those persons involved.

●      You can use SAP Event Management to make your supply chain measurable. When processing event messages SAP Event Management checks if expected events have been met, and applies quality characteristics for execution and reporting habits.

●      You update the status of the business process that you are monitoring in SAP Event Management so that it can send current information (for example, about the production level) in response to queries (see Event Reporting).

●      You use events in the application system to define whether changes to application objects or processes are relevant to supply chain event management (SCEM-relevant).

For more information about using events in the application system, see Event in the Application System.

Event Categories

You can assign events to three different categories that allow you to monitor and evaluate the supply chain:

●      Regular event
The event occurs within the expected time (for example, the punctual arrival of materials).

●      Overdue event
The event does not occur within the expected time (for example, the late arrival of a service provider).

●      Unexpected event
The event occurs, but it was not planned (for example, traffic jam, production stop, change of route for a service provider).

The following figure provides an overview of the three event categories and the life cycle of an event handler:

Event Reporting

When reporting events you differentiate between:

●      Events that have been reported

(regular, premature, delayed, and unexpected)

●      Events that have not been reported (overdue)

Until the planned end time is reached, no information about whether the actual event has occurred is available for unreported events.

The following are possible reporting combinations for the event and the event message:

●      Event message

○       Regular (event reported)

■       Regular (event occurred)

■       Premature/delayed (event occurred)

○       Premature/delayed (event reported)

■       Regular (event occurred)

■       Premature/delayed (event occurred)

●      No event message

○       On schedule (in order according to time schedule) and not expected (unexpected event has not yet occurred)

○       On schedule (in order according to time schedule), but expected (event and event message)

○       Overdue (as far as is known, the event has not yet occurred, the event message has not yet been sent)

You can send actual events to SAP Event Management in the following ways:

●      You enter the data directly in the application system (for example, document processing).

●      You enter the data manually in SAP Event Management.

●      You enter the data externally and report in the Internet or using EDI, for example.

Planned events are reported to SAP Event Management or determined in the following ways:

●      The application system sends the data to SAP Event Management.

●      SAP Event Management determines the data itself.

For example, you define the time for an expected shipment start to be two hours after loading end.

●      External partners report the data.

For example, a tender is sent to a service provider who cannot complete the order for the required time, but instead for a later time. Since the service provider has the appropriate authorization, he or she can overwrite the expected events that are defined in SAP Event Management with the new data.