How-to Guide

SAP EPM

How To…
get Balances
from SAP ECC
6.0 for
Consolidation
in BPC 7.0 NW
Version 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 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, Outlook, and PowerPointare
registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel
Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,
iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent
Miner, WebSphere, Netfinity, Tivoli, and Informix are
trademarks or registered trademarks of IBM Corporation
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.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, 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 in several other
countries all over the world. 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.
These materials are subject to change without notice.
These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes
only, without representation or warranty of any
kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only
warranties for SAP Group products and services are those
that are set forth in the express warranty statements
accompanying such products and services, if any.
Nothing herein should be construed as constituting an
additional warranty.
These materials are provided “as is” 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 not be liable for damages of any kind including
without limitation direct, special, indirect, or
consequential damages that may result from the use of
these materials.
SAP does not warrant the accuracy or completeness of
the information, text, graphics, links or other items
contained within these materials. 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.
SAP CPM “How-to” Guides are intended to simplify the
product implementation. While specific product features
and procedures typically are explained in a practical
business context, it is not implied that those features and
procedures are the only approach in solving a specific
business problem using SAP. Should you wish to receive
additional information, clarification or support, please
refer to SAP Consulting.
Any software coding and/or code lines / strings (“Code”)
included in this documentation are only examples and
are not intended to be used in a productive system
environment. The Code is only intended better explain
and visualize the syntax and phrasing rules of certain
coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall
not be liable for errors or damages caused by the usage of
the Code, except if such damages were caused by SAP
intentionally or grossly negligent.
1 Scenario
This 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. The
document is intended for consultants or administrators that understand the basic
elements need to be set up in the transaction system and SAP BPC 7.0 NW in order to
make consolidation engine work. The intention of this document is not to explain the
financial accounting as defined in various accounting principles and also the
consolidation rules needed to be set-up for getting the consolidated financial statements.
The scenario in this document only covers extraction of YTD balances from the
transaction system for each accounting period.

2 Prerequisites
SAP ECC 6.0 is the transaction system, which is connected with SAP BI 7.0
system
New GL is activated in SAP ECC 6.0 system and different Parallel ledgers are
defined 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 in
each GL Account. This step is optional as the data in BPC can be extracted on
GL Accounts
Set up the Consolidation Transaction Types. These facilitate detailed reporting in
BPC

3 Introduction
Following steps outline how the extraction system should be set up to get the balances
from 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 from
SAP ECC 6.0 system.
Creation of extraction procedure in SAP BI system for getting the data in relevant
Info-cubes.
Creation of Conversion File and Transformation File in SAP BPC 7.0 NW system.

4 Step by Step Solution

The following are the steps in order to set up basic transaction data extraction into SAP
BPC 7.0 NW system:

-1-
4.1 Activation of relevant Data Sources for data extraction in SAP BI 7.0
The 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, which
would 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, which
would be required if there are reporting requirements on SEGMENT in BPC.

Create a Transformation Rule for this Info Source.

-2-
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;

-3-
The following END ROUTINE is included to delete redundant data.

4.3 Create following two Info-Cubes, one for recording the Closing
Balances 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 the
cumulative (YTD) closing balances of only selected accounts, which are relevant
for recording movements data
The structure of both the cubes has to be same.

-4-
4.4 Create Transformation Rules for Cube ZGLBAL_LL

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

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

0COMPANY: This info-object is used to record the trading partner in SAP ECC
6.0 system. At the time of data loading in BPC, none of the values in any of the
characteristics should be blank. Hence the following routine is written to record
“NONE”, wherever the value in 0COMPANY is blank.

-6-
ZGLACCGRP: The routine for this info-object is optional. In order to meet the US
GAAP requirements, the data of specific Functional Areas should be shown
separately. In the following routine, the data of certain accounts is posted on
relevant accounts based on the functional area in transaction data. This routine is
client specific and would be different based on client specific requirements and
SAP ECC 6.0 system configuration.

0CALMONTH: In BPC the TIME Dimension members are required to be created

in calendar month format (YYYY.MMM). In order to record the data of fiscal
periods, calendar month is required to be derived. The following formula is used
to derive the Calendar Month from Fiscal Year/Period.

-7-
0MOVE_TYPE: This info-cube will contain the cumulative balance of each
Account, irrespective of the movements. The constant value “920” is used for this
rule. This value would be mapped with F_CLO member of FLOW Dimension in
SAP BPC 7.0 NW.

-8-
The following Start Routine is included in order to eliminate “ZERO” balances in
transaction data.

4.5 Create Transformation Rules for Cube ZGLMVT_LL

-9-
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 Process

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

4.7 Create Multi-Provider

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

4.8 Data Flow

The data flow of above two cubes should look like:

- 10 -
 ZGLBAL_LL ZGLMVT_LL

4.9 BPC Transformation File

The following transformation file in BPC highlights the mapping of BI Infoobjects with
BPC Dimensions:

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

4.10 BPC Conversion Files

The following conversions in BPC are used for conversion of external master data with
BPC Dimension Members.
The conversion file should be designed in a manner to minimize the maintenance by the
users. The following conversion file is being designed as a Zero maintenance conversion
file.
ENTITY:

C_CATEGORY:

- 12 -
GROUPS:

FLOW:

INTCO:

C_DATASRC:

TIME:

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