How to restrict changes in PM Notification by creator only?

[former_member832687]

We are using various type of PM notifications to notify defects. The user who creates the notification, may or may not belong to the intended Planner Group which would attend to that notification. But the authorisation to process that notification is restricted by Planner Group.

In one particular type of notification we wish that only the creator is allowed to make any changes. The user who is processing (from the intended Planner Group) can only create Order from that notification and close it.

How can we achieve it?

M.S.Sachan

[jogeswararao_kavala · Accepted solution]

"In one particular type of notification we wish that only the creator is allowed to make any changes."

Below is the solution: (Assuming the Notification type to be 'M2', replace it by yours)

User-Exit: QQMA0014

Put the code below in the include ZXQQMU20 of the above exit.

IF i_viqmel-qmart = 'M2' AND sy-tcode = 'IW22' .
  IF sy-uname <> i_viqmel-ernam.
    MESSAGE: 'You can not make changes to this Notification.' TYPE 'E'.
  ENDIF.
ENDIF.

With this code implemented, when user tries to change a Notification (or Create Order from Notification) which was created by someone else, he receives the error shown below in the status bar, Means he is prevented to do so.

(For your ABAPer it is 2 minute job.)

Good luck

Jogeswara Rao

[Former Member]

Hi Sachan,

As suggested above by Mr Jogeswar, you can put the error message in IW22 and can call the notification in display mode. and one addition in the same message can be done as below -

' You are not authorized to change notification XXXXXX. For further notification processing with order creation, Goto -> IW34'

Assuming user has IW34 authorization.

Thanks

Avni Kumar

[MTerence]

Hi Sachan,

Is notification type and Order type 1:1, If yes, then you need to create separate roles for Notification creation / release / closure and Order creation / release / closure based on the Notification type and Order type.

I guess this can be achieved through authorization, else, you need to put a custom code to check the Planner group and Order type. Discuss with your security team to resolve this

Regards

Terence