elite bpc 7.5 nw partner trainingdocshare04.docshare.tips/files/25802/258020409.pdfelite bpc 7.5 nw...

ELITE BPC 7.5 NW PARTNER TRAININGData Loading from Flat File to BW to BPC

Enterprise Performance Management RIG

© 2010 SAP AG. All rights reserved. /

Moving Data for BPC

Planning and Consolidation (BPC) has a number of unique features that need to be considered when attempting to move data in/out of the application:

• BPC has a protected namespace (/CPMB/). This prevents BPC from directly interacting with much of the BW environment. Note: this feature is by design allow independence of the data model from corporate EDW processes and models.

• BPC has an unique data model (no BW “Time” or “Unit of Measure” characteristics. This feature requires transformation of the inbound BW data into the BPC data model.

• BPC is a single key figure model, while BW data models are typically multiple key figure based. This feature also therefore requires a transformation of the inbound BW data to allow loading the BPC data model

• Planning data needs to be aggregated to a higher level than data typically used fro actual reporting (i.e.: planning data is usually presented in monthly buckets, while BW reporting data may be weekly or even daily).

The above considerations require specific designs to efficiently move data from ECC into BW, and then into a BPC environment. Fortunately Netweaver has the Extract, transform, and load (ETL) tools to make this job easy!


Moving Data for BPC

SAP Business Warehouse (BW) is the data warehouse application for Netweaver. BW has a multitude of delivered content that can be activated to extract data from a variety of SAP (i.e.: ECC, APO, CRM) and non-SAP based systems. A few of these tools are:

• Extractors – small programs that make data connections to systems outside of the home BW system. These extractors can modify the form of the data (i.e.: change field from 8 characters to 6).

•Transformations – allow the mapping of one data model to another.

• Open Hub - is a service that enables the distribution of data from an SAP BW system into an external data marts, analytical application, or various other applications

•Business Application Programming Interface (BAPI) is used to extract data from non-SAP sources. BAPI serves the purpose of connecting third- party ETL tools to SAP BW.

•DB connect – allows the extraction of data directly from the underlying database

•Data Transfer Processes (DTPs) are used within BW to transfer data from one data target to another (i.e.: from the PSA to an info provider)


Moving Data for BPC

The focus of this presentation is to demonstrate a basic method of data loading for BPC objects:

1. The extraction of data from ECC is simulated in our example though the use of a prepared flat file. More typically the BW system would connect to the ECC system via the extractor and make a logical connection to move this data. The Data Source defines the location of the source data.

2. Data is loaded into the PSA (Persistence Staging Area) via the instructions defined within the infopackage.

3. A transformation is created to map the source data in the PSA into a targeted data model in another BW object (i.e.: info provider (for records), info object (for master data)).

4. A Data Transfer Processes (DTP) controls the movement of data from the PSA into the targeted info object and/or info provider.

5. Data is then moved again into a “BPC friendly” info provider call a Staging Cube. Atransformations and DTP are use to facilitate the transfer.

6. Finally the data from the Staging Cube is loaded into the BPC application through the use of standard BPC Data Manager tool ( transformation files, conversion file, and data manager package).


Data Records Flow

Flat File record:

0FIGL_C10 record:

Staging Cube:

BPC

Data Load (with Filtering)

DTP Load

DM Load


Data Records Flow

0FIGL_C10 Cube

Flat File record

Data Flow

Z_STAGE Cube

BPC Planning Cube

Filtered in DTP


Data flow from ERP to BPC

General Ledger Account

FI/CO or other

Extractor Extractor

0G\L_AccountFI/CO Actual Cube

BPC FI Planning

Cube

Planning and Consolidation

P_ACCT

SAP

ERP

SAP

Net

Wea

ver B

W S

yste

m

SAP

Net

Wea

ver

BW

ED

WSA

P B

usin

essO

bjec

ts

Plan

ning

and

C

onso

lidat

ion

Two paths are illustrated here: one for master data and one for transactional data.

The master data process uses delivered BW extractors to access the ECC definition tables. The data is pulled into BW and placed into a BW info object call a characteristic.

The second path details the load of transactional data. As with the master data process, delivered extractors pull data into BW and place the records in a BW info provider (cube).



0FIGL_C10 Z_STAGE /CPMB/PLANNING cubeFlat File

1. Data is loaded from Flat file to the 0FIGL_C10 cube

2. Data is loaded from 0FIGL_C10 standard cube to the Z_STAGE cube (Staging cube)

3. Using the data manager package , data is loaded from Z_STAGE cube to BPC Planning cube


Info Providers

Info Providers are the central multidimensional data model in BW. An Info Provider describes a self-enclosed data set encompassing one or more related business processes.

There are several types of Info Providers :

•Info Cubes (Basic and Real Time)

•Virtual Providers (loaded at run time)

•Data Store Objects (flat structures that lack many of the mufti dimensional features of cubes)

Info Cubes (Info Providers): physically contain data in the database

Virtual Providers: Represent logical views of a dataset. Data is stored only at runtime.

In this entire BW class 0FIGL_C10 standard cube will be used for loading the data.

Two sub types of InfoCubes:

•Standard InfoCube and

• Real-time InfoCube (Transactional cube)


Data flow from ERP to BW

Different type of source systems

Flat File, ERP system, BW system , APO, CRM, non-SAP, etc.

Extractors are used to move data from the source into the BW system

Infopackages are used to move data from source system to PSA

Transformations are built to map the fields between the source and target

Data Transfer Process are used to move the data from the PSA to Target i.e. characteristic or infocube or keyfigure


Source Systems

Flat Files for which metadata is maintained manually by BI and data is transferred to BI using a file interface

Database management systems into which data is loaded from a database supported by SAP using DB Connect without using an external extraction program

Relational or multidimensional sources that are connected to BI using UD connect

Web Services that transfer data to BI by means of a push

Non-SAP systems for which data and metadata is transferred using staging BAPIs


Data flow from Flat File to InfoCube




0FIGL_C10

Flat File SS

InfoPackage

DTP



Source Systems

Source system type is determined in the source systems area of the Data Warehousing Workbench


DataSource Systems

A DataSource comprises the quantity of logically related fields that provide the data for a business unit for data transfer to BI. You need to create a separate DataSource for transaction data and for Master data (each for Texts, Attributes and hierarchies). The data source in the exercises identifies where the flat file is located.


InfoPackage

An InfoPackage determines what data from which DataSource and from which source system are requested and written to the BI entry layer, the Persistent Staging Area (PSA).


Transformation

Transformation process defines mapping rules and ability to aggregate and filter data


Transformation

Transformation process allows to map the source fields to the target fields

Source

Target


Transformation

Click on each arrow (mapping rule) to view the rule details. Accept system generated proposal:


Transformation

Transformation rules can be created to provide target defintion when ther is no source. In the exercise example, the target Fiscal Variant field is defined by a rule that sets this to a constant value (K1).


Transformation

Transformation rules can in some cases be very simple. In the example below, the transformation provides a Direct Assignment between the source and the target fields. No conversion routines are used in this mapping definition.


Transformation and mappings

Characteristic Info Objects Transformation 0FIGL_C10 cube Const Value

Chart of accounts Mapped 0CHRT_ACCTS

Company code Mapped 0COMP_CODE

Controlling area Mapped 0CO_AREA

Cost Center Mapped 0COSTCENTER

Currency Type Constant 0CURTYPE “00”

Functional area Mapped 0FUNC_AREA

G/L Account Mapped 0GL_ACCOUNT

Profit Center Mapped 0PROFIT_CTR

Segment for Rep Constant 0SEGMENT “#”

Valuation View Constant 0VALUATION “0”

Value Type for Reporting Constant 0VTYPE “10”

Version Constant 0VERSION “V00”

Key Figure Info Objects:

Cumulative Balance with CURRYKEY Mapped 0BALANCE

Total Debit Postings with CURRYKEY Mapped 0DEBIT

Total credit postings with CURRYKEY Mapped 0CREDIT



Time Characteristic Transformation 0FIGL_C10 cube

Fiscal year Mapped 0FISCYEAR

Fiscal year / period Mapped 0FISCPER

Fiscal year variant Mapped 0FISCVARNT

Posting period Mapped 0FISCPER3


DTP

Data Transfer Processes (DTPs) are used to transfer data within BW from the PSA to another object (0FIGL_C10 in the example shown) in accordance with transformations and filters.


Data Records Flow

0FIGL_C10 Cube

Flat File record

Data Flow



Data flow from 0FIGL_C10 to Z_STAGE


Staging Cube

The main objectives in using a staging cube is to:

1. Provide a BW target to aggregate records form multiple BW sources of dataFor example: data from HR, CRM, APO, non-SAP systems can be collocated in the staging cube and minimize any additional BW security and administration. The staging cube can then become a one stop shop for BPC data.

2. To simplify the BW to BPC ETL processCreating a staging cube with a data model similar to the target BPC application allows the business user to take a more simplified approach to BPC Data Manager ETL design (in other words, the BPC transformation and conversion file designs can be relatively simple).

3. Provide disaggregation of the BW multiple key figure data model into a single key figure based data model (similar to BPC).


Data flow from BW cube to Z_STAGE cube


DTP

0FIGL_C10

Flat File SS

InfoPackage

Z_STAGE


InfoCubes

Object Overview of the 0FIGL_C10 cube (note the use of four key figures!)

Four Key Figures!


Staging Cube

Staging cubes are used extensively within BPC to summarize data from multiple sources and to pre-format data.

Note that the number of info objects and key figures are significantly different from the 0FIGL_C10 cube. A major function of the staging cube is to organize the BW key figure based data model into an account based (single key figure based) data model.

One Key Figure!



Characteristic Info Objects 0FIGL_C10 cube Transformation Z_STAGE Cube

Chart of accounts 0CHRT_ACCTS Filtered Selection in DTP

Company code 0COMP_CODE Not Mapped

Controlling area 0CO_AREA Concatenated w/ PCN

Cost Center 0COSTCENTER Not Mapped

Currency Type 0CURTYPE Not Mapped

Functional area 0FUNC_AREA Not Mapped

G/L Account 0GL_ACCOUNT ==> Z_ACCT (Account)

Profit Center 0PROFIT_CTR Concatenated w/CO_AREA

Segment for Rep 0SEGMENT Not Mapped

Valuation View 0VALUATION Not Mapped

Value Type for Reporting 0VTYPE Not Mapped

Version 0VERSION Not Mapped


Cumulative Balance 0BALANCE ==> Z_SDATA (and Z_ACTY=F00)

Sales for the Period 0SALES Not Mapped

Total Debit Postings 0DEBIT ==> Z_SDATA ( and Z_ACTY=F10)

Total credit postings 0CREDIT ==> Z_SDATA ( and Z_ACTY=F20)



Time Characteristic 0FIGL_C10 cube Transformation Z_STAGE Cube

Fiscal year 0FISCYEAR Not Mapped

Fiscal year / period 0FISCPER ==> FISCPER

Fiscal year variant 0FISCVARNT ==> 0FISCVARNT

Posting period 0FISCPER3 Not Mapped

Unit:

Currency key 0CURRENCY Not Mapped

Other fields:

Change Run ID 0CHNGID Not Mapped

Record type 0RECORDTP Not Mapped

Request ID 0REQUID Not Mapped


Transformation

Within the transformation definition, rules can be created to provide additional technical transformations between source to target data. In the exercise, the 0FIGL_C10 field FISCPER field mapped to 0FISPER field of Z_STAGE cube the technical mapping id relatively simple: a seven character field is mapped into a seven numeric field. This mapping is easy to perform since the system recognizes 0FISCPER as a specific characteristics called a Time Characteristics, and thereby has an arsenal of predefined functions (called conversion routines) to convert one time format into another.


Staging Cube: Transformation and Rule GroupTime Characteristic based rule for 0FISCPER


Staging Cube: Transformation and Rule GroupProfit Center is compounded characteristic that requires the definition of a controlling area to fully define a specific profit center. BPC does not have characteristic compounding feature, as a result the current best practice is to concatenate both characteristics (Controlling Area and Profit Center) to define a unique profit center key. To accomplish this in our transformation rule, select the Rule Type “Formula”


Staging Cube: Transformation and Rule GroupDirect Assignment for Z_ACCT


Staging Cube: Transformation and Rule Groups

Rule Groups can be used to easily transform a multiple key figure based data model intoa single key figure based model.

The Standard Rule Group can be defined for one key figure, and at the election of thedeveloper, can be copied as a template into a number of new rule group definitions(thereby minimizing redundant configuration).

These new rule groups would each process a different key figure from the source data.

In the exercise for this topic, the standard rule group is initially defined to process the0BALANCE key figure. Subsequent rule group definitions copy this standard rule group(preserving the mappings for many of the source and target fields). The copiedstandard rule group is them modified by re-pointing it to another key figure (such a0CREDIT or 0DEBIT) .

To identify which key figure spawn which Staging record, the characteristic Z_ACTY isidentified in each rule group to correspond to Balance, Credit, or Debit.


Staging Cube: Transformation and Rule GroupsSAP NetWeaver BW provides standard functionality called “Rule Groups” to transpose a source record with multiplekey figures into multiple records with one key figure. For this transformation we will use the concept of Rule Groups todefine how each multiple key figure based 0FIGL_C10 record will be broken into three separate single key figurerecords in the Z_STAGING cube. The first rule group (called the Standard Rule Group) will define how the0FIGL_C10 record’s 0BALANCE key figure will be processed.


Converting SAP ERP Data to a Generic One Key Figure ModelFor this transformation we will use the concept of Rule Groups to define how each multiple key figure based0FIGL_C10 record will be broken into three separate single key figure records in the Z_STAGING cube. The first rulegroup (called the ZDEBIT Rule Group) will define how the 0FIGL_C10 record’s 0DEBIT key figure will be processed:


Data Transfer Process

A Data Transfer Process (DTP) provides the framework to move data from within the BW system. Data can move from Cube to cube, DSO to Cube, Info Object to Cube. The DTP can execute the data movement as defined by a transformation.

In the exercises associated with this presentation, a DTP is created to move the data from the 0FIGL_C10 cube into the Z_STAGE staging cube

.


Data Transfer Process

DTP is created to load the data from 0FIGL_C10 and Z_STAGE

The DTP filter selects only those records associated with a specific chart of accounts

Source & Target


Staging Cube Load Results

End result of the Staging cube load:•The concatenation of the controlling area and the profit center•The multiple Z_ACTY value corresponding to the three key figures: 0BALANCE, 0CREDIT, and 0DEBIT (transformation into a single key figure model).•Filtering of the Chart of Accounts


Data Records Flow

0FIGL_C10 record:

Staging Cube:

DTP Load


Data Records Flow

0FIGL_C10 Cube

Z_STAGE Cube

0CHRT_ACTS record with value “2” is Filtered in DTP


Z_STAGE to BPC Application

Data flow from Z_STAGE to BPC Application


Z_STAGE to BPC Application

Once the staging cube is loaded the next process uses standard BPC ETL tools (Data Manager packages) to load the data from the staging cube into the BPC application.

Data Manager will use a standard BPC mapping tool, call a transformation file to map the fields fro the source to the target data model.

A conversion file is used to changed the format of some source data (fiscal period) into the standard BPC time format YYYY.MMM).

A standard Data Manager package brings all of these objects together (source, target, transformation, and conversion).

© SAP


Staging cube to BPC Planning Application


BPC DM Pkg

0FIGL_C10

Flat File SS

InfoPackage

Z_STAGE BPC Cube

DTP


Load data from Z_STAGE to BPC Cube

Staging cube and the BPC Planning Application



Z_STAGE Cube Mapping /CPMB/PLANNING

Z_PCN BPC Transformation file ENTITY

Z_ACTY BPC Transformation file P_Activity

Z_ACCT BPC Transformation file GL_ACCT

* BPC Transformation file Category = ACTUAL (constant)

* BPC Transformation file P_DataSrc = BWLOAD (constant)

* BPC Transformation file RptCurreny = LC (constant)

0FISCPER BPC Transformation /Conversion file TIME


Z_SDATA BPC Transformation file SignedData


BPC Transformation and Conversion Files

Transformation file in BPC Conversion file in BPC

Source & Target Mapping

Source & Target Conversion



Data Manager package defines the source (the info provider identified in the first box, the target (the calling BPC application) , the transformation. The transformation file defines the specific conversion file(s) to be used.



Staging cube and the BPC Planning cube should have 1:1 mapping

Transformation file in BPC Conversion file in BPC



Total 252 records are loaded into BPC Planning cube


Data Records Flow

Z_STAGE Cube

BPC Planning Cube

DM Load with Transformation and Conversation file


Data Records Flow

0FIGL_C10 Cube

Flat File record

Data Flow

Z_STAGE Cube

BPC Planning Cube

Filtered in DTP



Flat File with data 193 data records



Total 193 records are loaded into 0FIGL_C10 cube from Flat file



Total of 84 records ( 84 x 3 =252 )records are loaded into Z_STAGE cube from 0FIGL_C10



Total 252 records are loaded into BPC Planning cube


Examples of Differences Between BPC and SAP NetWeaver BW Data Storage

Modeling SAP NetWeaver BW

BPC Example

Key figure models

Possible Not possible SAP NetWeaver BW splits currency and units into two key figures, while BPC has just one

Financial Logic Modeled in various ways

Handled in ShareQueryEngine

Data Signage is handled using account type in BPC.SAP NetWeaver BW expects the signage in the database

Time Modeled in 13different InfoObjects

Modeled in one Time dimension

SAP NetWeaver BW handles Period 0 and 13-16 out of the box

Currency Handled similar to SAP ERP usingcurrency types

Leverages entitiescurrency and “LC”

LC is a currency type in SAP NetWeaver BW, but a currency in BPC

BPC = SAP BusinessObjects Planning and Consolidation


SAP BusinessObjects Planning and Consolidation Has Only One Key Figure, SAP Has Many

Since SAP BusinessObjects Planning and Consolidation has only one key figure, any SAP ERP record with more than one key figure needs to be converted into a “generic key figure” model with the SAP BusinessObjectsPlanning and Consolidation account dimension being the characteristic that differentiates the different records

0BALANCE 0CREDIT 0DEBIT$66,000.00 $50,790.00 $51,650.00

BPCP_Activity

Amount

BALANCE –F00

$66,000.00

CREDIT –F10

$50,790.00

DEBIT –F20

$51,650.00

BPC = SAP BusinessObjects Planning and Consolidation


SAP BusinessObjects Planning and Consolidation Has Only One Key Figure, SAP Has Many (cont.)

Also, SAP ERP and SAP NetWeaver BW clearly distinguish between a unit of a quantity and the currency of a financial amount or balance

SAP BusinessObjects Planning and Consolidation does not have a designated unit field and thus units and currencies need to be merged into one fieldAlso the local currency in SAP BusinessObjects Planning and Consolidation is stored as “LC.” What currency LC actually stands for is determined via the SAP BusinessObjects Planning and Consolidation entity.

0CURRENCY 0UNITUSD each

RPTCurrencyLCeach

Be aware of the different terminology: Local currency “LC” in SAP BusinessObjects Planning and Consolidation is a currency, while local currency in SAP ERP represents a currency type.


Format Challenges

Transforming SAP NetWeaver BW data into the SAP BusinessObjects Planning and Consolidation one key figure model, as described in the previous section, is usually not enough to ensure an error-free load of SAP NetWeaver BW data into SAP BusinessObjects Planning and Consolidation Several format conversions may be required to allow data to flow into SAP BusinessObjects Planning and Consolidation. We will examine the following:

Data signage conversionDate format conversionDefinition of constant valuesRemoval of leading zeros: ALPHA conversionRemoval of special characters from alphanumeric SAP ERP material numbers

In order to keep an audit trail, any transformed data should be stored in a custom InfoObject along with the original data. So for example, keep 0MATERIAL for the original SAP ERP material number but create a custom object to store the material number in SAP BusinessObjects Planning and Consolidation format.


Data Signage Conversion

SAP NetWeaver BW stores signage as a suffix (e.g.,100-); however, SAP BusinessObjects Planning and Consolidation expects it as a prefix (e.g., -100). This little piece of ABAP code delivers this conversion


Date Format Conversion — Simple

SAP ERP and SAP NetWeaver BW store Fiscal Period date information as YYYYPPP (e.g. 2010001) while SAP BusinessObjects Planning and Consolidation expects YYYY.MMM (e.g. 2010.JAN)

The SAP BusinessObjects Planning and Consolidation conversion file can be used to accomplish this conversion:

If you use Fiscal Period to populate the SAP BusinessObjects Planning and Consolidation time dimension then your conversion is slightly different, as the period is stored as YYYYPPP in SAP NetWeaver BW

BPC Date Amount2010.JAN 100,0002010.MAY 150,000

Calendar Month Amount2010001 100,0002010005 150,000


Additonal details

Thank you


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

© 2010 SAP AG. All Rights Reserved

elite bpc 7.5 nw partner trainingdocshare04.docshare.tips/files/25802/258020409.pdfelite bpc 7.5 nw...

Documents