Entering content frameProcess documentation Error Diagnosis Locate the document in its SAP Library structure

Purpose

Typical problems that may arise when you work with the SAP Business Workflow can be diagnosed and remedied. You have the option of analyzing these problems step-by-step using a diagnostic report.

Process Flow

To call error diagnosis, choose Tools ® Business Workflow ® Development ® Utilities ® Diagnosis.

The diagnostic report always operates on a task with errors or which has been causing you problems. Enter the task type (T, TS, WF, WS) and its eight-digit Task number in the relevant input fields.

In the lower part of the screen, you can select from the List of tasks last used.

Workflow Customizing

There is a basic problem if the system settings for SAP Business Workflow were not made or were not completed during Customizing. Before you start error analysis for an individual task, you should make sure that automatic workflow Customizing is not causing any problems.

Select Verify Workflow Customizing to check the system settings and, if necessary, make or change settings.

For more information, see Automatic Workflow Customizing.

Problem: Task is not started

A task that should be started by a triggering event or in dialog has (apparently) not been started because no corresponding work item has appeared in the Business Workplace of the recipient.

Choose Problem: Task is not started. The next screen offers diagnosis options.

Carry out the steps in the order shown, noting the help texts.

You first need to differentiate between the following two error causes using the function Determine instances for task:

In this case, the error was probably caused in event receiver linkage or event creation.

If you can identify a dialog work item (type W) that represents the single-step task started or a step in the workflow, but cannot be seen in a Business Workplace, check the agent assignment ( possible and responsible agents).

If you can identify a workflow work item (type F) that represents the workflow started, but no other work items that represent the individual steps of this workflow, an error has probably occurred that is connected with the internal communication of the workflow system components.

For more information, see Workflow is "hanging".

The individual steps that need to be carried out for diagnosis can often be reached via other menu paths.

Problem: Workflow is "hanging"

The problem here is that a workflow does not run as expected although you know that it has been started. You have either already processed steps in this workflow or you have at least seen the workflow in the selection report.

Choose Problem: Workflow is "hanging". The next screen offers diagnosis options.

Carry out the steps in the order shown, noting the help texts.

You first need to decide whether the problem is the result of errors involving the agent assignment (work item exists but is not visible) or whether it is caused by errors in the internal process control of the workflow system.

Test environment

The test environment contains various useful tools designed to help you with problem analysis.

Note the help texts.

 Leaving content frame