Event Simulation (SAP Library - Roles in Workflow)

Event Simulation

Use

The creation of an event is simulated and the result specifies which tasks and workflows would be started as receivers of this event.

Prerequisites

Authorization

You require appropriate authorization for the functions shown. This is the authorization (authorization object S_PROGRAM) for executing a program for authorization group SWU_DIAG.

Features

The result of the test also shows whether errors were diagnosed in connection with the simulated start of the task, which may result in the task or workflow not being started.

The respective error causes are designated with a letter. The legend can be consulted for an short explanation of the error causes. The most common error causes are:

There is no workflow definition for the workflow to be started (error cause a).
The workflow is not activated (error causes b, c).
The linkage between the triggering event and the task or workflow has not been activated (error cause e).
The binding definition from the event container to the workflow or task container has errors (error causes h, i). The task or workflow may nevertheless be started but will probably not be processed as expected.

To remove the error in all of the above cases, position the cursor on an entry and choose Goto ® Task. This takes you to the definition of the workflow or task in question, where you can take appropriate measures.

You activate workflows in the Workflow Builder.

The linkage between the event and the task/workflow is entered in the linkage table but the task does not exist (error cause g).

This error occurs if you delete a task/workflow defined with triggering events. You must then use transaction SWE2 to process the type linkage table manually and delete the relevant entry.

The linkage between the triggering event and the task/workflow to be triggered has been created for the task/workflow, but has not been entered in the linkage table (error cause d).

This error indicates an inconsistency between two tables. Call the task/workflow (Goto ® Task) and save it again.

The actual execution of the task to be started still depends on a check function module being run without errors. It therefore cannot be finally assessed at this point (error cause f).

Calls with errors or non-executable calls to tasks/workflows can, for technical reasons, also affect other calls, which may themselves be successful (error causes j, k).

Activities

Executing simulations

Choose Tools ® Business Workflow ® Development ® Utilities ® Event ® Simulate event to simulate an event.

Describe the event to be triggered with object type and event ID.

Choose

to simulate the event.

You can also simulate an event directly from a step of the type event creator .