Show TOC

Loading HierarchiesLocate this document in the navigation structure

Use

You can load hierarchies from different source systems:

  • from an SAP system

    Since the metadata have already been delivered, you can load the standard hierarchies from an SAP system.

  • from an external system (BAPI, file)

    If you want to load the hierarchies from an external system, you first need to define the metadata for these hierarchies.

    Note

    You can also load hierarchies using the data mart interface from a different BW system. See Hierarchy and Using the Data Mart Interface.

Prerequisites

  • In the InfoObject maintenance screen, the With Hierarchies flag is set for the hierarchy basic characteristic. This means that the characteristic can have hierarchies.

  • Before you load a hierarchy, you first need to select the permitted characteristics in the InfoObject maintenance screen. See Tab: Hierarchy of InfoObject maintenance screen.

  • You have assigned an InfoArea to the characteristic in the InfoObject maintenance screen. This makes the hierarchy into an InfoProvider.

Procedure

1. Create a transformation.

  1. Create a transformation for your hierarchy.

    More information: Creating a Transformation for a Hierarchy

2. Creating an InfoPackage Project.

  1. Create an InfoPackage using the context menu of your DataSource.

    More information: Defining an InfoPackage

  2. Enter a description for the InfoPackage. Select the required DataSource (data type Hierarchies), and confirm you selection.

  3. On the Hierarchy Selection tab, select the hierarchy that you want to load into your BW system.

    If you want to load a hierarchy from an external system with BAPI functionality, configure the relevant BAPI-specific settings.

  4. Load a hierarchy from a file and configure the settings in the External Data tab.

  5. Configure the Processing tab.

  6. Configure the Update tab.

3. Create a data transfer process.

  1. In the context menu of the hierarchy, choose Create Data Transfer Process.

    More information: Creating Data Transfer Processes

    All the data from one hierarchy must be processed in one single package (if the field object ID is not filled with a unique ID for each hierarchy). The extractors usually return a hierarchy per request. In PSA the following scenarios affect the settings in the DTP:

    1. Old requests are saved in the PSA and the new request is updated immediately using a DTP:

      In DTP the setting Only Load Last Request must be activated - otherwise all old requests will be loaded. This option is available for DTPs in full mode.

    2. Only one request is loaded from the source at a time. The request is then updated using the DTP and then deleted from the PSA:

      Data can only be loaded using a DTP in full mode.

    3. Multiple InfoPackages are used to write several hierarchies to the PSA and the hierarchies are updated with a DTP:

      You need to use a DTP in the delta model with the option Request by Request Update to ensure that the data of a hierarchy is processed in one update.

  2. On the Update tab, set the Activate Hierarchy flag.

4. Define a process chain.

  1. Define a process chain and schedule it.

    More information: Loading Hierarchies Using a Process Chain

Result

The hierarchy structure and node texts or intervals are loaded. The structure information and hierarchy texts are stored in the BW system. You can edit the hierarchy.

You need to activate the hierarchy to use it for analysis and reporting.