Expected causes and Solutions when workflow goes to a wrong agent/Not find any agent.

[Former Member]

While working with SAP Workflow, in initial phase most of the time we can see the issues when workitem goes to either to wrong agent or doesn’t go to any agent. This document contains the 8 different causes and their solutions to avoid such issues.

Case 1 .

Run SWU_OBUF and check transaction SWU3 for problems

It is used to synchronize the runtime buffer and check transaction SWU3 for maintaining runtime Environment.

By synchronizing the runtime buffer it synchronizes the version of current workflow .

SWU3 is for Workflow Customizing.

Case 2.  The task has not been set to General Task

               Set the task as General task .

Case 3. The user has a workflow substitute set up for him in table HRUS_D2.

Check the database table HRUS_D2, this might be possible if user has set any substitute for him for a given period of time .

Case 4. The user has been listed as an Excluded Agent for that task.

A pop up will appear if it has not been listed as excluded Agent. Check excluded agents .

　Case 5.   The user is actually expecting an email, not a work item, and the user has an

　　　　　 email substitute set up for him in table SOSU.

                   Check the database table SOSU for this .

Case 6.    If the method is a Dialog method then check the agent hasn’t been set as WF-    BATCH.

                   If Agent is set as WF-BATCH , the workitem will be processed by workflow system itself and No agent will get the workitem .

Case 7.  Check that WF-BATCH has SAP_ALL.

             Go to SU01D and check the Profile.

Case 8.  The agent determination is faulty

          For error free agent assignment, this will look like as shown below (In green status). If status is not green , recreate the agent assignment step .

Hopefully all these points will be helpful while working with SAP Workflow .

Happy learning .

Regards,

Ashish Gaur .