SRM Process Controlled Workflow Issue - Process Level Agent not shown up

[Former Member]

System: SRM 7.0 (SP09)

Implemented BADI to determine agents at process level - BADI Definition /SAPSRM/BD_WF_PROCESS_CONFIG

Configuration: 1 Process Level (Seq 100, Lvl Type A, Resp. Resolver Name: Z_XXXXXX, Task ID 40007954, Decision Type 1)

When creating the Shopping cart based on the cart value, the agents are determined correctly and process level GUID is created with Agent ID associated.

something like

GUID1 - APPR1

GUID2 - APPR2

GUID3 - APPR3

GUID4 - APPR4

Before "Order" when we do preview of Approval Process, it shows all the approvers in the sequence as expected. As soon as the cart is ordered, the first process level GUID lost its agent thus throwing error saying "Strategy Z_XXXXXX did not determine any approver"

But when we look at the table /SAPSRM/D_WF_016, the corresponding entires of GUID1 has the agent ID as APPR1.

The task 40007954 has been GENERALIZED so as the master workflow template 40000014. The same is working in our Dev system but throwing error "Strategy Z_XXXXXX did not determine any approver" in QA system.

Any input is highly appreciated.

[former_member578547]

Hi Prabhu,

Specify the break point and , can you analyze the issue.

Other way, indeed, we configured our SCHEMA in /SAPSRM/WF_PROCESS Transaction with our BRF functionality.

Any way, i will do as you did and come back .

Thanks,

balaji.T.

[Former Member]

See the thing is the agents were picked up & saved in the table /SAPSRM/D_WF_016 in the process level BADI. The first process level guid doesn't get processed in the RESP_RESOLVER BADI. I put the break point and can see the agents were picked up & saved in Process Level BADI.

The funny part is it is working just fine in the Dev system. Secondly, when we do BOB for the same user (requester), it picks up the first level approver without the error.

Meaning, If USER1 shops for himself (Creator & Requester are same), we encounter this error. If USER2 shops for USER1, then the corresponding approvers were picked up correctly without the error. USER1 & USER2 have same authorizations in SU01D (USER2 is copy of USER1, so no authorization issues). Approvers determination is based on the requester.

Somewhere, we miss the settings. Don't know where though.

[former_member578547]

In SRM, Creator(Requester) should not be Approver.

Just for information.

Thanks,

Balaji.T.

[Former Member]

Okay. The problem is resolved.

It is due to the position based roles. Requester's position had some user roles associated through Relationship B-007/Related Object AG which standard code doesn't like it. As soon as we remove the position roles, it is able to pickup the stored agents against the respective Process Level GUID and no error is thrown.

PROBLEM RESOLVED.