Lock Role for Changes till the transport is released

Question

Issue : since roles are managed by multiple security administrators, changes are moving against the sequence.
We have multiple security administrators, is there a way to lock a role for changes until the task/ req is released.
Example Scenario :
Security admin 1 : if there is a change request to add SU01 to the role: Z_TESTROLE, Security admin adds it and creates a Change request but does not release it.
Security Admin 2 : the security admin 2 will get a Change req for the same role Z_TESTROLE to add a tcode PFCG to it. Security admin 2 does his job and moves his transport now even though the first transport does not move the change made by the first security admin moves with the transport for the second admin.
We have multiple security administrators, is there a way to lock a role for changes until the task/ req is released.

Answer 1

Hi all,
Thanks for your responses.we follow a change procedure but I guess its just needs to be refined. Everybody figured out that this is a coordination issue but I was asked to research on any technical ability to handle this.
Here is a brief overview of our process :
1) BPO approves the change
2) Role owner support manager approves the change
then the Change request comes to 3)Security Manager for her approval.
I feel from Sox prespective the 3rd approval in not manadatory.
I'm I correct ??? where can I find Sox guide for SAP ?
Recap of the incident:
1)A change ticket is created for the t-code creation and a task is created for the role in which this report is to be added.
State I role Z_TESTROLE  is with ZMMR0025
After adding the new report ZMMR0055 the old report ZMMR0025 is removed.
State II
The role Z_TESTROLE has tcode ZMMR0055
now this is tested in development system by the requestor.
Before this goes into PRD via QA a newsflash is sent to all the endusers (so that they know which t-code to use)
Meanwhile if another security administrator works (suppose adds a new tcode or changes an authorization)  on this while the role is in state II changes made by Admin 1 are transported along with the second change.
State II + new changes = State III
When the role reaches PRD in state III result is the end user losses access to the required functionality ZMMR0025 before ZMMR0055 is made available.
I hope I’m clear , please let me know if I need to be more specific on any part.
I appreciate your help.
regards,
Salman.