...
| Note |
|---|
Before analyzing, make sure that all steps for setting up ProProcess have been performed as described. These steps are mandatory for operation. |
Analysis of ProProcess process data
If unexpectedly no activities are created or do not end up in an inbox, this does not necessarily mean that no process was actually started. In principle, each time the process is started, data of ProProcess is first generated and only after the process data has been updated is the corresponding event for starting the SAP Business Workflow triggered.
In the first step, you must use ProProcess Reporting to check whether the process was created at all. If this is not the case for processes that are to be started automatically, it can be assumed that the start or autostart conditions are not (completely) fulfilled. If, on the other hand, the process was either started manually or selected during automatic startup, a product error is obvious.
The process status provides further information:
Undefined In all probability, no SAP Business Workflow was started. It is also possible that a workflow was started but stopped immediately with an error.
Incorrect An SAP Business Workflow was triggered, but an unexpected error occurred.
The workflow ID is required for further analysis. This can be determined in the Basic Data . If the status is "Incorrect", you can continue with the analysis of processes with errors.
Analysis of Workflows Not Started
If the problem occurs after an import, a process version may not have been activated or the workflow template may not have been imported correctly. You can use transaction SWDM to display the transported workflows. To do this, the option Transport Workflows must be activated in the Other tab.
...
The process was not started due to inappropriate conditions. This problem only occurs if either the process data or the workflow template is not current. Check whether all data is current.
Analysis of processes with errors
If a process has the status "error", an unexpected error occurred during processing. ProProcess provides tools for troubleshooting. In this way, known problems in particular can be solved semi-automatically (e.g. missing agents). In the case of unknown errors, it is always possible to restart the process. This is also possible via the surface of <%PRODUCTNAME%> with corresponding rights. Alternatively, processes with errors can also be restarted using transaction SWPR.
...