In our organization, there are many users who use QM02 to maintain data on a Quality Notification. Now want only a small subset of them to have the ability to set the QN to notification complete (status NOCO). This is done using menu path Functions -> Complete.
Can we use standard security to block the setting of NOCO?
Is there some way to make the Q_VORG_MEL security object manage this (it doesn't seem to be well-documented)?
Ideally, we'd like to disable the portion of the QM02 menu path that permits the setting of Complete and 'In Process Again' options (without resorting to screen variant).
Is there an enhancement point in the functions that bring up the menu that we can use to disable the Complete/In Process Again options?
Suggestion:
What you can do is to have three roles in total - Creator, Modifier and Coordinator.
This is the description of the Modifier role.
Change a Quality Notification and perform tasks (not limited to the user's assigned tasks) in the Quality Notification.
Notes on QM02 authorization objects: Modifier can only use statuses "Put in Process", unable to change user statuses. Cannot reopen, set delete flag, postpone or refuse approval.
Q_VORG_MEL restricted to BABS, PMM2, QN40, QN41, QN42 business statuses.
In addition to the Creator role (since both roles need to be assign), the user is able to change the QN header data, able to add/release/complete tasks including tasks not assigned to the user (system still logs who made the changes). Unable to make status changes except for “Put-in-process”.
Here is the Coordinator description:
Disposition of Quality Notifications using transactions to add tasks to a quality notification, change coding on a quality notification, delete, disposition or close the quality notification.
In addition to the Creator and Modifier role (since all three roles need to be assigned), user is able to make all status changes including system and user statuses.
Notes:
Basically, the above suggestion indicates that proper use of the Q_VORG_MEL security object can satisfy the above scenarios requirement.
Business transaction PMM4 is required to set the NOCO status, so you need to be careful not to include that one. Your task is to find out all the possible business transactions really are required for your day-to-day users.
