Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
HrishikeshWagle
Product and Topic Expert
Product and Topic Expert
1,099

Problem

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.

Solution

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.

HrishikeshWagle_0-1716491870974.png

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.

HrishikeshWagle_1-1716492098163.png

Summary

  • This solution should be used with care. Means, we should be sure that this has no other downgrade impact. In my case, the Source Transport was only failing at activation phase, Import phase was successful. And, Conflict transport was completely imported. Also, there were no other older pending transports.
  • Report RSCTS_OBJ_TRACK_REMOVE does not ask for any confirmation before executing, so one should be careful about correct input.
  • Ignoring Downgrade Protection conflict on tabs of CRMUI, is also the solution in such cases, but when failed transports still exist, conflicts gets raised again.
  • We could use this solution even in cases, where some transports are removed from buffer without importing them. (Although this is not good practise)

SAP Solution Manager Focused Build for SAP Solution Manager 

1 Comment