While many of us would like to simulate/check our transport request for error before we import the changes into production system, it becomes almost a necessity during big Go-Live’s / Release Management phase to sequence the transport request and check dependency between requests.
Although there are lot of solutions already been implemented like the followings
it is always best to use tools provided by SAP.
With ST-PI component, SAP has delivered tcode /SDF/TRCHECK (program: /SDF/CMO_TR_CHECK) which makes sure errors of transport request gets detected before TR is imported to production system.
Refer to program documentation for details.
Lot more details can be found in
Given that we have a solution doesn’t mean we end up using it to the best of its value. Hence it will be great to integrate this with SE10. 😉
I implemented BADI: CTS_REQUEST_CHECK to execute report: /SDF/CMO_TR_CHECK before releasing the transport request (method: CHECK_BEFORE_RELEASE) and then giving a pop-up to decide if I wish to continue to release the transport request.
Also I created a custom SET/GET parameter to ensure BADI calls report only when the user parameter is set to X.
Results are good 🙂
Identifies if objects are missing in production system.
Catches missing transport request.
Can be a life saver 🙂