Loading Hierchys Into FF From r3 and Then to BI

8/9/2019 Loading Hierchys Into FF From r3 and Then to BI

1/14

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

2009 SAP AG

Extraction of Hierarchy into FlatFile from R/3 and Loading in BWSystem

Applies to:

This article applies to SAP R/3 (any version) and SAP B/W (any version).For more information, visit theBusiness Intelligence homepage.

Summary

This document discusses the R/3 Tables involved in Extracting Hierarchies (mainly covered Cost CenterGroup Hierarchy and Cost Element Group Hierarchy), dump the hierarchy in Flat File in required BWstructure and Load the same to BW.

Author: Anil Suryavansi

Company: Patni Computer Systems

Created on:15 September 2009

Author Bio

Anil Suryavansi is presently working with Patni Computers Systems Ltd. He has workedextensively on SAP BIW 3.5, BI 7.0, different versions of R/3 and is mainly responsible forvarious BW and R/3 developments.
https://www.sdn.sap.com/irj/sdn/nw-bihttps://www.sdn.sap.com/irj/sdn/nw-bihttps://www.sdn.sap.com/irj/sdn/nw-bi


2/14

Extraction of Hierarchy into Flat File from R/3 and Loading in BW System


2009 SAP AG

Table of Contents

Introduction ......................................................................................................................................................... 3Cost Element Group Hierarchy in R/3 ................................................................................................................ 3

R/3 Tables Involved ..................................................................................................................................................... 4Code to Extract the Hierarchy:............................................................................................................................ 6How Hierarchy is shown at BW Reports: .......................................................................................................... 12Related Content ................................................................................................................................................ 13Related Content ................................................................................................................................................ 13Disclaimer and Liability Notice .......................................................................................................................... 14


3/14



2009 SAP AG

Introduction

In SAP R/3 for a Group (Ex: Cost Center Group or Cost Element Group), if any of Header node / Sub Node /Base Node is entered, hierarchy for that node appears. The same functionality can be achieved in B/W byloading a Single Hierarchy and with maintaining proper Link for an Organizational Unit. There are manyscenarios in which it is required to Extract Hierarchies from R/3 tables, dump Hierarchy in Flat File andLoad into B/W. Using same logic and code All the Group Hierarchies present in R/3 can be Extracted.

For Example:

Cost Center Group Hierarchy

Cost Element Group Hierarchy

Cost Element Group Hierarchy in R/3

We can check Cost Element Group in R/3 by T-code KAH3.

For an example, we consider a group KG-ALLCOST:

Now if we check for K585ADEPRE:


4/14



2009 SAP AG

Now if we check for K585AFIXDP:

By above example it is possible to check hierarchy of KG-ALLCOST, K585ADEPRE and K585AFIXDP, as allthese entries are maintained in SETHEADER table.

R/3 Tables Involved

Mainly 3 tables are involved to extract hierarchy:

SETHEADER

The value of field Set class represents that the hierarchy is related to which field, as value0102 is for Cost Element Group, 0101 is for Cost Center Group.

If we check Set ID KG-ALLCOST (Higher Node) entry is available in this table.


5/14



2009 SAP AG

SETNODE

If we check table SETNODE with Set ID KG-ALLCOST, there are 12 Subset Ids available.

If we now take any Subset ID ex. K585ADEPRE and check this as Set ID, there are two SubsetIDs for this.

Now if we take a Subset ID K585AFIXDP and check this as Set ID, there are no entries availablein SETNODE table as its a leaf node.

SETLEAF

If we take K585AFIXDP and check this as Set ID in table SETLEAF, it contains values of Cost

Elements assigned to the node.


6/14



2009 SAP AG

Code to Extract the Hierarchy:


7/14



2009 SAP AG


8/14



2009 SAP AG


9/14



2009 SAP AG


10/14



2009 SAP AG


11/14



2009 SAP AG

The above code will generate the file, which is compatible to load in BW in Master Hierarchy Object.


12/14



2009 SAP AG

How Hierarchy is shown at BW Reports:

Now we can Load this extracted Hierarchy in Cost Element Object and create a Hierarchy Node variableat query level for this hierarchy. In Selection Screen Hierarchy is available to select at different nodes.


13/14



2009 SAP AG

Related Content

Relation between SETNODE, SETLEAF and SETHEADER

Structure of a Flat Hierarchy File for Loading via IDoc

Hierarchy Nodes

Link Nodes

For more information, visit theBusiness Intelligence homepage.
https://forums.sdn.sap.com/thread.jspa?forumID=50&threadID=159787&messageID=1791791#1791791https://forums.sdn.sap.com/thread.jspa?forumID=50&threadID=159787&messageID=1791791#1791791http://help.sap.com/saphelp_nw04/helpdata/EN/c1/493d3854129f68e10000009b38f8cf/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/EN/c1/493d3854129f68e10000009b38f8cf/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/EN/b3/fa3d3806136268e10000009b38f8cf/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/EN/b3/fa3d3806136268e10000009b38f8cf/content.htmhttps://www.sdn.sap.com/irj/sdn/nw-bihttps://www.sdn.sap.com/irj/sdn/nw-bihttps://www.sdn.sap.com/irj/sdn/nw-bihttps://www.sdn.sap.com/irj/sdn/nw-bihttp://help.sap.com/saphelp_nw04/helpdata/EN/b3/fa3d3806136268e10000009b38f8cf/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/EN/c1/493d3854129f68e10000009b38f8cf/content.htmhttps://forums.sdn.sap.com/thread.jspa?forumID=50&threadID=159787&messageID=1791791#1791791https://forums.sdn.sap.com/thread.jspa?forumID=50&threadID=159787&messageID=1791791#1791791


14/14



Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is notsupported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article orcode sample, including any liability resulting from incompatibility between the content within this document and the materials andservices offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.

Documents

Loading Hierchys Into FF From r3 and Then to BI