Can TMS warn of objects on released-but-not-imported requests?

[former_member203650]

I'm sure this is a common problem: Developer A makes a change to an ABAP program, releases his transport, and imports it to the QA system. Developer B makes a subsequent change to the same program (unaware of Developer A's changes), realeases his transport and imports it to QA. Developer B's QA testing completes first, and his transport is imported to the Production system. Some time later, Developer A's QA testing is completed, and his transport moves to Prod, wiping out Developer B's changes!

How do we avoid this situation? Is there a way to configure TMS so that it warns Developer B of Developer A's released-but-not-yet-imported-to-Prod transport?

I am open to all suggestions, including activating user exits in TMS, and coding the warning myself. If that's the only solution, some guidance on TMS user exits and TMS tables I would need to query would be helpful.

Thanks in advance.

[Former Member]

Did you ever find any advice about this, or figure something out on your own?

[former_member203650]

Well, this thread may be 4 years old, but I have answered my own question (some time ago), and would like to share the answer with the SDN community.

I ended up activating the BADI CTS_REQUEST_CHECK. In the CHECK_BEFORE_RELEASE method I added my own code to check for "incomplete" transports for any of the objects on the transport being released. The code is pretty involved, but the basic trick is to SELECT all transports for each of the objects in the request from database tables E070, E071, and E07T, then use function TR_READ_GLOBAL_INFO_OF_REQUEST to get the details of each request to determine if it has been imported into the production system.

Once I have a list of "potentially conflicting" transports, I display it for the user in an ALV grid. I then allow the user to decide whether to go on with the release of the transport, or to cancel the release.

Cheers,

Terry