After creating SC in SRM the SC doesn't always WF to approver

[Former Member]

Hi Everyone,

We are on SRM 4.0 and have just installed support packs in our test environments.

I tested the SC approval process and received the following results.

Created a SC (5665) using TECHREQ1 which should WF to APPROVER6 - doesn't work.

Created a SC (5666) using TECHREQ1 and substituted APPROVER1 - this works.

Created a SC (5667) using TECHREQ1 and substituted APPROVER6 - this works.

The 3 SCs above are identical except for the approver.

So when assigning a substitute approver the WF works correctly and the approver receives the SC in their inbox. When not assigning a substitute approver the SC does not workflow to the approver.

I was thinking it might be an org structure issue but then I noticed in the WF log that for the SCs that work, the WF AGENT is listed as USAPPROVER1 and USAPPROVER6 and the SC that doesnu2019t work shows the WF AGENT as APPROVER6. The US prefix is missing.

Does anyone have any ideas about what may be wrong?

Thanks,

Mike

[Former Member]

If you are hardcoding the approver user id's in the BADI, append "US" infront of their userid.

During subsitution the system automatically assumes US infront of the userid and hence it works without any problem.

Regards,

PR.