sap bpc consolidation(copy opening)

SAP BusinessObjects

EPM RIG

How To Use COPYOPENING usingSAP BusinessObjects Planning andConsolidation for the SAPNetWeaver Platform

Applicable Releases:

SAP BusinessObjects Planning and Consolidation 7.0 for the SAPNetWeaver platform

Version 1.0

SAP BusinessObjects

EPM RIGAugust 2009

© Copyright 2009 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 containedherein 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 PowerPoint are

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, Informix,

i5/OS, POWER, POWER5, OpenPower and PowerPC are

trademarks or registered trademarks of IBM Corporation.

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 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, SAP

NetWeaver, and other SAP products and servicesmentioned 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 thetrademarks 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 SAPGroup 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 suchproducts 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 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 including

without limitation direct, special, indirect, or consequentialdamages 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 theinformation 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 NetWeaver “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 thosefeatures and procedures are the only approach in solving a

specific business problem using SAP NetWeaver. 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 andvisualize 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, exceptif such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Anycode change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is onlyto be used by SAP’s Support Services and may not be

modified or altered in any way.

Document HistoryDocument Version Description

1.10 << Enter your summary of changes in this version >>

1.00 First official release of this guide

Typographic ConventionsType Style Description

Example Text Words or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.

Cross-references to otherdocumentation

Example text Emphasized words orphrases in body text, graphictitles, and table titles

Example text File and directory names andtheir paths, messages,names of variables andparameters, source text, andnames of installation,upgrade and database tools.

Example text User entry texts. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampletext>

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

IconsIcon Description

Caution

Note or Important

Example

Recommendation or Tip

Table of Contents

1. Business Scenario ..........................................................................................................1

2. Background Information .................................................................................................1

3. Prerequisites....................................................................................................................2

4. Step-by-Step Procedure ..................................................................................................3

4.1 Create/Modify the Application....................................................................................3

4.2 Required Dimension properties .................................................................................4

4.3 Business Rules .........................................................................................................6

4.4 Script Logic ...............................................................................................................7

4.5 Data Package ...........................................................................................................7

4.6 Validating the rules ...................................................................................................8

4.7 Executing the COPY opening task ............................................................................9

The COPYOPENING script with SAP BusinessObjects Planning and Consolidation(BPC) 7.0 for theSAP NetWeaver platform.

August 2009 1

1. Business ScenarioThis document describes how to set up Balance Carry Forward using the COPYOPENING script withSAP BusinessObjects Planning and Consolidation (BPC) 7.0 for the SAP NetWeaver platform.

An ApShell (starting and example AppSet provided) in BPC7 NW initial release would not contain anyconsolidation application, the strategy is to keep ApShell straight and reflect the baseline requirementfor customer to start new implementation and ensure there is nothing that will have to be re-engineered that is related to the customer’s master/meta data, on the other hand, need minimize the“taken off” work on ApShell at customers. In this case, the document is intended for consultants oradministrators that understand the basic elements need to be set up in the Application in order tomake consolidation engine work. It also tries to provide fairly detailed procedures to set up all theelements composing the consolidation module as a referenced document to the manual. But we donot try to explain here how the consolidation rules that can be defined with BPC consolidation engineand especially leaving the accounting principles such as IFRS, USGAAP building likely to the expertsin COE team probably with the coming BPC Start Kits.

This “How to Guide” will focus on what the dimension properties and the relevant setting required forcreating the Balance Carry Forward (CopyOpening) using the Business Rules tables and script logicusing the “BPC Admin”. This will also show how to setup the data package to run the task using the“BPC Excel.”. Business Rules provide the mathematical foundation for the BPC application, andallows the clients to manage both management and legal consolidation reporting.

2. Background InformationAutomatically create the required opening balances when opening a new year for processing. Whenopening a new year for processing, it is generally necessary to be able to initialize the Balance SheetAccounts for the new reporting period (year) with the YTD closing balances of the last period of theprevious year.

Effectively the closing balances for year x-1 need to become the opening balances of the current year.

Normally the balance carry forward functionality is required to the closing balance for Balance Sheetaccounts of one fiscal year into the opening balance of the subsequent fiscal years periods is required.

This guide provides all the properties and configuration settings required to provide the functionalitywhich can automatically create the required opening balances in a new fiscal year.

This procedure can be used to initialize a new reporting period with the closing balances of the lastperiod from the previous year into the opening balances of the current period. It can also copy closingbalances from a designated year and period to current period. The designated year and period can beabsolute or relative number. Sum up the balances of YTD to current period. Copy the same periodbalances to current period.

In a legal consolidation application, such balances are usually identified as members of theFLOW dimension. In simpler applications, however, it is also possible to store them as additionalaccounts in the ACCOUNT dimension.


August 2009 2

3. Prerequisites Successful installation of BPC 7.0 version for SAP NetWeaver.

Completion of Apshell activation.

Create the consolidation environment as per the How To setup consolidation environment usingBPC 7 version for SAP NetWeaver.

Understanding Business Rules for BPC.

Provide information about:

Relevant SAP Notes

How to setup consolidation environment using BPC 7 version for SAP NetWeaver.


August 2009 3

4. Step-by-Step ProcedureThe Carry - Forward Business Rule gives you the ability to generate the Opening Balance of anycategory. This procedure is often used to initialize a new reporting period, copying the closingbalances from the last period of the previous year, and loading them into the opening balances of thecurrent period of the current year.

The Carry – Forward Rule is handled by the stored procedure called COPYOPENING.

The steps to setting up the requirements necessary to have this Business Rule complete successfully.The example will demonstrate the proper setup that is required to bring the year end balances of theBalance Sheet items to the opening balance in the New Year.

4.1 Create/Modify the Application...

For a base line legal consolidation environment, Consolidation, Rate and Ownership applications aremust-to-have applications, the consolidation engine will look into these applications to retrieve some ofthe necessary information.

To create the Consolidation application first, create a RATE application and the OWNERSHIPapplication as listed in the “How To setup consolidation environment using BPC 7 version for SAPNetWeaver”.

Note that you can also use this in the Financial application in which case you need to just create theRate application.

Here is the screenshot of the business rule activation during the creation of the Consolidation typeapplication.

Here is the screenshot from the financial type application


August 2009 4

This can also be validated the web admin parameters where the following parameter is set to “1”to indicate that the Carry forward business rule is activated.

4.2 Required Dimension properties...

1. TIME Dimension – Property – MONTHNUM

The system uses this property to determine the “Last Period” of prior fiscal year. This propertybasically helps to facilitate the automated functionality to carry forward the closing balances of specificaccounts (i.e. Balance Sheet) accounts from the “Last” period of one fiscal year into the openingbalance of the periods of the subsequent fiscal year.

2. DATASRC Dimension - Property – DATASRC_TYPE

The system uses this property to determine whether the data is “Input” balances and their related“Manual” adjustments. The value of “I” and “M” in the DATASRC_TYPE property means that thesystem will only copy the “Input” balances and their related “Manual” adjustments.

Note: The carry forward procedure should however be limited to the copy of the opening balances forinput and Manual Adjustment data only. Balances which are generated “automatically” (DATASRCmembers flagged as “A”) by the consolidation process will be taken care of during the actualconsolidation process itself.

3. DATASRC Dimension - Property – OPENINGDATASRC


August 2009 5

This property is used to define a different destination data source to which the corresponding amountsshould be carried forward. The rule should be attached directly to the Data source. Where this mightapply is where for example certain entries are posted to a datasource which specifically identifiesthese adjustments as for example audit adjustments in the current year but in future years we maywish to simply include in another standard data source (i.e. input).

4. DATASRC Dimension - Property – COPYOPENINGThis property when set to no, the system will then exclude any data under this specific datasourcefrom the carry-forward process.

5. CATEGORY Dimension - Property – CATEGORY_FOR_OPEThis property is used when you want to define a source category from which the balances should becarried forward. For example if you want to create the opening balances for the current year plan(category P) from the closing actual (category A) balance of the prior year.

6. CATEGORY Dimension - Property – OPENING_PERIODThis property is used when you want to the option to override the standard logic which specifies thatthe last period of the prior year should always represent the balance to be rolled forward into theopening balances of the New Fiscal Year. This may not be used that frequently as this may be a rarecase scenario especially when there may be situations where one chooses to pick a particular periodfor roll-forward which is not the last period of the prior year. The “override” period year can be definedas either fixed values or relative values.

7. CATEGORY Dimension - Property – OPENING_YEARThis property is used when you want to the option to override the standard logic which specifies thatthe last period of the prior year should always represent the balance to be rolled forward into theopening balances of the New Fiscal Year. This may not be used that frequently as this may be a rarecase scenario especially when there may be situations where one chooses to pick a particular year forroll-forward which is not the last period of the prior year. The “override” year can be defined as eitherfixed values or relative values.

8. FLOW Dimension - Property – FLOW TYPEThis property is used to define the type of flow of the dimension. The FLOW_TYPE property can takemany values, but the most important is the value CLOSING. The rule of currency translationwith FORCE_CLOSING = Y will make use of it.


August 2009 6

This dimension is needed for business rules calculations to breakdown account activity or flow. Forexample, some accounts, like Fixed Assets, have a FLOW dimension which contains OpeningBalances, Additions, Deletions, Transfers and Ending Balances.

4.3 Business Rules...

1. In the Admin Console, select the “Legal” application, then “Business Rules” and select the“Carry-forward rules” table.

2. Fill in that table according to the following table (delete the existing content first):

Here are the details of each column in the Carry forward business rule.

Source account - this controls the rule to apply to a given account. This field is driven by a drop-down menu choice and may contain either of the following:i) A valid base or parent level member ID from the Account type dimension. Orii) A list of members defined filtering the members using a value of the DIMLIST property (or anyproperty whose name begins with DIMLIST) in this same Account type dimension.

Source flow – This controls the applicability of the rule from a given member ID of the Flowdimension. This field is driven by a dropdown menu choice and may contain either of the following:1) A valid base or parent level member ID from the Subtable type dimension. Or2) A list of members defined filtering the members using a value of the DIMLIST property (or anyproperty whose name begins with DIMLIST) in this same Subtable type dimension.

Destination account -This is the new Account that the rule is copying the data to. This field isdriven by a drop-down menu choice containing all base level members of the Account typedimension.

Destination flow - This field controls the destination member ID of the Flow dimension. This field isdriven by a drop-down menu choice containing all base level members of the Subtable typedimension.

3. Click “Save without validation” and then click “Validate Carry-forward rules table”


August 2009 7

4.4 Script Logic

1. In the Admin Console, select the “Legal” application, then “Script Logic” and select the “CreateNew Logic”.

2. Create the CopyOpening script “COPYOPENING.LGF” as shown below.

3. Add the following code to the LGF file and click on “Validate and Save”.

*RUN_PROGRAM COPYOPENINGCATEGORY = %CATEGORY_SET%CURRENCY = %GROUPS_SET%TID_RA = %TIME_SET%OTHER = [ENTITY=%ENTITY_SET%]

*ENDRUN_PROGRAM

4.5 Data Package

1. Login BPC for excel to create the data package.

2. Add the Copy Opening data package under Financial Processes as shown below.


August 2009 8

4.6 Validating the rules

1. Create a report to validate and use the Groups and Flow in the column and Account in therow. Here is an example to validate the data loaded for DEC 2007.

.2. Click on “Expand all” icon and check the result is transferred to Retained Earning (according

to the rules in the Carry-forward Business Rules table)


August 2009 9

3. Here is the report that shows the data that is available in 2007.Dec.

4. Here is the report that shows the data that is available in 2008.Jan. please note that there isno data as the balance carry forward task has not been executed.

4.7 Executing the COPY opening task

1. Click on the “Home” button in the Action Pane, then on “Data Manager” and finally click on“Run a data management package”. Select the “Copy Opening” package in “FinancialProcesses” and set the following parameters:a. C_Category : C_100b. Entity : <all>c. Time : 2007.DECd. Groups : LC


August 2009 10


August 2009 11

2. Click on “View Status” to check whether the package completed successfully and click onView details.

:

3. The details of the task can be viewed here.


August 2009 12

4. Refresh the report created in for 2008.JAN and you can see the data showing up under theopening flow i.e. F_100.

www.sdn.sap.com/irj/sdn/howtoguides

http://www.sdn.sap.com/irj/sdn/howtoguides

sap bpc consolidation(copy opening)

Documents