尤尼佳asap_hirearchy.docVIP

Hierarchies in SAP BW ASAP for the BW Accelerator Business Information Warehouse Information about and Examples of Using Hierarchies in the SAP BW Introduction This document provides background information on hierarchies used in the SAP Business Information Warehouse. Software Version Supported This document was written specifically for BW version 2.0B, but should apply to all versions of BW. References Loading InfoSource Data via Flat Files Multi-Dimensional Modeling with BW Authorizations and Roles Introduction, Definition and Terms Objectives The aim of this documentation is to explain the various options for modeling data using hierarchies in the SAP Business Information Warehouse, based on specific examples. This document is written for software version 2.0B. Definition and Properties A hierarchy models the grouping and structuring of a characteristic by individual evaluation criteria. A hierarchy in the SAP BW has the following properties: Hierarchies are created for base characteristics (characteristics involving master data) in the SAP BW. One example of a base characteristic is the cost center (InfoObject 0COSTCENTER). Hierarchies for the cost center can then be applied to both sender and receiver cost centers. Hierarchies are saved in special master data tables of a characteristic. They behave the same as master data, and are therefore valid for all InfoCubes and can be modified. Several hierarchies can be defined for a single characteristic. A hierarchy can contain a maximum of 98 levels. Hierarchies can be loaded from an R/3 System or from a file, or can be manually created and changed in the BW. The following diagram shows an example of a hierarchy in the BEx Analyzer: Hierarchical structures can also be modeled within an InfoCube, in the dimensions, or as attributes of a characteristic. Hierarchical structures that are modeled in dimensions cannot be changed without a comprehensive realignment, which is not contain