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.