Skip to content

Latest commit

 

History

History
190 lines (116 loc) · 4.45 KB

dependency-analysis-fec4927.md

File metadata and controls

190 lines (116 loc) · 4.45 KB

Dependency Analysis

In this topic, you will learn more about dependency analysis in the Custom Code Migration app.

Purpose

You can utilize dependency analysis to identify dependencies from your custom code to the SAP standard and thus which part of your custom code can be transformed to the SAP BTP, ABAP Environment. To do this, you can use the Scoping app within the Custom Code Migration app. This app provides you with a set of measures that analyze how likely it is for you to be able to transform your code to the SAP BTP, ABAP environment.

Note:

Please be aware that as of the SAP BTP, ABAP environment 2411 release, you now need to initiate scope calculation manually after project creation. Scope calculation no longer starts automatically at project creation.

This is how you start a dependency analysis in the Scoping app:

  1. In your project, select the Scope tab in the lower half of the project overview page.

  2. Select Change Scope.

  3. Select the second Packages tab from the left. This tab is marked with a bubble chart icon.

  4. Select the Settings (:gear:) button.

  5. Under Measures, choose your metrics for the chart axes.

    Tip:

    This way you can set up your own individualized chart to perform dependency analysis of your custom code with SAP standard. You can determine, for example, how often your custom code calls SAP application APIs or uses DB accesses to SAP application tables such as the MARA table.

The following measures are available:

The measures and their meanings

Measure

Explanation

Number of Changes

Number of changes per object within the last year

Number of application API usages

All usages of application APIs such as classes, interfaces, and function modules

Number of application DB API usages

All database operations on database tables or views; i.e., only the number of different database tables and views are counted, not the overall number of accesses

Number of distinct app. DB APIs used

Database operations on distinct database tables or views

Number of distinct application APIs used*

Distinct usages of application APIs; i.e., only the number of different APIs are counted, not the overall number of accesses

Number of objects in package

Overall number of custom code objects within a package or request entry point

Number of objects using appl. DB APIs

Number of objects within a package or request entry point accessing application-specific database tables or views

Number of objects using application APIs

Number of objects within a package or request entry point using application APIs

Proportion of objects using app. APIs

Ratio between objects using application APIs and all objects within the package/request entry point

Proportion of objects using app. DB APIs

Ratio between objects using application-specific database tables or views and all objects within the package/request entry point

*With this measure, for example, you can check how many dependencies to different APIs your code has. In the best case, both this number and the number of locations where you are accessing those APIs are small.

After adjusting your settings, your chart could look as follows:

You can then also save your individual settings as your own view. This way, you won't have to adjust your settings again the next time you want to use the chart.

Related Information

Custom Code Migration

Complexity Analysis