
In Focused Build (FB) or in Change Request Management (ChaRM),we typically have automatic jobs running for doing import in target systems. Many times some of the transports in queue gets failed to import and they the job attempts to import such transports at every execution. While doing so, we may get downgrade protection conflict against any latest transport which is successfully imported. In case of such conflict, the automatic job does not import other transports, blocking complete import. The failed transport may not be resolved immediately, so I needed to find way to let the imports continue, while the failed transport is still there.
Find which are the transport in conflict. This is either found on Downgrade Protection tabs on CRMUI of Change Document/Release or on FB Batch Import logs. In my example, following were the transport:
Source Transport = D31K905155 (transport being imported, which ended previously with RC=08), Conflict Transport = D31K904807 (Transport with Successful import)
I will have to remove tracking for D31K904807 using report RSCTS_OBJ_TRACK_REMOVE. Here, we give the System ID for target system. Before executing this report, you may check entries in table SCTS_TRACK_MAIN, with REQUEST_ID and SYSTEM_NAME. You should find that few entries exist.
After report is executed, we get success message. If you check the table SCTS_TRACK_MAIN again now, you will find 0 entries with previous criteria.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
14 | |
12 | |
12 | |
9 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 |