How-to GuideSAP EPM

How Toget Balancesfrom SAP ECC6.0 forConsolidationin BPC 7.0 NWVersion 1.00 27th of April 2009

Applicable Releases:SAP BusinessObjects 7.0 for the NW Platform

Copyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The informationcontained herein may be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook, and PowerPointareregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,iSeries, pSeries, xSeries, zSeries, z/OS, AFP, IntelligentMiner, WebSphere, Netfinity, Tivoli, and Informix aretrademarks or registered trademarks of IBM Corporationin the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registeredtrademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,WinFrame, VideoFrame, and MultiWin are trademarksor registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks orregistered trademarks of W3C, World Wide WebConsortium, 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 andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and otherSAP products and services mentioned herein as well astheir respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several othercountries all over the world. All other product andservice names mentioned are the trademarks of theirrespective companies. Data

contained in this document serves informationalpurposes only. National product specifications may vary.

These materials are subject to change without notice.These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposesonly, without representation or warranty of anykind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The onlywarranties for SAP Group products and services are thosethat are set forth in the express warranty statementsaccompanying such products and services, if any.Nothing herein should be construed as constituting anadditional warranty.

These materials are provided as is without a warrantyof any kind, either express or implied, including but notlimited to, the implied warranties of merchantability,fitness for a particular purpose, or non-infringement.SAP shall not be liable for damages of any kind includingwithout limitation direct, special, indirect, orconsequential damages that may result from the use ofthese materials.SAP does not warrant the accuracy or completeness ofthe information, text, graphics, links or other itemscontained within these materials. SAP has no controlover the information that you may access through theuse of hot links contained in these materials and does notendorse your use of third party web pages nor provideany warranty whatsoever relating to third party webpages.SAP CPM How-to Guides are intended to simplify theproduct implementation. While specific product featuresand procedures typically are explained in a practicalbusiness context, it is not implied that those features andprocedures are the only approach in solving a specificbusiness problem using SAP. Should you wish to receiveadditional information, clarification or support, pleaserefer to SAP Consulting.Any software coding and/or code lines / strings (Code)included in this documentation are only examples andare not intended to be used in a productive systemenvironment. The Code is only intended better explainand visualize the syntax and phrasing rules of certaincoding. SAP does not warrant the correctness andcompleteness of the Code given herein, and SAP shallnot be liable for errors or damages caused by the usage ofthe Code, except if such damages were caused by SAPintentionally or grossly negligent.

- 1 -

1 ScenarioThis document describes how to set up extraction of balances from SAP ECC 6.0 system(transaction system) for the purpose of consolidation in SAP BPC 7.0 NW system. Thedocument is intended for consultants or administrators that understand the basicelements need to be set up in the transaction system and SAP BPC 7.0 NW in order tomake consolidation engine work. The intention of this document is not to explain thefinancial accounting as defined in various accounting principles and also theconsolidation rules needed to be set-up for getting the consolidated financial statements.

The scenario in this document only covers extraction of YTD balances from thetransaction system for each accounting period.

2 Prerequisites

? SAP ECC 6.0 is the transaction system, which is connected with SAP BI 7.0system

? New GL is activated in SAP ECC 6.0 system and different Parallel ledgers aredefined for recording various GAAP specific accounting adjustments, such US-GAAP, India GAAP, IFRS, etc

? Set up the Consolidation Chart of Account and assign the Group Accounts ineach GL Account. This step is optional as the data in BPC can be extracted onGL Accounts

? Set up the Consolidation Transaction Types. These facilitate detailed reporting inBPC

3 IntroductionFollowing steps outline how the extraction system should be set up to get the balancesfrom transaction system for consolidation in BPC 7.0 NW system.

? Creation of Consolidation AppSet, Application and setting various parameters.? Master Data set up for various Dimensions in BPC.? Activation of standard data sources to extract the balances from SAP table

FAGLFLEXT in SAP ECC 6.0 system.

? Creation of Info-Cubes in SAP BI system for getting the transaction data fromSAP ECC 6.0 system.

? Creation of extraction procedure in SAP BI system for getting the data in relevantInfo-cubes.

? Creation of Conversion File and Transformation File in SAP BPC 7.0 NW system.

4 Step by Step SolutionThe following are the steps in order to set up basic transaction data extraction into SAPBPC 7.0 NW system:

- 2 -

4.1 Activation of relevant Data Sources for data extraction in SAP BI 7.0The following standard data sources are used for getting the data:

? 0FI_GL_12 Data from Leading Ledger? 3FI_GL_XX_TT Data from Non-Leading Ledgers

These data source extraction process should be set to ADDD Additive Delta, whichwould facilitate extraction of data directly in an Info-cube. Refer SAP Note 1153944,which explains the process of setting up the data source extraction process to ADDD Additive Delta.

4.2 Create an Info-Source, such as ZFI_GL_12. Follow the following steps:Create an Info-Source and select the following fields. SEGMENT is an option field, whichwould be required if there are reporting requirements on SEGMENT in BPC.

Create a Transformation Rule for this Info Source.

- 3 -

In the above scenario, ZGLACCGRP is defined as an info-object in SAP BI system.

This info-object is included as an attribute of 0GL_ACCOUNT. The following master

data mapping is done for ZGLACCGRP in the transformation rule;

- 4 -

The following END ROUTINE is included to delete redundant data.

4.3 Create following two Info-Cubes, one for recording the ClosingBalances of all accounts and the other for recording the Movements(Flows) balances.? ZGLBAL_LL GL YTD Balances US GAAP: This info-cube will record the

cumulative (YTD) closing balance of all Accounts.

? ZGLMVT_LL GL YTD Movements US GAAP: This info-cube will record thecumulative (YTD) closing balances of only selected accounts, which are relevantfor recording movements data

The structure of both the cubes has to be same.

- 5 -

4.4 Create Transformation Rules for Cube ZGLBAL_LL

- 6 -

Following routines / formula are written for some info-objects:

? 0FISCPER: The SAP table FAGLFLEXT stores balances up to Period 016, hencethe data recorded up to period 016 in SAP ECC 6.0, should be taken for thepurpose of consolidation. In BPC we can only have 12 periods. In order to recordthe period 016 balances in period 012, the following routine is incorporated.

? 0COMPANY: This info-object is used to record the trading partner in SAP ECC6.0 system. At the time of data loading in BPC, none of the values in any of thecharacteristics should be blank. Hence the following routine is written to recordNONE, wherever the value in 0COMPANY is blank.

- 7 -

? ZGLACCGRP: The routine for this info-object is optional. In order to meet the USGAAP requirements, the data of specific Functional Areas should be shownseparately. In the following routine, the data of certain accounts is posted onrelevant accounts based on the functional area in transaction data. This routine isclient specific and would be different based on client specific requirements andSAP ECC 6.0 system configuration.

? 0CALMONTH: In BPC the TIME Dimension members are required to be createdin calendar month format (YYYY.MMM). In order to record the data of fiscalperiods, calendar month is required to be derived. The following formula is usedto derive the Calendar Month from Fiscal Year/Period.

- 8 -

? 0MOVE_TYPE: This info-cube will contain the cumulative balance of eachAccount, irrespective of the movements. The constant value 920 is used for thisrule. This value would be mapped with F_CLO member of FLOW Dimension inSAP BPC 7.0 NW.

- 9 -

The following Start Routine is included in order to eliminate ZERO balances in

transaction data.

4.5 Create Transformation Rules for Cube ZGLMVT_LL

- 10 -

All the rules in transformation rule of ZGLBAL_LL info-cube are similar for this cube also.The only difference is to directly map the info-object 0MOVE_TYPE with source field.

4.6 Create Data Transfer ProcessCreate the Data Transfer Process (DTP) for both the info-cubes. You can set the filter inDTP as per the requirement. The filter in DTP for info-cube ZGLMVT_LL should be set toonly include Accounts relevant for movement types. This is required to ensure that onlythe relevant movements are available in BPC.

4.7 Create Multi-ProviderCreate a Multi-Provider for these two info-cubes. This multi-provider is used in the datamanager package of BPC for loading the data. Since only one infoprovider can beselected in BPC data manager package, creation of multi-provider would facilitateloading of data in one single step.

4.8 Data FlowThe data flow of above two cubes should look like:

- 11 -

4.9 BPC Transformation FileThe following transformation file in BPC highlights the mapping of BI Infoobjects withBPC Dimensions:

ZGLMVT_LLZGLBAL_LL

- 12 -

The SELECTION option is very important in the transformation file. As per the BPCsystem design the whole data in info-provider is loaded every time a data load isdone through data manager package. In order to avoid overwriting theconsolidated data in BPC, the period selection in transformation file is veryimportant.

4.10 BPC Conversion FilesThe following conversions in BPC are used for conversion of external master data withBPC Dimension Members.

The conversion file should be designed in a manner to minimize the maintenance by theusers. The following conversion file is being designed as a Zero maintenance conversionfile.

? ENTITY:

? C_CATEGORY:

- 13 -

? GROUPS:

? FLOW:

? INTCO:

? C_DATASRC:

? TIME:

www.sdn.sap.com/irj/bpx/epm