Dependency Analysis Results¶

Summary¶

In the summary view, you’ll see general advice about any potential issues that could arise when the analyzed transports are moved to the target system, as well as details about the transports that were analyzed.

Transport advice¶

There are two possible options :

Importing these transport into the target system is safe : No issues were detected and there should not be any import errors when the transport is imported in the target system.
Importing these transports into the target system could cause problems : Issues were detected. In the summary section you’ll see an overview of any potential issues.

Analysis Summary¶

This section shows an overview about what was analyzed, and any issues that were found.

Dependencies Analyzed : the number of objects that use any objects in the analyzed transports that were analyzed. You can click on the number of analyzed dependencies to see a list.
Dependant Objects different : the number of objects that use any objects in the analyzed transports that are not the same in the target system. You can click on the number of different objects to see a list.
Used objects analyzed : the number of objects used in the objects in the analyzed transports that were analyzed. You can click on the number of analyzed objects to see a list.
Used objects missing : the number of objects used in the objects in the analyzed transports that don’t exist on the target system. You can click on the number of missing used objects to see a list.
Used objects different : the number of objects used in the objects in the analyzed transports that are different on the target system. You can click on the number of different used objects to see a list.

Analyzed Transports¶

The list of transports that were analyzed will be displayed here.

You can click on the transport number to see the content of the transport.

Dependencies¶

Dependency Summary¶

This section shows a summary of the analysis that was done.

The number of analyzed dependencies is displayed, as well as the number of dependencies that are different on the target system.

Dependent Objects Found¶

The number of objects that use any objects in the analyzed transports that were analyzed. You can click on the number of analyzed dependencies to see a list.

Dependent Objects Different¶

The number of objects that use any objects in the analyzed transports that are not the same in the target system. You can click on the number of different objects to see a list.

Dependency List¶

The list of all analyzed dependencies will be displayed here.

Dependency List Functions¶

Select Objects With Difference : Select all entries in the list that are different on the target system.
Add to transport : Add the selected objects to a transport. This allows you to include these objects in a transport, you could add it to the transport you are analyzing, or a different transport that you will also move to the target system along with the analyzed transport.

Dependency List Columns¶

Program ID : The Program ID of the object in the transport request. Possible values are R3TR or LIMU.
Object Type : The type of objects that was analyzed, you can find a list of possible objects here[TODO]. A complete list of these object types and what they mean in your system can be found in table [TODO]
Object : The name of the analyzed object. You can click on the object name to display the object in the local system.
Problem : If the object was different, this will be displayed here. You can click on the value in this column to see what the differences of this object between the source and target system are.

Used Objects¶

This section shows a list of all objects that are used in any of the objects in the analyzed transports, and will show information about their status in the target system. If the objects are missing or different, this could cause the transport to fail, or the transported functionality to not work correctly.

Used Object Summary¶

This section shows a summary of the objects that are used in any of the objects in the analyzed transports.

Number of analyzed objects : Total count of all objects that were analyzed.
Number of different objects: Total count of all used objects that are different on the target system.
Number of missing objects: Total count of all used objects that don’t exist on the target system.

Used Object List¶

The list of all objects that are used in any object in the analyzed transports is displayed here.

Used Objects List Functions¶

Select Objects With Difference : Select all entries in the list that are different on the target system.
Select Missing Objects : Select all entries in the list that don’t exist on the target system.
Add to transport : Add the selected objects to a transport. This allows you to include these objects in a transport, you could add it to the transport you are analyzing, or a different transport that you will also move to the target system along with the analyzed transport.

Used Object List Columns¶

Program ID : The Program ID of the object in the transport request. Possible values are R3TR or LIMU.
Object Type : The type of objects that was analyzed, you can find a list of possible objects here[TODO]. A complete list of these object types and what they mean in your system can be found in table [TODO]
Object : The name of the analyzed object. You can click on the object name to display the object in the local system.
Problem : If the object was different or missing, this will be displayed here.

Different : You can click on the value in this column to see what the differences of this object between the source and target system are.

Missing : You can click on the value in this column to display the object in the local system.

Suggested Transports¶

If any issues were detected, the dependency analyzer looks for any existing transports on the local system that contain the missing or different objects. Including these transports when moving the analyzed transports to the target system will bring the status of these objects to the same status as on the source system.

You can include these transports in the analysis, to ensure there wouldn’t be any issues when they are included. Problems could happen if these transports contain other objects that have their own dependency issues.

Suggested Transports Summary¶

This section displays the number of transports that contain any objects that were dependent on or used in the analyzed transports that are missing or different in the target system.

Suggested Transports List¶

The list of any transports that contain the objects that caused any dependency issues is displayed here.

Suggested Transports List Functions¶

Analyze including these transports: Re-run the analysis including the transports selected in this list.

Suggested Transports List Columns¶

Transport Number : Transport Request number. You can click on the number to see the contents of the request.
User : User that created this transport. You can click on the number to [TODO]
Program ID : The Program ID of the object in the transport request. Possible values are R3TR or LIMU.
Object Type : The type of objects that was analyzed, you can find a list of possible objects here[TODO]. A complete list of these object types and what they mean in your system can be found in table [TODO]
Object : The name of the analyzed object. You can click on the object name to display the object in the local system.
Problem : If the object was different or missing, this will be displayed here.