Usage of BW Entities

The classical Where-Used Analysis can be found in the Where-Used Analysis area and in the search view:

Where-Used Analysis in the System Scout ribbon and the System Scout search

The Where-used analysis can also be started from the System Scout menu or via the context menu of the entity.

Where-used Analysis in the context menu of a BW entity

The functionality supports the usage analysis of the following groups of entities:

All entities that are supported are also supported for the Where-Used Analysis in the coding. Normally, the code is searched for the Technical Name of the entity. However, there are exceptions where the system searches for the underlying tables of the entities in the code (for example, A table for DSOs):

Advanced DSOs
Characteristics
DSO
InfoCubes
Key Figures

The where-used analysis requires the installation of two customer Function Modules:

Z_RFC_USAGE_ANALYSIS
Required for usage analysis within reporting entities, like Structures or Variables
Z_RFC_CODESCAN
Required for the scan of ABAP coding for certain strings or InfoProvider tables

The names can be different when another prefix other than Z_ is used. The correct installation can be checked in "Administration → Connection Data → Function Modules".

Function Module Check with all needed Function Modules up to date

You can also run this function for multiple objects at once. The results are shown in separate tabs:

In BW Objects – Flat list of usages in all detected BW entities.
In Code - Flat list of all code findings, including the lines where they occur.
In BO Reports - Flat list of usages in all BO reports (stored in BW or BO). Requires a BO license and synchronized BW relations (see BO Synchronization).
Nested usage in Process Chains - Tree view of nested usages in Process Chains (e.g., an InfoProvider activated in a Process Chain step that is itself used in a Meta Chain).
Nested usage in Reporting Elements - Tree view of nested usages in Reporting Elements (e.g., a Key Figure used in a Calculated Key Figure, which is used in a Query).
In HANA - Flat list of direct usages in supported HANA entities. Requires a HANA license and configured HANA Schema Mapping (see Maintain HANA Schema Mappings).
In HANA Code - Flat list of usages in HANA code for supported HANA entities. Requires a HANA license and configured HANA Schema Mapping (see Maintain HANA Schema Mappings).
In SAC - Flat list of direct usages in SAC Stories. Requires an SAC license and configured Source System Mapping (see Maintain Source System Mappings).

Where-used Analysis with results in BW entities, in BO reports and nested usages in Process Chains

Each grid in every tab contains a Usage Of column, which identifies the entity used in the result. This is especially useful when running a Where-Used Analysis for multiple entities.

When analyzing code for InfoProviders of type DSO, Cube, or Characteristic, the search is performed on the corresponding table names rather than the InfoProvider name itself.

For example, a search for DSO 0CCA_O09 will be executed for the string /BI0/ACCA_O9.0 (where the dot . is a placeholder for a single character). This approach ensures that results for related DSO tables—such as /BI0/ACCA_O900 or /BI0/ACCA_O940—are also found.

If you want to search specifically for the InfoProvider name, you can use the Code Scan of the System Scout.