Versions Compared

Old Version 1

changes.mady.by.user Alexej Hinz

Saved on

compared with

New Version Current

changes.mady.by.user Alexej Hinz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The classical Where-Used Analysis can be found in the Where-Used Analysis area and in the serach view:
Image Removed
Image Added

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

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

...

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

  • Z_RFC_USAGE_ANALYSIS   ANALYSIS        (required for usage analysis within Reporting entities, like Structures or Variables)
  • Z_RFC_CODESCAN 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".

 Image Removed

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

 Image Removed

The functionality can be started by selecting multiple entities. The results are shown in different tabs. Image Added

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 SAC - Displays a flat list of the direct usages in SAC Stories. (info) For that functionality, SAC must be licensed and you have to maintain a source System Mapping (see Maintain Source System Mappings).

 Image RemovedImage Added

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.