Authorization Control in PM Order

[Former Member]

Hello,

We would like to control authorizations in PM Order, but not from transaction side.

More specific, we would like some users to have authorization to change pm orders but only some fields, for example user status or basic dates but not to have authorization to change material tab or operation tab.

Could this be possible??

Regards,

George Michalos

[jogeswararao_kavala · Accepted solution]

GEORGIOS

• What about other fields? You should be very clear about fields to be allowed OR fields to be not allowed.
• When you specify the list of fields to be allowed, then it will be presumed that all other fields are not allowed in Order by a user.
• Similarly when you specify the list of fields to be not allowed then all other fields will be treated as allowed for solution evolving purpose.
• So let's be clear about this before we start working on a solution.
• SHD0 is not an answer to your requirement.
• Also you can not achieve this through AuthObject/s  as per my judgement in case of complexity .

Regards

KJogeswaraRao

[Former Member · Accepted solution]

Thank you for your answer.

[jogeswararao_kavala · Accepted solution]

• In fact, my reply was awaiting your full specifications.
• However, I was hinting at use of user-exit IWO10009 using a Ztable.
• This ztable will contain users vs allowed fields
• And the code in the exit will check whether the logged-in user is editing the field he is allowed for?
• IF not it will throw an error and the Order is prevented from update.

[Former Member]

In addition to this, if you want to restrict on field level, then try to follow following approach.

1) Go to SU24

2) Enter transaction code as IW32

3) Execute

4) You will see the detailed list of authorization objects relevant to IW32. Select whichever is appropriate for your requirement and use them in different roles. Assign these roles to users.

Regards,

Amol

[Former Member]

Thank you for your answer.

[Former Member]

Hi Georgios Michalos,

Try to get this through transaction variant using SHD0.

Regards,

Amol