Skip to Content

Summary

Data manager packages are used to upload master and transaction data into BPC system,  in BPC 10.0 version,  the prompts or parameter values have been changed to fulfil different needs of data upload. In this document, we will understand the functionality of BPC 10.0 Data manager Packages and how it is different from BPC 7.5.

Author    :        Sreekanth Surampally

Company:       Accenture Technology Inc. Canada

Created on:     Sep 11 2014

Sreekanth is an SAP BI  and BPC Consultant in Accenture Canada,  he has done BI implementations for various Clients in North America. Currently he is working on BPC development and upgrade projects.

Introduction,

BPC Administrator uses several DM packages to run the data uploads to Planning models an Dimensions,  it is very important to understand how each option works when you are triggering them,  SAP help information is all accross on this topic but not consolidated, So I thought of keeping every thing at one place.

The common Data manager packages used in BPC are

  • Load transaction data from flat file
  • Load transaction data from BW infoprovider
  • Copy
  • Load master data attribute from BW
  • Load Hierarchy from BW
  • Currency Conversion(FX revaluation)

All of them are explained below,

  Load transaction data from flat file

This DM package is used to load transaction or master data from flat into BPC model. Once the file is updated to BPC server,  we start uploading to BPC objects. Let us see what options we have while executing this,

First prompt is,  Import file.  The flat file which needs to be imported will be selected, – Not changed from BPC 7.5 version.

Second prompt, transformation file,  select the transformation file used for mapping of the data fields – Not Changed from BPC 7.5 version.

Thirid Prompt,  Update mode options,   Overwrite and Replace data.   – This is Changed.

Image 1.jpg

Overwrite Option: It overwrites the existing record with new record,  Technical Characteristics do not come into considering while looking for the matching key.  Matching key is all the dimension values from source and target. For example, if the applciation has the record as below,

100020  AG123450 10.2013  200$

if the new record from flat file is having as below,

100020 AG123450  10.2013 50$ 

then after loading this record to model,  there will be 2 records like below,

100020  AG123450 10.2013  200$

100020  AG123450 10.2013  -150$

-150$ is made up of -200$ before image 50$ after image, total it is -150$    Overwrite means technically it does not overwrite the existing record in the model, as it does in BW DSO. It posts a negative to existing record first and then gets the new record. Because model is technically a BW Cube, it is always adding records.

Replace data:It is more of deleting the existing records where Category, Entity and Time dimension matches. It does not look all the characteristics into consideration while deleting it. For example, if we have a record with Account time and WBS element(entity) Char as above,

100020  AG123450 10.2013  200$

Your newly updating record is as below,

100014   AG123450 10.2013  50$

What happens in this case,  it deletes the current record first though the new record has a different account number but does not care it delets entire record because it only look time Dimension and Entiry Dimension which are same in this example.  Then load the new record to Cube, it will be

100014  AG123450  10.2013  50$.You see the difference between the 2 types of options, so it is more often to use the Overwrite option than Replace.

What is different from BPC 7.5,In BPC 7.5,  you will see update mode screen with different prompt descriptions,

Image 2.jpg

With the ENVIRONMENTSHELL activation in during BPC 10.0 upgrade, the above prompts are changed to BPC 10.0 prompts,

But technically, there is no difference between the options

Merge  <— > Overwrite

Replace & Clear  < — > Replace

So after upgrading the system, you will use the corresponding prompt options without further changes.Prompt 4,  Selection of Aggregation type,  Pre aggregate or take a last record. This is new prompt setting appears only in BPC 10.0, below is screen shot,

Image 3.jpg

if you choose, Pre aggregate,  records with same key are summed up for the amount values,  other case, last record is chosen, then last record value is taken into consideration for uploading. The next prompts on this package have no change in the latest version.

Load transaction data from BW Infoprovider

This is used to upload data from SAP BW infoprovider to BPC model,  most of the prompts work as they are for flat file package discussed above except the below one. The update mode of this DM package has an additional parameter now,  that is ‘Append’.

Image 4.jpg

With this option all source records are just appened to Model, it does not look the characterstic combination is already available in BPC or not. When you migrate System to BPC 10.0,   this DM package selects ‘APPEND’ option by default, you need to change to either Overwrite or Replace according to your BPC 7.5 option. It is a manual step during upgrade.

Copy

Copy DM package is used to copy records from one dimension to other dimension value, also copy records from one model to another model.Example,  you can apply this function to Category dimension, Copy from ACTUAL to FORECAST, so the amount values in ACTUAL category are copied to FORECAST. The options are,

Image 5.jpg

With mach key option, the target selection records overwrites the existing records in the model, if there is a record already and matches.For example: If model has already the following records,

ACTUAL   2000$

FORECAST  3000$

If we run a copy function to copy the value  ACTUAL to FORECAST,   in the target,

FORECAST 3000$

FORECAST  -1000$

-1000$ is the result  of -3000$  and 2000$  which are generated as part of the copy function.  So it is pretty much same as Overwrite option in Load transaction data.Copy by replacing data,  exactly works as Replace option described in Load transaction data.

Move DM package also works in similar way,  the difference between COPY and MOVE is,  MOVE will delete the source record which is

getting moved to target.

Load master data attribute from BW

This DM package is used to load the master data attributes to BPC Dimension,  the prompts have no change in BPC 10.0  but few points to take care while running the package.

  • You Can also set up a filter on Hierarchy, name of the hierarchy and to which level it can be expanded while loading the node values.
  • Choosing the option ‘Filtering by Hierarchy or Attribute’   ‘filtering by Hierarchy and attributes’ will make a difference in the update.
  • AND option will look for the records matches the selection on both attributes and Hierarchy, or will get both sets of records into BPC,  to get the hierarchy nodes as base members it is important to use OR condition.
  • External or Internal format,    External will remove the preceding 0 on the dimension value.
  • Always use the update option, so that existing data in BPC will not be changed, for example if you use overwrite and do not have a mapping in the transformation to that property/attribute, system will overwrite the value to blank.

More information on this DM package is explained the SAP document,

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c02d0b47-3e54-2d10-0eb7-d722b633b72e?QuickLink=index&overridelayout=true&50843823515844

Load Hierarchy from BW

Purpose of this package is to update the parent nodes in the hierarchy, This package also does not have any change in the functionality of BPC 10.0

  • Conversion file tells about the mapping of BW hierarchy to BPC hierarchy whether it is ParentH1 or ParentH2 etc.
  • No hierarchy nodes will be created as base member IDs as part of this execution.
  • Node name is all the hierarchy nodes(0HIER_NODE) but not the infoobjects.
  • Node name is placed in ParentH1 for the members which are children to that parent node. If there is a condition to that to
    check source node name is hierarchy node or not.
  • So pre requisite for hierarchy update is,  hierarchy has to be updated/created as a base member first before it is updated to ParentH1.

  This is also explained with different scenarios in the following document

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c02d0b47-3e54-2d10-0eb7-d722b633b72e?QuickLink=index&overridelayout=true&50843823515844

FX Revaluation

Purpose of this DM package is to convert the currencies,  With BPC 10.0 Upgrade, GROUP_ID Dimension has become part of DM pacakge prompts, so if we are not using the GROUP_ID then you will have to replace that with Category Dimension,

The detailed explanation on this correction is explained in the SAP note 1784801

Note: CLEAR,  Light Optimize, Open/Close DM packages do not have any changes to their prompts and functionalities. They exactly work as in BPC 7.5.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply