how to run a top down allocation within bpc nw

5/20/2018 How to Run a Top Down Allocation Within BPC NW

1/34

How To

Run a Top DownAllocation within BPCNW

Run a Top DownAllocation within BPCNW

SAP Product Name:SAP Product Name: SAP Business Planning and Consolidation 7.0,

version for SAP NetWeaver

SAP Business Planning and Consolidation 7.0,

version for SAP NetWeaver

Applicable Product Versions:Applicable Product Versions: 7.0 SP2 & above7.0 SP2 & above

Document VersionDocument Version 1.11.1

Last Updated:Last Updated: Feb 2009Feb 2009

Enterprise PerformanceManagement

Enterprise PerformanceManagement

www.sdn.sap.com/irj/sdn/bpx-epmwww.sdn.sap.com/irj/sdn/bpx-epm
http://www.sdn.sap.com/irj/sdn/bpx-epmhttp://www.sdn.sap.com/irj/sdn/bpx-epmhttp://www.sdn.sap.com/irj/sdn/bpx-epm


2/34

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 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 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, and Informix are trademarks or registered

trademarks of IBM Corporation in the United States and/orother 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 MultiWinare 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 theirrespective 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 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 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 includingwithout 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 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 products. 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 SAPintentionally or grossly negligent.


3/34

1 Scenario

In this scenario, we will try to run a top down allocation within BPC NW.

2 Introduction

The goal of this how-to guide is to show a top-down allocation. This example will first show how to setupthe technical design time of allocations as well as show the front-end user interface for allocations and howit is integrated into the end users runtime.

The scenario will show how to allocation Planning Asia data down to China, Japan, India,and Rest of Asia.

We can allocate based on numerous options. In this guide, we will show the following scenario:

Allocate top down planning based on previous years data across hierarchya. We are allocating $50,000 for RENT to 2009.JAN based on Asia All. Were basing the

breakout to the base members based on the historical data for RENT in 2008.JAN.b. Source Data:

c. Target after allocating $50,000:


4/34


5/34

The Step By Step Solution

Within this solution, we will pass parameters for top down allocations from Data Manager thru to ScriptLogic.

2.1 Setup Pre-requisite data

To show this example, we will start with ApShell, and load some sample data to build a scenario todemonstrate top-down allocations.

1. Log in the BPC Admin Console

2. Within the Dimension Library, click

on Entity and choose Maintaindimension property


6/34

3. Enter a new property calledALLOC_PERCENT with length 5and click Modify DimensionProperty.

4. Click OK.

5. Under the Dimension Library, chooseEntity and click Maintaindimension members


7/34

6. Paste the dimension members fromthe attached Entity excel file intothis Dimension Member Sheet.

7. Click Save to Server.


8/34

8. Click Process dimension

9. Choose Entity and click OK.


9/34

10.Click OK.

11.Go to the Dimension Library andchoose P_ACCT and click

Maintain Dimension Members

12.Paste the dimension members fromthe attached P_ACCT excel file

into this Dimension Member Sheet.


10/34

13.Click Save to Server

14.Click Process Dimension and clickOK.


11/34

15.Click OK.

2.2 Create Process Chain

After we have the sample dimension members loaded, well want to configure a process chain to use for ourallocations scenario. There is a delivered process chain to RUN_ALLOCATIONS. However, if you wantto customize the user interface, you can build a process chain for your scenario. In this example, we will

build a process chain for our custom scenario.

1. Go to transaction RSPC

2. Double click on the BPC:

Allocation process chain.


12/34

3. In the menu, choose Process chain-> Copy

4. Name the process chainZBPC_RUN_ALLOC2 and call itRun Top Down Allocation Based on

History.

5. Double click on the Start variant.


13/34

6. Click New

7. Specify the process variant asZBPC_RUN_ALLOC2_START andcall it Start Allocation 2. Click the

Green Check.

8. Click the Change Selectionsbutton.


14/34

9. Click Immediate and click theSave button.

10.Click Save and then click back.

11.Right click on the Start type andchoose Exchange Variant.


15/34

12.Choose the selector.

13.Double click onZBPC_RUN_ALLOC2_START.

14.Click the Green Check.


16/34

15.Double click on the Run Logicprocess variant.

16.Ensure the following field names areset and click Save and the Back.

17.Click Activate to activate the processchain.

You dont have to create new process chain for each script file you want to execute. You can passthe script file dynamically either in the data manager dynamic script (explained in section 3.3) of thepackage or prompt the user for the script file (explained in Appendix section).

Please note that currently you can create only one Data Manager package per process chain.


17/34

2.3 Develop the required scriptIn this step, we will develop the script with parameters which will replaced by data manager prompts.

1. Login to the BPC Administration.

2. Navigate to the AppSet/Applicationwhere you want to create the scriptLogic.

In this case, were working with a

copy of ApShell.

3. In the action pane, click Create NewLogic.


18/34

4. Name the Logic FileALLOCATEHISTORICAL.LGF andclick OK.

5. Enter the script logic code here.(Sample code is provided in theappendix). $SOURCE$ and

$TARGET$ will be replaced at runtime with prompt value. Use $character before and after name tobe replaced.

6. Save the script logic.

2.4 Build the Data Manager Package

In this step, we will build the data manager package for running our allocation


19/34

1. Login to the BPC Excel client.

2. Click on Manage Data in the Actionpane.


20/34

3. Click on Maintain datamanagement in the next menu.

4. Then, click on Manage packages(organize list).


21/34

5. Choose the desired team and clickon Create package to add a newpackage.

In this example, were creating itunder the Financial Processesfolder.

6. Click on open folder button to selecta process chain for this package

7. Choose the process chain which wecreated in the earlier step.


22/34

8. Enter Package name andDescription (Avoid using specialcharacters for naming the package.and choose a group as well. Makesure to select the desired task typeas well. Then, click Save.

In this case, were calling thepackage Run Historical Allocation

9. Next screen, click save to store thepackage in the system.

10.You will get a message that packagelist successfully updated.


23/34

11.Go back to Manage packages(organize list) to modify thepackage

12.Right click on the Run HistoricalAllocation package and chooseModify Package.

13.Click view package (button next toopen folder on the same line asprocess chain).


24/34

14.Click on Advanced button.

15.Here, maintain the dynamic script

(sample code is provided in theappendix). Then, click ok.

Note: There are two INFO statementshere. The parameter EQU is used asthe splitter between parameter andvalue (e.g.in A=B, EQU is just =). Theparameter TAB is used to separatewhole parameter & value sets (e.g. forA=B;C=D, the TAB is ;). You can seehow these two variables are used in thefinal TASK line of this dynamic script

file.

16.Press Save in the next screen.


25/34

17.Press save again

18.Press save again. Now, we createdthe package.

19.You will get a message that saysPackage list successfully updated.Click OK.


26/34

2.5 Scenario 1 - Enter Data and Allocate based on historical data

In this step, we will enter data for the RENT account and all entities under Asia within 2008.JAN.Then well run an allocation to allocate a number across the Asia entities based on historical

percentages within 2008.JAN.

NOT

This is the step that most end users who perform allocations will work with. All previoussteps would be performed by power users or BPC Administrators.

1. Login to the BPC Excel client.

2. Choose Data Input.


27/34

3. Choose Build a schedule using adynamic template

4. Click Entity-Trend and chooseOpen.


28/34

5. Change the current view to thefollowing to plan on data for all ofAsia:

6. Enter the following numbers:

7. Click Send data.


29/34

8. Click Send active worksheet

9. Click Yes.

10.Click Close.


30/34

11.Change Current View to thefollowing:

12.Click Home

13.Click Manage Data


31/34

14.Click Run a data managementpackage

15.Choose Run Historical Allocationand click Run.

16.Enter the following parameters andclick Next.

Here, we are allocating from 50,000to RASA from all of Asia in2008.JAN.

(See hierarchy above)


32/34

17.Choose the following members, andclick Next.

18.Click Finish.

19.Refresh your report, and you will seeyour allocated data.


33/34

3 Appendix

3.1 Scenario 1 - Sample Source Code for Script Logic file:

*XDIM_MEMBERSET TIME=2008.JAN,2009.JAN*XDIM_MEMBERSET P_ACCT=RENT*XDIM_MEMBERSET CATEGORY=PLAN,ACTUAL*XDIM_MEMBERSET ENTITY=$SOURCE$,$TARGET$

*WHEN ENTITY*IS "ASA"

*REC (EXPRESSION=$ASARENT$,TIME=2009.JAN,CATEGORY=PLAN)

*ENDWHEN*COMMIT

*RUNALLOCATION*FACTOR=USING/TOTAL*DIM P_ACCT WHAT=RENT; WHERE=


34/34

how to run a top down allocation within bpc nw

Documents