SAP® Documentation

Single view

/SDF/CMO_TR_CHECK - Check Transport Request

General Data in Customer Master   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Transport Check

Check Transport Requests

The report "Check Transport Requests" provides various checks for the 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 request in a test system, before he imports it into the preproduction or production system.

Configuration and Prerequisites

RFC Connections and Authorizations

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 1830640. Or you can directly use the Solution Manager READ user SM_ 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. 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 connection which requires a logon. From the result screen you can then navigate into the details of the transport requests or objects by double-clicking on a corresponding field.

Transport Checks

The objects in the selected transport requests are checked and compared with the target system.

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 reference 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 and customizing objects.

BW Cross Reference

This works as the cross reference check. It must be used if BW objects are included in the transport request.

Sequence Check

The sequence check identifies other transport requests with identical objects which have been released in the analysis period, but have not yet been imported into the target system.

Software Component Check

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 Criticality

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 collection of the usage statistics must be triggered in the production system with the report /SDF/OI_ADMIN. You must first activate the Usage and Procedure Logging (UPL) in the production system.

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 in the production system. These objects are then also shown in the result.

PERFORM Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 4850 Date: 20191213 Time: 090104     sap01-206 ( 26 ms )

Our Service

Looking for Support? Questions?




Leave us your contact details and we will call you back. Panels marked with * are mandatory.