Skip to main content

Creating Hierarchies

Prerequisites

In the InfoObject maintenance, the indicator with hierarchies is set for the relevant characteristic, meaning that the characteristic can have hierarchies.



Procedure

Step 1: Select the InfoObject tree in the Administrator Workbench.
If you have assigned the characteristic to an InfoObject catalog, select the corresponding InfoObject catalog for an InfoArea.
If the characteristic does not belong to an InfoObject catalog, select the Not Assigned Nodes InfoArea and the Not Assigned Characteristics InfoObject catalog.

Step 2:Select the characteristic for which you want to create a hierarchy, choose the context menu with the right mouse button, and then Create hierarchy.

Step 3:In the dialog box, enter the technical hierarchy name, or the hierarchy version if applicable, the time-reference, and at least one short description of the hierarchy. Confirm your entries. You come to the screen Maintain hierarchies. You can now define your hierarchy here.
Creating Nodes and Leaves

Step 4:Select the root and choose Edit ® Create nodes. Give the node a technical name and at least one short description.
Select a node that does not represent a value interval, and create a child node for it, or choose Edit ® Insert . You now see a list of the Characteristic values and can select one single value or various single values.
These InfoObjects deal with chargeable nodes. These are symbolized by the green InfoObject icons


If you want to include external InfoObjects in the hierarchy, you can do this using right mouse button ® Insert nodes for characteristic, or Characteristic in the menu toolbar.
These InfoObjects deal with non-chargeable nodes. These are symbolized by the green InfoObject icons.

If the hierarchy is allowed to involve intervals, then go to Right mouse button ® Create intervals, or Interval in the menu toolbar. Specify (for example, with input help), the value interval.


You can create intervals anywhere, even under chargeable nodes.

A hierarchy node, which represents a value interval, is an end node and cannot have child nodes.



Step 5:Repeat these steps until you have created all the nodes and the leaves.
To display, change, or delete nodes or leaves from the hierarchy, place the cursor on the node/leaf to be deleted, and choose Edit ® Change, display, delete nodes.




Saving and activating hierarchies

Save the hierarchy.
With the right mouse button, choose Activate hierarchy

Comments

Anonymous said…
Hello Im about to create a hierarchy, but as my infoo bject is being used everywhere, I would like to know, is there an extra step to adjust i.e. my data sources, extractions, cubes. Or just with the activation of the new hierarchy all my BI content using this infoobject will be updated?
Good day, I am having problems in the insert characteristics for the hierarchy. When I insert a characteristic, it then asks for the external infoobject, after inputting the external infoobject a list pops up to show the values for the characteristic. My problem is that it only shows 500 entries whereas my external characteristic have more than 500 records. How do i get all the values for my external characteristic?

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 button and act

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!

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