Executing Embedded Processes
Purpose
At runtime, the system creates a runtime version from the definition of the embedded process; this runtime version can then be executed. An embedded process usually comprises steps that are executed automatically in the background by the system, or steps that are executed by the responsible users. These steps are represented by work items at runtime.
Use of the Process
This process is part of the following IT scenarios:
IT Scenario |
Scenario Variant |
Prerequisites
You have fully defined and configured the embedded processes so that they can be executed.
Process Flow
The following IT process applies to the usage type AS ABAP:
1. System executes a status change.
Depending on the way it is defined, an embedded process can be started either manually by a user or automatically by the system. For the process to start automatically, there must be a status change in the system, for example, when a material is created.
2. System triggers event.
The status change in the system triggers an event. This is the ‘signal’ to start the process.
3. System creates process instance.
The system creates a process instance for the process definition that the start event is assigned to; this process instance is then executed.
4. System creates work item/task.
The system produces work items. These represent a step in the process definition, or a task. Depending on their type, work items are either executed in the background or sent to the responsible user for processing. This process only describes the work items that are executed by the system. For more information about work items that are executed manually by users, see the business task management scenario documentation.
Result
The system has started the embedded process and created the relevant work items.