Block Object Deletion from Transport Request / Task

[Danish]

Hello,

Scenario:

Developers are allowed to create transport request, and add objects to it. They also can delete the “objects” from transport request.
This is very high risk scenario where developers may have made changes to certain objects and then deleted those objects from transport request (may be that object is not required for implementing solution). Ideally, instead of deleting such object, the developer should revert the changes in same transport to ensure consistency.
If objects are deleted from the transport, it can cause serious inconsistencies across the landscape, including risk to transport unwanted code in case the deleted object is modified afterwards without reverting the original code.

We have identified enhancement point where the Delete button can be disabled and only authorized person can delete after checking consistency. But this will increase the overall turnaround time in the process – request to be sent to authorized person, review, delete object and then the developer can proceed.

Any suggestion for a better approach is much appreciated.

Thanks

Danish

[Danish]

Hello,

Scenario:

Developers are allowed to create transport request, and add objects to it. They also can delete the “objects” from transport request.
This is very high risk scenario where developers may have made changes to certain objects and then deleted those objects from transport request (may be that object is not required for implementing solution). Ideally, instead of deleting such object, the developer should revert the changes in same transport to ensure consistency.
If objects are deleted from the transport, it can cause serious inconsistencies across the landscape, including risk to transport unwanted code in case the deleted object is modified afterwards without reverting the original code.

We have identified enhancement point where the Delete button can be disabled and only authorized person can delete after checking consistency. But this will increase the overall turnaround time in the process – request to be sent to authorized person, review, delete object and then the developer can proceed.

Any suggestion for a better approach is much appreciated.

Thanks

Danish

[Former Member]

Did you consider using SAP authorization technique?

Authorization object : S_TRANSPRT.

Activity : 06 ( For delete ).

and 23 ( Change/edit object list manually ).

R

[Danish]

Hello Rudra,

Thanks for your response.

This a also a good option for my scenario.

S_TRANSPRT is default authorization given to all developer with access to Request type: DTRA and TASK and Activity: 01, 02, 03, 06, 43 and 90.

By removing 06, we can stop object deletion. But the need for deleting object from task is very common and valid scenario in development client. So I will have to have authorized person reviewing that having authorization (06) to delete. This may take too much time.

Is there something we can automate to say the object being deleted from Task is consistent in Development client, QA and Production.

Thanks,

Danish

[Former Member]

Hiya,

That is what you wanted and that is how it should be. I don't understand why it is valid scenario to delete object from transport manually?  For me it is risky and non-recommended and we don't have to delete objects from transport ever and I am quite sure it will work. That is the beauty of CTS.

I understand some client ( mainly some people from client side ) push for this without knowing the consequences and believe me it becomes sometime painful to reconcile. I am sure you can justify them not deleteing objects from object list. Rather use sometimes "Sort and Compress" to delete duplicates.

Also I did not get what you meant by automating object being deleted from task is consistent in Development client, QA and Production.?

R