Troubleshooting - Process Start

If errors occur in connection with the process start, there are different analysis approaches to isolate the problem.

The architecture of ProProcess provides for a process (ProNovia data) and an SAP Business Workflow at runtime, both of which are automatically synchronized by events. In principle, problems can therefore be caused by the ProNovia processes, the SAP workflows and the interface between them. However, the ProProcess implements various checks in order to exclude a large number of errors.

The following analysis is basically constructive. The individual conclusions and measures are based on the fact that the previous steps have been checked and all proposed actions have been carried out.

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.

A list of all transported workflow templates and the corresponding status is then displayed (see also note 802797). If the workflow does not exist or is red, this indicates a problem with the transport of the workflow. The corresponding transports may have to be imported (again). If the entry is yellow, the workflow may have to be reactivated manually. The RSWDACTIVATE report is available for this purpose (see also note 1027175).

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.

Open	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).

Open	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.

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.

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.