Definition of Events for an Object Type 

Use

You define events for an object type, if a status change in an object of this type is to be published across the system. Potential event receivers can then react to this event.

You use an event in a workflow under the following circumstances:

The workflow or task is started when the event is triggered.

The task is terminated when the event is triggered.

The event is triggered (event creator) or the workflow is continued when the event is triggered (wait for event).

The event is not normally triggered in the implementation program, but instead by an event creation. You can use the function modules SWE_EVENT_CREATE or SAP_WAPI_CREATE_EVENT to trigger an event.

Integration

An event is published without the creating application being informed as to whether a receiver reacts to this event. The system enters potential receivers in a linkage table, which is evaluated by the event manager. For further information, refer to Event.

Every event has an event container that contains data about the context of its creation. The data is passed to the task or workflow via a binding. For further information, refer to Binding Definitions from the Event Container.

Prerequisites

Before creating a new event, check whether the event is already defined in an interface. If so, include this interface in the definition of your object type.

Activities

To create an event, position the cursor on the name Events (blue background), and select .

Assign an event ID, a name and a description. Bear in mind the rules for naming object type components.

The system always enters the event ID into the event receiver table in upper case regardless of how you wrote it.

Set the indicator Triggering object does not exist if the object has been deleted.

The workflow system elements are in the event container as standard. If the event container is to contain other container elements, you must define parameters for this event. For further information, refer to Definition of Event Parameters.