2020-07-13 2475591

2475591 - Transport Check Report

Version 8 Type SAP Note
Language English Master Language English
Priority Recommendations / Additional Info Category Consulting
Release Status Released for Customer Released On 18.04.2020
Component SV-SMG-SDD ( Service Data Download )

Please find the original document at https://launchpad.support.sap.com/#/notes/ 2475591

Symptom

The transaction /SDF/TRCHECK or report /SDF/CMO_TR_CHECK provides various proactive checks for
objects in transport requests. It predicts transport related errors before the requests are imported into a target
system. Typical use cases are that a developer checks his transport in the development system, before he
releases it and imports it into the test system. Or a transport manager checks a number of requests in a test
system, before he imports them into the preproduction or production system.

Other Terms

Transport Execution Analysis for Projects, Return Code 8 Prediction, Online Import Check

Reason and Prerequisites

RFC connections to the source and target system must be provided. A system user with the authorizations of
the SAP Solution Manager READ profile can be used. The necessary authorizations are described in note
2257213. Or you can directly use the Solution Manager READ user SM_<SID> in this RFC destination.

If you select the transport requests with the option "Import Queue from target system" then the RFC to the
target system must point to the correct import client.

If you want to run the report locally in the development system with the test system as target system, you
must create an RFC connection from the development to the test system. If you want to run the report locally
in the test system with the production system as target system you must create an RFC connection from the
test to the production system. In these cases you can enter NONE as RFC to Source System. Or you run the
report locally in the production system. Then you need an RFC connection from the production system to the
source system, and you must enter NONE as RFC to the target system. If you run the report in the SAP
Solution Manager you can use the already existing READ or TMW connections to the source and target
system.

If you run the check in dialog mode you can also use connections which requires a logon, e.g. the TMSSUP
connections. From the result screen you can then navigate into the details of the transport requests or objects
by double-clicking on a corresponding field.

If you run the report with a variant in the background, then you find the results in the joblog.

The online import check requires additional preparation steps. First you should collect usage statistics in the
target or production system with the report /SDF/OI_ADMIN. For more information see the info button in the
report /SDF/OI_ADMIN. And you can maintain objects which are critical with regard to the online import in the
table /SDF/OI_CRITOBJ of the target or production system. For more information on the preparation steps
see the document in the attachment of this note.

© 2020 SAP SE or an SAP affiliate company. All rights reserved 1 of 3

2020-07-13 2475591

The checks are delivered with the ST-PI Plugin. You should implement the latest support packages for this
plugin. In addition the following notes should be implemented:

• ST-PI 740 SP6: Note 2475352 and 2517741

• ST-PI 740 SP7: Note 2517741
• ST-PI 740 SP8: Note 2661311 and 2711042
• ST-PI 740 SP9 to SP11: Note 2711042, 2804886, 2821480, 2851012 and 2886592
• ST-PI 740 SP12: Note 2851012, 2886592
• ST-PI 740 SP13: Note 2886592, 2911721
• ST-PI 2008.1 SP16: Notes 2475121, 2475058 and 2517741
• ST-PI 2008.1 SP17: Note 2517741
• ST-PI 2008.1 SP18: Note 2661311 and 2711042
• ST-PI 2008.1 SP19 to SP21: Note 2711042, 2804886, 2821480, 2851012 and 2886592
• ST-PI 2008.1 SP22: Note 2851012, 2886592,
• ST-PI 2008.1 SP23: Note 2886592, 2911721

Solution

The following checks are available:

Cross Reference: For all objects in the selected transport requests the referenced objects are identified by a
where-used-analysis. If the referenced objects are not included in the transport requests, we compare their
versions between the source and target system. If the versions are different or if the referenced objects do
not exist in the target system, it will be highlighted as a potential error. In addition we show the last transport
requests for the missing object versions. This check works for ABAP repository , data dictionary, customizing,
SAP notes and BW objects.

Sequence Check: The sequence check identifies other transport requests with identical objects which have
been released in the last 90 days, but have not yet been imported into the target system.

Cross Release: If the current system and the target system are on different support package levels, this
check identifies critical objects in the selected transport request, which belong to inconsistent software
components and should not be imported into the target system - e.g. SAP notes. For customizing objects we
compare in addition if the table structure is different in the reference system and target system.

Import Time in Source System: The import time of the selected transport requests in the source system is
summed up. For this check the source system should be a test system in which the transport requests have
already been imported.

Online Import Check: This check estimates the criticality of an import when the end users are working in the
production system. As a prerequisite you must first collect the table call statistics and the report execution
statistics in the production system for one week. The report identifies the dependent objects of the
transported objects and checks the usage profile of all objects. For tables the number of table accesses per
hour, table changes per hour and the table size in KB is shown in the output. For reports the number of report
execution steps per hour based on the UPL data is shown. In addition you can maintain a list of critical
objects with regard to online import in table /SDF/OI_CRITOBJ of the target or production system. These
objects are then also shown in the result.

Software Components

© 2020 SAP SE or an SAP affiliate company. All rights reserved 2 of 3

2020-07-13 2475591
Software Component Release

ST-PI 2008_1_700 - 2008_1_700

ST-PI 2008_1_710 - 2008_1_710

ST-PI 740 - 740

Other Components

Component Description

BC-CTS Change and Transport System

Attachments

File Name File Size Mime Type

Online Import Check Preparation.pdf 402 application/pdf

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2020 SAP SE or an SAP affiliate company. All rights reserved 3 of 3