cancel
Showing results for 
Search instead for 
Did you mean: 

Workflow Error due to missing user role S_DEVELOP

Former Member
0 Kudos

When we start this workflow for an approval with HCM we have to responsible users in the scenario. The first one has multiple user rights (role: it Manager, extended user rights for applications and ABAP workbench), the second one not (role: hr Administrator with typical hr user rights). The first approval (via SAP FIORI app) by the it manager works without any problems. The second one leads to the status ERROR of the workflow due to missing user rights of the hr administrator. They are all tracked and we currently are fixing them. BUT there is also a red light by calling S_DEVELOP which cannot be connected to anyone within the productive SAP system! Also we assigned the user role SAP_BC_ENDUSER and SAP_BC_SRV_USER to the end users involved into this scenario, S_DEVELOP is refered. See screen shot below. Does anybody know what to do now?

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member186746
Active Contributor

Hi,

Do you mean it is company protocol to not assign S_DEVELOP? I think activity 03 is display so this should not be a risk.

If this is not a possibility then you have to find out where in the task and method this authorization check takes place and if you can change that with a badi/exit/enhancement.

Kind regards, Rob Dielemans

Former Member
0 Kudos

Thanks for your time and effort! Again - sorry that you have to wait.

Former Member
0 Kudos

Sorry for keeping you waiting, it was a general problem in the system of the customer which was solved by the team.

pokrakam
Active Contributor
0 Kudos

How are you checking this? SU53 sometimes hides previous failures, or it's possible that S_DEVELOP is not needed or just a fallback from an earlier failure. You can use ST01 to do a trace, but auth checks are sometimes performed for noncritical reasons. The fastest way to check is to run it with a SAP_ALL or firefighter ID.

I also notice the object type is SMIM, I'm guessing it's trying to read something from the MIME repository. This points more to an origin in FIORI/web space rather than workflow.