...
The workflow ID is required for further analysis. This can be determined in the Basic dataData . If the status is "Incorrect", you can continue with the analysis of processes with errors.
...
In the next step, you should check whether a corresponding start event has been created. To do this, you can activate an event trace with transaction SWELS and evaluate it with transaction SWEL. All generated events are logged in the trace. In the list, you can search for the process to be started using the receiver type. The receiver type is the workflow ID (see above). If no event is triggered, there is a high probability of a product error. Otherwise, the icon can be used to determine whether the event could be processed.
 | SWW_WI_CREATE_VIA_EVENT_IBF |
The event was processed. Double-click on the entry to display the details. There you can also see if the event is delivered delayed or if an error occurred during delivery. With the administration cockpit for the event queue (transaction SWEAD), the events still to be processed can be monitored. If the system load is high, it can take several minutes until the event is processed, depending on the configuration. If there is no indication of a delay, there may be a product error and the workflow has been started but immediately set to "errored" (see Analysis of Errored Processes).
 | No receiver registered |
The linkage for the process is not active. Transaction SWETYPV should be used to check whether an entry exists for the object category CL, the object type /PCH/CL_BPF_BO_RPROCESS, the events STARTED_AUTO, STARTED_BY_API, STARTED_BY_PROCESS, and STARTED_MANUALLY for the receiver type (see above) and, above all, whether it is active. Missing entries indicate that a transport request is missing. However, if the type linkage is not active, it may have been deactivated automatically due to a system error and must be reactivated manually. The linkage can be reactivated with the transaction SWU0 using the object category CL, the object type /PCH/CL_BPF_BO_RPROCESS and the event STARTED_AUTO.
 | Check-FB with exception of |
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.
...
If the problem cannot be solved either by the automatic problem solution or by a restart, the only option is an analysis by a workflow expert. SAP provides various tools for this purpose. Transaction SWI1 can be used to find and analyze the affected workflow. For each work item, the log can be displayed and technical details can be displayed. In the technical details, you can select the relevant work item and several tabs provide information about any messages, etc.
 | Display log |
 | Display technical details |