cancel
Showing results for 
Search instead for 
Did you mean: 

Weird WF Task behavior on Agent Assignment - Please check attached screen shot

12-22-2019 4:40 PM
SAP Managed Tags
Subscribe

Hi Experts,

I am facing weird situation, please have a look in below steps:

Workitem set to Committed and Confimation column in inbox also set with flag - confirm end of processing either I set it in TASK or not

When I have created new task will all the same bindings with passing same agent table in expression showing error in agent determination while agent determination step is correctly return value...

Not able to know the reason of the error while table AGENT has error -

Thanks,

Saquib

Accepted Solutions (1)

Accepted Solutions (1)

Former Member

Hi Saquib,

1. Does Workflow Log View for TS99400067 look exact same in each row & each workflow step, as TS99400118?

2. You ran both tasks in same system, generating same 3 SAP userids as Agents? same 3 agents in TS99400067? Are all 3 SAP userids assigned to you?

3. Do all 3 SAP userids exist and are active in the SAP systemID(SID)/instance you are running in?

4. Workflow Log: Looks like: row 4: says: "Agent Determination failed"? What else does Workflow Log say? I cannot read the right side of Workflow Log (covered by Display Container pop-up).

5. on row 6, click the Agent Icon (icon of 2 people, 1 gray, 1 green), what will it show? same in TS99400067 workflow log?

6. In your "Dear Approver" screenshot, Purchase Order is not populated here. Is PO populated in TS99400067?

7. so I'm wondering of there may be a delay; consider a wait statement if custom

8. BUS2009 is No Instance. Same for step TS99400067?

9. since your SAP userid is also workflow initiator, is your SAP userid being excluded by both tasks TS99400067 & TS99400118, as an available agent to approve?

10. in TS99400067 workflow view, is workflow exit activated?

Happy New Year.

Answers (1)

Answers (1)

Former Member

Hi,

Please check the agent assignment of the task itself, maybe this is conflicting something.

I also noted the workflow exit part of the technical log, please check the tab Program Exits for this step in the worflow definition.

And finally, try if refreshing the HR buffer solves the problem (SWU_OBUF)

Kind regards, Rob Dielemans