Skip to main content

Introduction to SAP Hierarchies

Definition

A hierarchy is a method of displaying a characteristic structured and groupedaccording to individual evaluation criteria.A BW hierarchy has the following properties:

Hierarchies are created for basic characteristics (characteristics containing master data).The characteristic 0COSTCENTER is an example.

Hierarchies are stored in master data tables. They are also similar to master data, and can therefore be used and modified in all InfoCubes.

You can define several hierarchies for a single characteristic.

A hierarchy can have a maximum of 98 levels.

You can load hierarchies from the R/3 system, or from a flat file. You can also create andchange hierarchies manually in the BW system.

Use:

Hierarchies are used in two main ways:

1. Firstly, the structured display of characteristic values (tree display) in a presentation hierarchy.

2.Secondly, selecting a defined quantity of characteristic values as a selection of hierarchy nodes.

Structure
A hierarchy consists of nodes. A node can be assigned to a higher level node.There is exactly one top node (root). All nodes on the same level of the hierarchy(nodes that are the same distance away from the root) form a hierarchy level. Acharacteristic hierarchy consists of nodes that can and nodes that cannot be posted to

. Hierarchies can be created only for those characteristics that do not reference other characteristics.



The characteristic "Cost Element" can be structured according to cost elementgroups. The highest hierarchy level consists, for example, of personnel costs,material costs, administration costs, and so on. Personnel costs are divided up,for example, into the cost element groups pay, salaries, and personnel overhead
costs. The cost element group ‘pay’ contains the cost elements ‘individual paycosts’, ‘pay overhead costs’ and ‘other pay costs’


Another typical example of a characteristic hierarchy is the grouping of the characteristic Region into districts that are themselves sub-divided into areas


Hierarchies



Load characteristic hierarchies from a source system

The source system can be an R/3 OLTP system or an external system (BAPI, file). If you want to load a hierarchy from an external system, you have to first maintain the Metadata for this hierarchy. You can load a hierarchy directly from an R/3 system



1. oading Hierarchies

2.create characteristic hierarchies in the Business Information Warehouse


If you are working with aggregates and are loading or creating new hierarchies,or changing existing hierarchies, you have to reconstruct the aggregates that areaffected by the changes afterwards

Prerequisites

You have to determine in the InfoObject-Maintenance whether or not you want the characteristics to have hierarchies. The properties of the hierarchy (for example,the
hierarchy versions,time-dependent hierarchy structure) are also defined here.
Labels:

Comments

Post a Comment

Popular posts from this blog

Step by Step guide on BADI with Filter implementation

Step 1 à Before implementing filter objects to a BADI. We need to deactivate all the implementation for that BADI. Go to SE18 (BADI definition) and from there navigate to all BADI implementation to view all the active implementations for that BADI Select the BADI implementations listed on the screen and deactivate the implementation. Once done, return back to the initial screen of SE18 and proceed with next step. Step 2 à go to SE18 – BADI Definition screen and change the existing BADI definition that we created in the earlier tutorial.   Select the FILTER –DEPENDENT check box under the TYPE section. This will open up the FILTER TYPE field for inputs. And do an F1 on the FILTER TYPE field. Click on the F4 on the FILTER TYPE field name and enter some search criteria to find a relevant data element. And click on the continue button   Select the data element from the list to set up your filter and hit enter. Click on the save butto...
1 comment
Read more

Create Data Source in SAP

Data Sources are extraction structure. Data Sources are used to extract data from various source system. In the below steps, we will see how to create a data source using a SAP table VBAK. 1) Execute transaction RSO2 2) Enter data source name to be created 3) Press Create 4) Enter description of the data source 5) Enter the name of table or view on which data source has to be created. Data Source can also be created using a View, Info set or a Function Module. 6) Save the data source 7) Execute RSO2 again and click Change 8) Select VBELN field as selection 9) Save the Data Source 11) To check whether data is getting extracted, execute transaction RSA3 12) Enter the name of data source as shown below and press 'Extraction' 13) An information message will appear stating no. of records fetched 14) Additional button 'Display list' will appear, press button 15) Select one of the data packet and double click to get records fetched 16) Data Source is ready to be used!
4 comments
Read more

Responsibilities of BW Data Architect

Responsibilities of an implementation project... For ex, Lets say If its a fresh implementation of BI or for that matter you are implementing SAP... First and foremost will be your requirements gathering from the client. Depending upon the requirements you will creat a business blueprint of the project which is the entire process from the start to the end of an implementation... After the blue print phase sign off we start off with the realization phase where the actual development happens... In our example after installing the necessary softwares, patches for BI we need to discuss with the end users who are going to use the system for inputs like how they want a report to look like and what are the Key Performance Indicators(KPI) for the reports etc., basically its a question and answer session with the business users... After collecting those informations the development happens in the development servers... After the development comes to an end the same objects are tested in quality...
1 comment
Read more