Pulling data from different BPC Model

[former_member222556]

BPC Data PULL mechanism

Across Model data copy

Applies to: SAP BPC 10 NW/MS

Summary

This Article will explain how we can pull data from different model of an environment using standard script logic.

Author: Obaidullah Shaikh

Company: Alexion Business services

Created on: 28 November 2014

Author Bio

Obaidullah Shaikh is a SAP BW/BPC/IP/BO Associate manager with Alexion business services.

Table of content

• 
  Introduction
  


• 
  Script Logic in Source Model
  
  • 
    DESTINATION_APP Keywords
    
  
  


• 
  DM Package in Target Model
  


• 
  Create a DM Package
  


• 
  Conclusion
  

Introduction

This article addresses the copying data from one model to another using Push and Pull mechanism.  SAP has given a standard function called DESTINATION_APP for pushing data from one model to another model of an environment.

But we can also pull data using the same function by making some change in Data manager package.
This function will be working as it is but we will be calling this from target
model instead of source model.

Script Logic in Source Model

Create the DESTINATION_APP script logic in source model with all the required parameters. The DESTINATION_APP keyword allows you to write the results of calculations to a different application.

Here, we have two models with same dimensional structure, So we have written a simple DESTINATION_APP logic without any other key word. We are just copying data from source model to target model with the change of Category version.

DESTINATION_APP Keywords

• If destination application shares only some of the dimensions of the original application then, the missing dimensions can be dropped from the original records with the instruction:

*SKIP_DIM= {dimension name}[,{dimension name},…]

When the original application has dimension that are not found in the destination application, the SKIP_DIM keyword is mandatory.Validation cannot pass without the SKIP_DIM keyword.

Multiple dimension names can be supplied to the instruction separated either by commas or by multiple SKIP_DIMinstructions entered on separate lines.

• If the destination application has dimensions that do not exist in the original application, these can be added to the passed records,using the instruction:

*ADD_DIM {dimension name}={value}[,{dimensionname}={value},…]

Multiple dimension names and values can be supplied to the instruction separated either by commas or by multiple ADD_DIM instructions entered on separate lines.

• The keyword RENAME_DIM can be used, to change name of one or more dimensions. The syntax is:

*RENAME_DIM {dimension name}={value}[,{dimension name}={value},…]

This instruction can be used when data is to be written into an application where a dimension is named with a different ID. Multiple dimension names and values can be supplied to the instruction separated either by commas or by multiple RENAME_DIM instructions entered on separate lines.

DM Package in Target Model

Create a DM Package

Data Manager is a Business Planning and Consolidation (BPC) module that helps you move data in to BPC, as well as copy or move data within and across applications. In addition to allowing you to move and copy data, Data Manager supports mapping and complex transformations of data. It also allows us to trigger the Script logic (Calculation engine) to do any kind calculation.

Assign process chain and Task type. Click on Modify script.

In the DM Package script where you mention the script logic, you need to mention the Source Model name instead of parameter and Source model script logic.

Conclusion

Since package is created in Target model, user can only that from Target but that package will trigger the script created in Source model. That means even though system works like push mechanism but that is transparent for the end user.