Definition of Terminating Events of Task (SAP Library

Definition of Terminating Events of Task

Use

This function is used to define the terminating events of the task.

Tasks that refer to an asynchronous object method must always be defined with at least one terminating event. At runtime, the relevant work item is only terminated if one of the defined terminating events occurs.

Tasks that refer to a synchronous object method can also be defined with terminating events. At runtime, the relevant work item is generally terminated when the synchronous method has been successfully executed. But the work item is also terminated if one of the defined terminating events occurs.

Whether a method is defined as synchronous or asynchronous depends on its implementation in the Business Object Builder.

The terminating events of a task express the possible end statuses of the task.

A terminating event always refers to one object for which the event must be triggered. You define the object for which the event must be triggered in a container element in the task container.

The event DELETED of object type BUS2032 is defined as a terminating event for a task. At runtime the sales order 123456 is passed via the task container. The task is now only terminated if the sales order 123456 is deleted and the event BUS2032.DELETED triggered. If another sales order is deleted, the task is not terminated.

Integration

If the task is used as a step in a workflow definition, you can go to a separate modeling branch when the event occurs. For further information, refer to Maintenance of Tab Page Outcomes

The task Release budget has the terminating event Budget cancelled.

If a task is terminated by an event, the execution of the workflow is continued. The method does not necessarily have to have been executed. If a task is aborted or non-defined processing statuses arise, the work item is not terminated since no event is created. The workflow is not continued.

Activities

You maintain the terminating events on the tab page Terminating events.

You identify the event by specifying its instance ID and object type. The event must be defined for this object type.

If you are looking at a task in display mode, whose original system is not the current system, you can create additional terminating events. This creates an extension of the task definition.

You specify a container element of the task container, which at runtime contains a reference to the object for which the event has occurred. This is generally the task container element _WI_Object_ID .

The workflow system enters the instance linkage required into the linkage table automatically after the task is started.

If you want to check the properties of the terminating event, select . The properties of the instance linkage are displayed and can be changed.

If you change the properties of terminating events, all terminating events that exist for this task in the workflow system are affected by the change. Therefore do not change the indicator for activation of the event.