carga_datos reales (1).pdf

8/20/2019 carga_datos reales (1).pdf

http://slidepdf.com/reader/full/cargadatos-reales-1pdf 1/16

How-to GuideSAP EPM

How To…get Balancesfrom SAP ECC6.0 forConsolidation

in BPC 7.0 NWVersion 1.00 – 27th of April 2009

Applicable Releases:SAP BusinessObjects 7.0 for the NW Platform



©C opy r ig h t 2007 SA P A G. A l l r ig h t s reserv ed.

No par t o f th is pub l icat ion m ay be reprodu ced or

t r ansm i t t ed i n any f o rm o r f o r any pu rpose w i t hou t t heexpr ess perm ission o f SAP AG. T he in form ationconta ined here in m ay be changed w i th out p r io r no t ice.

Som e sof tw are products m arketed by SAP AG and i tsd ist r ibu tor s conta in p ropr ie tary so f tw are com ponents o foth er soft ware vend ors.

M ic rosof t , Window s, Ou t loo k , and PowerPo in t areregistered tradem arks of M icrosoft Cor por at ion.

IBM , D B2, DB2 U n iversal D atabase, OS/2, ParallelSyspl ex, M V S/ESA , A IX , S/390, A S/400, O S/390, O S/400,iSer ies, p Series, x Series, zSeries, z/OS, A FP, In t ell igen tM iner , WebSphere , Net f in i ty , T ivo l i , and In form ix aretr adem ark s or r egistered tr adem arks of IBM Co rpo rat ionin th e U n ited States and/or o th er coun tr ies.

Or acle is a registered tradem ark of Or acle Corp orat ion .

U N IX, X /Open, OSF/1, and M oti f are registeredt r adem ark s o f the Open Grou p.

C i t r ix , ICA , Program Neighborh ood, M etaFrame,Win Fram e, V ideoFrame, and M ul t iW in are t radem ark s

or registered tr adem arks of Cit r ix System s, Inc.

H T M L , XM L , XH T M L and W3C are t r adem arks o rregistered tr adem arks of W 3C ® , Wor ld W ide WebCon sort iu m , M assachu sett s Inst i tu te of Techn olo gy.

Java is a registered t radem ark o f Sun M icro system s, Inc.

JavaScrip t is a registered t radem ark of Sun M icro system s,Inc., used un der l icense for t echn olo gy inven ted andim plem ented by Netscape.

M axD B is a tradem ark of M ySQL A B, Sw eden.

SAP, R/3, m ySA P, m ySA P.com , xApp s, xApp , an d ot herSA P produ cts an d services m ent ion ed herein as w el l asth eir respectiv e lo gos are tr adem ark s or r egisteredtr adem arks of SA P A G in G erm any and in several oth ercoun t r i es al l over t h e w o r l d . A l l o th er p roduc t andservice nam es m entio ned are the tr adem arks of theirrespective companies. Data

conta ined in th is docum ent serves in form at ion alpu rpo ses on ly. Nat ion al prod uct specif icat ion s m ay vary.

T hese m ater ia ls are subj ect t o ch ange w ith ou t n ot ice.T hese m ateri als are prov ided by SA P A G and it s affi l iatedcom panies ( "SAP Grou p" ) fo r in fo rm at iona l pu rposeson l y , w i th out r epresen ta t ion or w ar ranty o f anyk in d , and SAP Grou p sha l l no t be l iable fo r e r ror s orom ission s w ith respect t o th e m ater ia ls. T he onl yw arr an t ies for SA P Gr ou p pr odu cts and services are tho seth at a re se t fo r t h in th e express warranty sta tem entsaccom panyin g such pro du cts and services, i f any.N oth ing h ere in shou ld be const ru ed as const i t u t i ng anadd i t ion al w ar r anty .

T hese m ater ia ls are pro vided “as is” w ith ou t a warr antyo f any k ind , ei th er express or im p l ied , inc lu d ing but no tl im i ted to , th e im p l ied war rant ies o f m erchant ab i l i t y ,f i tn ess for a part icu lar pur pose, or n on -infr ingem ent.SA P shal l no t be l iable for dam ages of any k i nd inclu din gw i thou t l im i ta t ion d i rec t , spec ial , ind i r ec t , o rconsequ ent ia l dam ages th at m ay resu lt f r om th e use ofth ese m aterials.SA P does not w arr ant th e accuracy or com pleteness ofth e in form at ion , tex t , g raph ics, l inks or o th er i tem scon tained wit hin th ese mater ia ls. SA P h as no con tr olover the in form at ion tha t you m ay access th rou gh th euse of h ot l ink s cont ained in t hese m ater ia ls and do es no t

endorse your u se o f th i rd par t y w eb pages nor prov ideany warranty wh atsoever r ela t ing to t h i r d par ty w ebpages.SAP CPM “ How - to” Gu ides are in tended to sim pl i fy th eprodu ct im p lem ent at ion . Wh i le speci f ic p roduct featu resand p rocedur es typ ical ly are explained in a pract icalbusiness cont ext, i t is not im pl ied t hat t hose featu res andpro cedu res are the on ly approach in solv in g a specif icbusin ess pr oblem u sing SAP. Sho ul d you w ish t o r eceiveadd i t ion al in fo rm at ion , c lar i f i cat ion or suppo r t , p leaserefer to SAP Con sul t in g.A ny softw are codin g an d/or code l ines / str ings (“ Cod e”)

inc lu ded in th is docum ent at ion are on ly exam ples andare n ot i nt ended to be used in a produ ct ive systemenv i r onm ent . Th e Code is on ly in tended bet te r exp lainand v isual ize the syntax and ph rasing ru les of certaincodin g. SAP does no t w arrant th e corr ectn ess andcom pleteness of th e Code given h erein, and SAP sh al ln ot be li able for err or s or dam ages caused by th e usage ofth e Code, except if such dam ages w ere cau sed by SA Pintent ional ly or grossly negl igent.



- 1 -

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 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.0

system

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 tableFAGLFLEXT 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 Solution

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



- 2 -

4.1 Act ivation 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, 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 thecumulative (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 record“NONE”, 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 each Account, 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 Process

Create 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 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 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 Flow

The data flow of above two cubes should look like:



- 11 -

4.9 BPC Transformation File

The 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 t ransformation file is veryimportant.

4.10 BPC Conversion Files

The 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 conversion

file.

ENTITY:

C_CATEGORY:



- 13 -

GROUPS:

FLOW:

INTCO:

C_DATASRC:

TIME:



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

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

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

carga_datos reales (1).pdf

Documents

Transcript of carga_datos reales (1).pdf