Merge Hierarchy Data from a Source with Manual Assignments in SAP BPC
- by Sridhar Srinivasan, SAP BPC/BI Solutions Architect, Zebra Consulting, Inc.
- Kumar Srinivasan, SAP BPC/BI Senior Consultant, Zebra Consulting, Inc.
- July 13, 2012
See how to maintain a hierarchy in an SAP Planning and Consolidation (BPC) system that merges data originating from a source system (SAP NetWeaver BW) with manual assignments done in a BPC system. You can extend this method, which is applicable for the SAP NetWeaver version, to merge data from two different sources. It is scalable and can be used for any number of dimensions once the steps listed here are followed.
SAP Planning and Consolidation (BPC) enables data to be grouped and analyzed using a hierarchy. You can create multiple hierarchies on a single dimension to make the analysis of data flexible. In the process of maintaining hierarchies, it may be necessary to merge data from a single hierarchy from a source – say the hierarchy data from SAP NetWeaver BW – with manual assignments done in SAP BPC.
In some business scenarios, it is necessary to pull data from multiple source systems into an SAP Business Planning and Consolidation (BPC) system. For example, in an initial implementation of a planning application, the data may be brought from a legacy system via flat files. This would serve as the history data.
The data after go-live may flow from the SAP ERP Central Component (SAP ECC) system into SAP NetWeaver BW and then into an SAP BPC system. This is especially true of organizations maintaining data in multiple source systems or for those that are implementing an SAP system for the first time. There may also be cases in which master data is maintained in the BPC system and is not available in the other SAP systems. The data in the BPC system is the one that is primarily required for reporting. These requirements call for master data to be maintained from more than one source such as a legacy, SAP ECC, or BPC system.
The ability to create hierarchies to group data inside a dimension helps in analyzing data. For example, if a company is involved in two business areas, say beverages and snacks, the data associated with beverages and snacks can be identified separately under a hierarchy and analyzed. This grouping could help the organization to determine how well each line of business is performing.
While the hierarchy data is clean when it is bought from one source system, it becomes muddled when the data is bought from a source system and customized with manual assignments. For example, when a hierarchy is brought from an SAP NetWeaver BW-based hierarchy into BPC, any hierarchy mappings maintained manually for the same hierarchy are lost. This presents a challenge in maintaining the hierarchies. The question is how to maintain the manual mappings when you load a hierarchy from SAP NetWeaver BW.
Our solution is based on SAP BPC 7.5 and earlier versions. Basic knowledge of ABAP is required to complete the steps outlined in this article. We have included the ABAP code for you to use as part of our solution.
Would you like to see this full item?