Analyzing transports

Transport Selection

Transports and RFC Destinations :

Transports

You can enter one or more transports in the “Transports” field on the “Transport Selection”-tab.

Target System :

You can enter the RFC-destination to the target system the transport will be transported to. The content of your transport will be analyzed on this system, detecting any issues that may occurr when the transport is imported there.

Used Object Scope

You can define the scope of used objects to be analyzed. This should usually be limited to the scope in which development is done in your organization.

The only exception to that would be if you intend to transport the request to a system that is of a different SAP release than the system where the development is done.

Used objects are objects that are used inside any object that is in the transports that are being analyzed.

These objects could be data elements, structures, classes, function modules, database tables or any other type of transportable development object.

Object Selection

Objects :

You can enter a range of objects that you want to be analyzed on the target system.

These fields are normally pre-populated with the Y* and Z* ranges.

You can modify this selection by adding additional ranges.

Packages :

You can limit the range of Packages (Development Classes) will be analyzed.

Used Object Transport scope

When analyzing used objects, any objects that don’t exist in the target system, or are not the same in the target system as in the local system, may be in an existing transport that should also be moved to the target system.

The Dependency Analyzer will search for any such transports during the analysis.

Ignore Transports older than x days :

When finding used objects in existing transports, only transports that were created within this specific number of days will be analyzed.

Only Unreleased Transports

When this is selected only transports that have not yet been released are analyzed.