SAP Knowledge Base Article - Preview

3680744 - discrepancy in STMS transport import history and /TMWFLOW/TRACK_N table entries in SAP Solution Manager

Symptom

  • Imports are not automatically declared as repaired after import for client "ALL" happens and is stored in /TMWFLOW/TRACK_N.
  • There is no 1:1 correspondence between the transport logs, import history in the managed system, and the table /TMWFLOW/TRACK_N.
  • Transport logs show that some imports have steps spanning several days, causing inconsistencies in the import history.
  • Import ended with RC=8 , followed by successful completion hours or even days later.


Read more...

Environment

  • Change Request Management (ChaRM)
  • Transport Management System (TMS)

Product

SAP Solution Manager all versions

Keywords

transport request, import history, /TMWFLOW/TRACK_N, RC=8, repair flag, multi-client import, transport profile parameter, SAP Solution Manager, discrepancy, import inconsistency, TMS configuration , KBA , SV-SMG-CM , Change Request Management , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.