Multiple Key Figures in BPC

[former_member223749]

SAP BusinessObjects EPM

How-To

SAP BPC: Import Transactional Data into SAP BusinessObject BPC 7.5 from Netweaver BI Cube with Multiple Key Figures

Applies to:

SAP Business Planning and Consolidation for Net Weaver 7.5 SP 05.

Summary

This white paper demonstrates how to use process chains provided in SAP BusinessObjects Planning and Consolidation 7.5, version for SAP NetWeaver to transfer transaction data into SAP BusinessObject from BI Netwearer BI cube with single and multiple key Figures using the Planning and Consolidation Data Manager “Load Transaction data from InfoProvider”.

Author(s):    Akkamahadevi Padashetty

Company:    Sasken Communication Technology Ltd.

Author Bio

Akkamahadevi Padashetty is a Lead Engineer-SAP at Sasken Communications Technologies Ltd. She has also worked as Senior Software Engineer for ACS Systech Integrators Pvt Ltd. She has been part of implementation projects on SAP BPC NW in both the organizations. She also has more than 5 years of experience in SAP BPC NW.

Table of Contents

Create a Table of Contents in Microsoft Word. To change, right-click on the TOC and select Update Field.

Objective   3

   .1 Scenario 1 ................................................................................................................1

1. 1.2 Scenario 2 ................................................................................................................1
2. 1.3 Scenario 3 ................................................................................................................1

Header 3

Related Content 4

Copyright 5

1. Objective

Load transactional data from any Infoprovider in BW to the BPC Application with three scenarios.

1. Load transactional data from any Infoprovider in BW to the BPC Application with single figure.
2. Load transactional data from any Infoprovider in BW to the BPC Application with multiple figures.
3. Load transactional data from any Infoprovider in BW to the BPC Application using selection option.

The Data Manager module in SAP BusinessObjects Planning and Consolidations, version for SAP NetWeaver, utilizes SAP Process Chains, and provides a way for business users to execute these chains.

It focuses on how to handle common design approaches, any of which, you may encounter when integrating Cost Center transaction data into BPC.

2. Step-by-Step Procedure

3. Scenario 1

This scenario is to use the Data Manager in BPC7.5 NW to load transactional data from any Infoprovider in BW to the BPC Application with single key figure.

Within this scenario, we will show how to transfer data from BI to SAP BusinessObjects Planning and Consolidations, version for SAP NetWeaver using data manager “Load Transaction data from InfoProvider”.

This scenario overcomes almost all the limitations enumerated since this is executed from within BPC itself. This can very well be scheduled from within Data Manager or by invoking the Data Manager Process chain from a custom process chain.

3.1 BPC Transaction Data Transformation Files:

Before we run the data manager package to load data, we should prepare the transformation and conversion files. An example of a transformation file that we can use to load data from other infoproviders is given below.

Please note the mapping section. The dimension names in the BPC Application are mapped to the corresponding characteristics from the Infoprovider from where we want to load the data. Please note that as far as the BPC dimension names are concerned, we are using the dimension names (and not the technical names of the BW characteristics corresponding to those dimensions) whereas when we map them to the Infoprovider characteristics, we must use the technical names of the BW characteristics. For example, the TIME dimension in BPC is mapped to OCALMONTH characteristic in BW. Here TIME is the BPC Dimension name whereas OCALMONTH is the technical name of the BW characteristic in the source Infoprovider. Also please note the mapping for SignedData. The SignedData is mapped to the technical name of the key figure in the source Infoprovider. So in this case, ZORD_QTYR is the technical name of the key figure in the source Infoprovider.

4. Scenario 2

In this scenario source BW Infoprovider multiple key figures. If so, we can assign multiple key figures to single dimension as shown below.

Assign the key figures to Account Dimension in this file. We see 2 key figures in this example. We use this structure: ACCOUNT=*MVAL(ZORD_QTYR|*NEWCOL(ZORD_QTY1)||ZORD_QTYB|*NEWCOL(ZORD_QTY2)) Here I mean that ZORD_QTYR key figure is an account member like ZORD_QTY1 and ZORD_QTYB key figure is an account member  like ZORD_QTY2.

If for any reason, you have a situation where you have to get data from two or more key figures, you can use multiple key figure transformation files and run the data manager package with multiple key figure transformation file.

5. Scenario 3

To import the transaction data from BI cube, best option is make use of transformation file. In transformation file if we want to filter the records based on some conditions then we have to make use of option SELECTION where we will give the parameters as there is no option to pass the data from LoadInfoProvider Package to transformation file.

Here, the conversions for TIME dimension are read from the file TIME.xls. That conversion file can have the mapping between internal (BPC) time dimension members and external (0CALMONTH) values. That conversion file is shown below:

Here ? is used as a wildcard so that we don't have to write conversion for each year. This conversion file can work for any year. Another example of the conversion file for account is shown below:

Validating the transformation file:

After we prepare the transformation and conversion files, the next step would be to get the transformation validated with the source Infoprovider. BPC7.5 NW gives additional options for validation as shown below:

Running the data manager package:

Once we have our transformation files validated, we are in a good shape to run our data manager package to load the data from the source Infoprovider. There is a delivered process chain and data manager package to load data from Infoprovider as shown below:

If we run this package, we can enter the technical name of the source Infoprovider and the transformation file and schedule the load.

Upon completion, we can get the success message in the data manager package status as shown below: