SAP Dependency Monitor

Introduction

The SAP Dependency monitor will analyze your transports to ensure there are no dependency issues when they are imported into the target system. The following issues will be detected :

Objects used missing : Any object in the analyzed transports use objects that don’t exist in the target system.

Objects used different : Any object in the analyzed transports use objects that are different in the target system

Dependency Issues : Objects that use any object in the analyzed transports are different in the target system.

Starting the transaction

You can start the transaction by adding the transaction /monitor/dep to you favourites, or by transaction from the command bar, by typing “/N/MONITOR/DEP”.

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.

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.

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.

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.

SAP System Requirements

The minimum requirement for installing the Dependency Monitor tool is an SAP ABAP Based system with a SAP_BASIS component version of 750. There are no minimum suport package requirements.

Other Documentation formats

E-Pub format

SAPDependencyMonitor.epub

Release Notes

Dependency Analyzer Version 1.0

Release Date : June 1, 2020

First Version

This release includes the ability to analyze transports to identify any issues that could arise when they are moved to a different sap system so you can avoid any transport failures or broken functionality

Index

SAP Jobs Monitor!

SAP Dependency Monitor

Introduction

The SAP Dependency monitor will analyze your transports to ensure there are no dependency issues when they are imported into the target system. The following issues will be detected :

Objects used missing : Any object in the analyzed transports use objects that don’t exist in the target system.

Objects used different : Any object in the analyzed transports use objects that are different in the target system

Dependency Issues : Objects that use any object in the analyzed transports are different in the target system.

Starting the transaction

You can start the transaction by adding the transaction /monitor/dep to you favourites, or by transaction from the command bar, by typing “/N/MONITOR/DEP”.

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.

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.

Dependencies

Used Objects

Suggested Transports