Dispatching to Users
Purpose
An integration process can send a message to a Business Workflow and thereby either start or continue the Business Workflow. The Business Workflow can create work items that the responsible user can then process in the Universal Worklist of the Enterprise Portal, for example.
Use of the Process
IT Scenario |
Scenario Variant |
Prerequisites
The receipt of a message has started the integration process.
Process Flow
1. System monitors exceptions and deadlines (PI).
You can allow for possible exception situations when you define an integration process. Examples of such exception situations might be a missing material, or an exceeded limit value. You can define which steps are to be executed when a particular exception occurs in the process definition. At runtime, the system checks whether an exception situation has occurred and, if applicable, executes the steps defined in the definition correspondingly.
Similarly, you can also incorporate deadlines in the definition of the integration process. You can specify the time and date by which the process must be executed, and define which steps are to be executed if the deadline is missed. At runtime, the system checks whether any deadlines have been missed and if applicable, executes the steps defined in the definition.
The reaction of the system due to an exception or missed deadline might be to terminate the process or to continue it in a different processing branch.
2. System sends message (PI).
The integration process sends a message to the relevant Business Workflow. The Business Workflow receives and processes the message.
3. System creates work item/task (AS/ABAP).
The workflow is processed further when the message is received and the system executes the steps defined in the definition. The receipt of the message can trigger the creation of a work item, for example.
Result
The system has created a work item. This can be displayed and processed by the responsible user.