Recently, I came across a new requirement where user status reversal should be authorized by Superior. User Status change can be controlled by Authorization Key. By assigning Authorization Key to user statuses, same user can set as well can reverse the status based on Lowest & Highest Number.
If one user (USER 1) can set the user status but should not reverse the user status to previous & the superior user (USER 2) can / cannot set the user status also he should provide approval to the USER 1 to change / reverse the status, then configurations should be done accordingly.
This document is having this User Status control based on user authorisation as reference for this document. (Thanks to Riyaz Maner).
User Status Configuration (OIBS)
Initial Status “CRTD” has been set while creating new document
Set Status from CRTD (Created) to ISSD (Issued)
Reversal of ISSD (Issued) status to CRTD (Created)
Approving Authority changes to Status as token of Approval (ISSD – issued to ISCR – Issued Reversal to Created)
Reverse Status to CRTD – Created
Here all the “Reversal” statuses should be assigned to Authorized User (Manager) using Authorization Key. Other statuses can be assigned only to End User (Planner) / both End User (Planner) as well as Authorized User (Manager) using Roles & Authorization in PFCG.
Conclusion: By having this, developments can be avoided for these controls in user status