null

Skip to end of banner
Go to start of banner

Troubleshooting - Process flow

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Process status is erroneous

Check the error message in the widget “Problem solving”. If the widget is hidden in the process overview, it must be activated via the layout. The steps vary depending on the error. Common errors are:

Status change error on the main object.

The status change on the main object was not possible. If this is a temporary error (e.g. lock error), processing continues automatically. However, the status change can also be performed manually in the widget. If a different error (e.g. incorrect data or incorrect successor status) occurred, the problem must be corrected manually. There are two ways to do this:

  1. Bring the object in a state where the status change can be executed and execute the status change in the widget “Problem solving”.

  2. Manually bring the object to the target state and ignore the status change in the widget “Problem solving”.

You may need to fix subsequent errors or restart the process in the widget “Problem solving“ after performing the status change.

Process is not continued

If an activity is connected and the process does not continue, the reason may be that the SAP Business Workflow associated with the activity was not completed.

This can happen if the work item was locked during processing. In this case, there is a corresponding event for the work item in the event queue.

Check whether there is a "FINISHED" event for the activity (object type /PCH/CL_BPF_BO_RACTIVITY) in the event queue for processing. If the system is set up correctly, pending events are checked and processed cyclically if the work item concerned is no longer locked. No further steps are necessary. If the event is not processed, the background job for processing the event queue may not be activated.

The process continues as soon as the event is processed and the work item is set to completed. Optionally, you can have the user exit the transaction so that the lock is removed and manually deliver the events to the event queue browser.

  • No labels