Start Event

The start event starts the flow of the process and thus does not have any incoming sequence flow. The start event in the process composer has a trigger that indicates how the process starts. This trigger is a message. Every process has one start event.

Intermediate Timer Event

An intermediate timer event occurs after a process has been started. It affects the flow of the process, but does not start or terminate the process. The intermediate timer event shows where the process pauses and waits for a certain time to pass before resuming.

End Event

The end event indicates where a process ends. It ends the flow of the process, and thus, does not have any outgoing sequence flow. An end event in the process composer can have a specific result, for example a message. A process can have only one end event whose result is a message. All tokens need to be caught.

Termination Event

The termination event also ends the process flow as the end event. It ends the process flow in a regular way. If a branch in the process reaches a termination event, all parallel flows in the process are also terminated. Only one token needs to be caught. A process can have an end event or a termination event but not both. Only one of these end events is allowed.

Error End Event

You use error end events to model an error that occurs in the process. There can be several error end events in a process. You need to set an error type for the error end event. The error represents the exception, which may be critical or non critical. The exception is thrown from inner sub-process to the next outer process until the exception can be handled by an exception handler. If no exception handling is possible for a critical exception, the sub-process is suspended. It is suspended until the exception can be handled by a boundary event which is placed on the boundary of the sub-process flow object in your process. Boundary events can also be placed on the boundary of a human or automated activity to handle errors in tasks or faults in the automated activity. The process flow continues from the boundary event.

If a critical exception cannot be handled in the whole process, the process remains suspended. You can analyze the error in the SAP NetWeaver Administrator.

Boundary Event

You use boundary events for exception handling. Boundary events are always assigned to an activity. You place them on the boundary of an activity (automated activity, human activity or sub-process). The boundary event handles an exception that has occurred while the activity has been performed. A sequence flow connection starting from the boundary event shows how the process branches after the exception.