What happen if I change a role after I released the transport?

Question

Here is my Scenerio:
1) Assuming I've created a role : ROLE1 in DEV
2) I create a transport TR1 with that ROLE1, NOT yet released.
3) Then I added ME21 txn to ROLE1.
4) Then I released the transport TR1
5) Then I remove ME21 txn from ROLE1.
6) Then I transport role from DEV to QA.
Q1) I would expect In QA, ROLE1 will still has ME21. - True?
Q2) TR1 will be the snapshot of the ROLE1 when I release the transport TR1 - True?
Now, I want to delete the ROLE1,
A) I would need to create another Transport TR2 first with ROLE1 in DEV
B) Then delete ROLE1 in DEV
C) Then release Transport TR2
D) Then I decided that I still need ROLE1. (oops)
Q3 I should not transport TR2 so that it won't delete it in QA. - True?

Answer 1

Hi Dominick,
>
> 1) Assuming I've created a role : ROLE1 in DEV
>
> 2) I create a transport TR1 with that ROLE1, NOT yet released.
>
> 3) Then I added ME21 txn to ROLE1.
You should add the role again to the Transport to avoid inconsistency
> 4) Then I released the transport TR1
>
> 5) Then I remove ME21 txn from ROLE1.
>
> 6) Then I transport role from DEV to QA.
> -
>
> Q1) I would expect In QA, ROLE1 will still has ME21. - True?
Answer: If you reassign the role to the TR then you will get.
> Q2) TR1 will be the snapshot of the ROLE1 when I release the transport TR1 - True?
Answer:  TRUE (but without ME21 if you don't add the change to the CR - see below for detail discussion)
> -
>
>
> Now, I want to delete the ROLE1,
> 
> A) I would need to create another Transport TR2 first with ROLE1 in DEV
>
> B) Then delete ROLE1 in DEV
>
> C) Then release Transport TR2
>
> D) Then I decided that I still need ROLE1. (oops)
> -
> Q3 I should not transport TR2 so that it won't delete it in QA. - True?
Answer:  TRUE. And if you want the role again back to DEV without recreating it, please download the role from QAS or PROD and then Upload it to DEV. After that you need to generate the Profile of the role.
> -
FYI:   When a Change is Included into a request to send in other systems, then this request is called "Change Request" (CR). After Releasing, the CR called as "Transport request".
CRs are basically (in layman language) the Pointers to the DB changes performed. These are included into a CR as "Task". A CR can contain multiple Tasks created by different users.
Please note if this is a Workbench CR then it is ONLY editable by that particular user(owner of the Task). Also the Object captured in a Task of a WCR possesses a Lock till it gets released and thus can't be added to any other Task of a different CR. The Objects are unlocked when the Tasks and the CR is released respectively.
There are no Object Lock for Customizing CRs ... like your TR1 which contains Creation / Deletion of roles.
After the release of each Task, all Objects contained into every Task are transferred to the Change Request. After release of all Tasks, the CR owner can release the CR and thus the Transport Request has been initiated. Technically, at this time, a copy of Data from the Database of DEV captured under the headers of each Tasks are written to Data Files in Central Transport Directory.
Now coming to your queries..... there are no such synchronization happens for a Task if the Objects are edited in different time frames before Release.  So, when you added ME21, again you need to assign this change to the same CR. (_Answer to your Q1_)
Please let me know if you have any confusion / query.
Regards,
Dipanjan