SAP NetWeaver BW 7.30
Load Hierarchy Data Using 7.0 Dataflow from Any Source

  • by Rakesh Kalyankar, SAP NetWeaver BW- and HANA-certified consultant, SAP
  • May 15, 2013
Learn how to load hierarchy data using 7.0 dataflow technologies, such as transformations and Data Transfer Processes, from any source.
Key Concept

SAP has enhanced the hierarchy loading method by allowing use of 7.0 dataflow technologies. With SAP NetWeaver BW 7.30, you can load hierarchy data using transformations and Data Transfer Processes. With prior versions of SAP NetWeaver BW, you could load hierarchy data using only the direct update method of loading master data and hierarchy. This older, inflexible method uses the dated 3.x dataflow, which has limitations. 

SAP improved dataflow technology with its release of SAP NetWeaver BW 7.0. I consider this feature a key reason for upgrading from SAP NetWeaver BW 3.x to the higher version.

Version 3.x’s processes were rigid. Source system objects were tightly coupled with BW InfoProviders, and there was no separation between the persistent staging area (PSA) loads and loads to InfoProviders in most cases. SAP NetWeaver BW 7.0 enabled you to load data to the PSA independently and provided more flexibility in building and maintaining the data warehouse. However, there was still a problem: Loading hierarchies still had to be performed using old dataflow methods. SAP decided to leave out Data Transfer Process (DTP) support for hierarchy load, leaving many users disappointed. SAP listened to its customers and now has enabled hierarchy load with new dataflow technology that uses transformations and DTPs. This new technology is known as 7.0 dataflow.

Dataflow technology only has two versions: 3.x and 7.0. For any SAP NetWeaver BW 7.30 system, you use dataflow 7.0 technology.

Limitations of the Old Approach

Let’s look at the major pain points of loading hierarchy data using the old 3.x dataflow in an SAP NetWeaver BW 7.0 system.

With SAP NetWeaver BW 7.0, loading hierarchy data was via the direct update method, which had the following limitations:

  • After upgrading to 7.0, you could migrate all your master data and transactional dataflows to the 7.0 dataflows, but you had to retain the hierarchy flows in the 3.x dataflow. That limitation meant you had to maintain two sets of dataflows in your system.

Rakesh Kalyankar

Rakesh Kalyankar is an SAP NetWeaver BW- and HANA-certified lead and architect, working with SAP Global Delivery in Bangalore, India. He speaks regularly at events, such as SAP TechEd and BIIG. He is also an SAP trainer and writes frequently about SAP NetWeaver BW and SAP HANA topics. Prior to his starting his consulting work, he was part of the SAP NetWeaver BW research and development team at SAP Labs, and he has worked on the development life cycles of SAP NetWeaver BW releases, including versions 7.30 and 7.03.

If you have comments about this article or would like to submit an article idea, please contact the BI editor.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.