When you release a transport in Dev system, the release removes all the locks. The releasing is independent from the actual transport into Test, Quality and Productive Systems (there are even SAP customers who have just a develpment and a productive system). If there is not automated check available regarding e.g. the version of an object, there needs to be manual checks and processes in place, before sending transports into the production.
(A) Option to solve release/transport/testing problem without the purchase of other solutions
1. Send Copy to Test/Quality system without releasing Transport in Development System
One solution to your problem is, to only send a copy of your transport into the test/quality system, leaving the transport open in the dev system. Only when the tests in test/quality system are positive, you would release the transport in dev system. That way, untested coding will most likely not end up in production, and also, other developers that have to maintain the same objects will be aware that somebody else is working on those objects already.
There still will be situations that are not fixed with this method, especially after the final release of the transport, or with customizing transports and possibly other scenarios as well, were locking is not available.
2. Use STMS QA Approval Procedure
With STMS Quality Assurance Approval Procedure, you can put a critical Review Process in place before the transport into the productive system. Transport requests can be approved or declined and critical transport objects can be identified based on customizing (e.g. declare your untested / unfinished codings in the quality system as critical transport objects).
This process only works if the review process is done thoroughly. It will fail if transport requests are always approved without checks.
(B) Other solutions that require purchasing
Other solutions mostly require the purchase of a product, to be in better control of the transport management, like the above mentioned powerful ChaRM being part of the SAP Solution Manager or also simpler products from third party vendors like SAPalot GO.
If you dont have the Solution Manager in place already, most likely it wouldnt make a lot of sense to acquirer it, just for the purpose of implementing ChaRM alone. However, ChaRM is very powerful: Change Request Management enables you to manage your SAP Solution Manager projects from end to end: From change management and project planning, through resource management, to physical transports of changes from the development environment into the productive environment.
Other, smaller solutions, might just check for the correct sequence of transports, detecting collisions and overtakers. These solutions will not help you in fixing the problem, but make you aware of the possible risk, therefore helping you to react before the transport into production is done.
Bluesky
