Process Activity Overview
Aggregated view of the Process Step Journal component of all participating logical systems. The process activity overview contains the combined data of all local Process Activity Logs on the level of a single process step (this means service messages). It also contains additional information as well as the aggregated technical status of all process steps. This means for all service messages that belong to a specific business process ID.
The data contained in the process activity overview is decribed below in detail:
Received
The receiving system has received the service message. The relevant process step is completed from a technical point of view.
In Processing
The process step has not yet been completed.
Obsolete
The completion of the process step is no longer relevant for possible follow-up processes.
Errors in Content
The underlying component could not complete the process step successfully (for example, error handling or service call).
In addition, the process activity overview contains the following specifications for each service message or for each process step:
Business Process ID
The business process ID groups the log entries for all process steps that belong to one cross-system business process together. At the time of evaluation, it enables the identification of log entries that belong together.
Message ID/Process Step ID
This uniquely identifies the process step (service message) on which the log entry is based.
Message ID/Process Step ID of the Predecessor
This contains the ID of the process step that initiated the previous process step. In some cases this information may not be available.
System ID of the Sending System
This identifies the logical system that assumed the sending roll when the service message was transferred to the current process step.
System ID of the Receiving System
This identifies the logical system that assumed the receiving roll when the service message was transferred to the current process step.
Postprocessing Order ID
This exists if the process step is in error handling or if error handling has taken place.
Status History
This contains all log entries for the individual process activity logs with all the details that lead to the existing service message. Using the status history, you can see from which log entries the Process Step Journal derived the technical status of a process step.
The following diagram shows in simplified manner how the Process Step Journal maps the data from the individual process activity logs in the process activity overview.
Case examples for deriving the aggregated process step status for each process step in the process activity overview are as follows:
Example 1: Aggregated Process Step Status Received
Example 2: Aggregated Process Step Status In Processing
Example 3: Aggregated Process Step Status Obsolete
Example 4: Aggregated Process Step Status Errors in Content