The classical Where-Used Analysis can be found in the Where-Used Analysis area and in the search view:
...
The Where-used analysis can also be started from the System Scout menu or via the context menu of the 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 2 customer Function Modules named:
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 than Z_ is used. The correct installation can be checked in "Administration → Connection Data → Function Modules".
...
This function can also be performed for several objects at the same time - the results will be displayed in several tabs:
In BW Objects - Displays a flat list with the usages in all found BW entities.
In Code - Displays a flat list with all findings in coding. In the list, you can see the code lines where the result was found.
In BO Reports - Displays a flat list of the usages in all BO reports (which are stored in BW or BO). 
For that functionality, BO must be licensed and you have to synchronize the BW relations (see BO Synchronization).
Nested usage in Process Chains - Displays a list with tree structures of nested usages in Process Chains (e.g. InfoProvider is activated in a Process Chain step and this Process Chain is used in another Meta Chain).
Nested usage in Reporting Elements - Displays a list with tree structures of nested usages in Reporting Elements (e.g. Key Figures is used in a Calculated Key Figures which is used in a Query).
In HANA - Displays a flat list of the direct usages in all supported HANA entities. For that functionality, HANA must be licensed and you have to maintain a HANA Schema Mapping (see Maintain HANA Schema Mappings).
In HANA Code - Displays a flat list of the usages in HANA code for all supported HANA entities. For that functionality, HANA must be licensed and you have to maintain a HANA Schema Mapping (see Maintain HANA Schema Mappings).
In SAC - Displays a flat list of the direct usages in SAC Stories. For that functionality, SAC must be licensed and you have to maintain a source System Mapping (see Maintain Source System Mappings).
...
Every grid in every tab contains a column Usage Of. This column identifies the entity which is used in the result. This is needed if you start a Where-Used Analysis for multiple entities.
| Tip |
|---|
In case the analysis in coding is done for InfoProviders of type DSO, Cube or Characteristic the coding will be checked for the according tables, not for the entity name itself. So when a search is done e.g. for DSO 0CCA_O09 the search will be executed for the string /BI0/ACCA_O9.0 (the dot is a placeholder for a single sign). This is done because a search for 0CCA_O09 would not find results for selections on the DSO tables /BI0/ACCA_O900 or /BI0/ACCA_O940. In case you want to search for the InfoProvider name itself, you can use the functionality ABAP Scan of the System Scout. |