avoid user to transaction code when create workflow

[yadollah_geraei]

avoid user to transaction code when create workflow

[bpawanchand]

Hi ,

In complete Information or question does not help either sides. Can you give more inforamtion?

Thanks

Pavan

[mh97]

Hi yadollah geraei,

Then I think Pavan is right, you should give more information. Is it a SAP standard workflow? If so, what is the number?

It sounds like the workflow is using the basic Edit method on the business object. So when user executes the work item, it takes them to the normal transaction. In that case if there is an event triggered after the user performs the transaction (by workflow or otherwise), the workflow can wait for that event and use that to continue the workflow after the user has done their action, even if it wasn't via the workflow.

If it is a custom workflow you could possibly replace the Edit method step and use a user decision step followed by a BAPI call that updates the transaction per the user decision. In that case the BAPI call is executed in background by wf-batch and you can have your security team take the t-code access away from the users who are always to use the workflow.

[mh97]

Hi yadollah geraei,

The best way is to remove access to the transaction via security roles. So for example you have a purchasing requisition workflow and want user to always use the workflow decision step rather than ME54N. So just have your security team disable users' access to ME54N.

There might be other ways to accomplish your goal but I think the security approach is simplest and best. Unless there is more to your situation.

Hope this helps!

Margaret

[yadollah_geraei]

hi Margaret

when disable users access to t code workflow does not work

Thanks

[former_member186746]

Hi,

You can use roles in agent assignment of workflow tasks, then your authorization profile and workflow agent determination rules are alligned.

Kind regards, Rob Dielemans