Using this simple assignment of predecessor and successor activities, you may also define forks, joins, and even loops, and they will be displayed correctly in the process diagram. If you do not define the sequence flow, the process is displayed in a default order.
Note: The sequence flow in the process definition does not represent the order in which activities are actually executed, however, it does describe a best-practice order for the activities that you then use in the process instance diagram to visualize the process’s progress.
In the Process Viewer (POC_VIEWER), you can select the ‘Process Diagram’ button to visualize a process definition with its defined best-practice flow. The diagram itself is opened in a Web Dynpro browser window. Start steps and end steps are also marked.
In the Process Monitor (POC_MONITOR) you will now find an ‘Instance Diagram’ button. By choosing it, you will find a projection of the process log to the best-practice process flow, as defined earlier. Already executed activities are marked with green, non-executed activities are still grey. The executed activities contain detail information, such as the ID of the object, the date of execution, and the involved user. All-in-all, this gives you a quick overview of the progress of a process’s execution.
Technically, the visualization requires the installation of SAP jNet frontend component on the display client, which itself is based on Java. jNet can be installed using the SAP frontend installation tools.
Besides calling this visualization from the Process Viewer or the Process Monitor, the visualization can also be used as a side panel in SAP Business Client, and as such it can be linked to a normal business transaction, such as VA03, and visualize the process flow next to the normal business transaction for the business user.
The visualization functionality is available from SP08 of SAP Business Suite Foundation 7.31 (this is ERP 6.0 EhP 6 SP08), shipped mid-2013 or in higher releases. For more information, see note 1853507.
I hope you enjoy this little piece of code that enriches the functionality of Process Observer.