How to Run a Top Down Allocation Within BPC NW

How To Run a Top Down Allocation within BPC NWSAP Product Name: SAP Business Planning and Consolidation 7.0, version for SAP NetWeaver Applicable Product Versions: Document Version Last Updated: 7.0 SP2 & above 1.1 Feb 2009

Enterprise Performance Managementwww.sdn.sap.com/irj/sdn/bpx-epm

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/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 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 SAP intentionally or grossly negligent.

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

2 IntroductionThe goal of this how-to guide is to show a top-down allocation. This example will first show how to setup the technical design time of allocations as well as show the front-end user interface for allocations and how it 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 hierarchy a. 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:

The Step By Step SolutionWithin this solution, we will pass parameters for top down allocations from Data Manager thru to Script Logic.

2.1

Setup Pre-requisite data

To show this example, we will start with ApShell, and load some sample data to build a scenario to demonstrate top-down allocations.1. Log in the BPC Admin Console

2. Within the Dimension Library, click on Entity and choose Maintain dimension property

3. Enter a new property called ALLOC_PERCENT with length 5 and click Modify Dimension Property.

4. Click OK.

5. Under the Dimension Library, choose Entity and click Maintain dimension members

6. Paste the dimension members from the attached Entity excel file into this Dimension Member Sheet.

7. Click Save to Server.

8. Click Process dimension

9. Choose Entity and click OK.

10. Click OK.

11. Go to the Dimension Library and choose P_ACCT and click Maintain Dimension Members

12. Paste the dimension members from the attached P_ACCT excel file into this Dimension Member Sheet.

13. Click Save to Server

14. Click Process Dimension and click OK.

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 our allocations scenario. There is a delivered process chain to RUN_ALLOCATIONS. However, if you want to 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.

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

4. Name the process chain ZBPC_RUN_ALLOC2 and call it Run Top Down Allocation Based on History.

5. Double click on the Start variant.

6. Click New

7. Specify the process variant as ZBPC_RUN_ALLOC2_START and call it Start Allocation 2. Click the Green Check.

8. Click the Change Selections button.

9. Click Immediate and click the Save button.

10. Click Save and then click back.

11. Right click on the Start type and choose Exchange Variant.

12. Choose the selector.

13. Double click on ZBPC_RUN_ALLOC2_START.

14. Click the Green Check.

15. Double click on the Run Logic process variant.

16. Ensure the following field names are set and click Save and the Back.

17. Click Activate to activate the process chain.

You dont have to create new process chain for each script file you want to execute. You can pass the script file dynamically either in the data manager dynamic script (explained in section 3.3) of the package 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.

2.3 Develop the required script In 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/Application where you want to create the script Logic. In this case, were working with a copy of ApShell.

3. In the action pane, click Create New Logic.

4. Name the Logic File ALLOCATEHISTORICAL.LGF and click OK.

5. Enter the script logic code here. (Sample code is provided in the appendix). $SOURCE$ and $TARGET$ will be replaced at run time with prompt value. Use $ character before and after name to be 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

1. Login to the BPC Excel client.

2. Click on Manage Data in the Action pane.

3. Click on Maintain data management in the next menu.

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

5. Choose the desired team and click on Create package to add a new package. In this example, were creating it under the Financial Processes folder.

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

7. Choose the process chain which we created in the earlier step.

8. Enter Package name and Description (Avoid using special characters for naming the package. and choose a group as well. Make sure to select the desired task type as well. Then, click Save. In this case, were calling the package Run Historical Allocation

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

10. You will get a message that package list successfully updated.

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

12. Right click on the Run Historical Allocation package and choose Modify Package.

13. Click view package (button next to open folder on the same line as process chain).

14. Click on Advanced button.

15. Here, maintain the dynamic script (sample code is provided in the appendix). Then, click ok. Note: There are two INFO statements here. The parameter EQU is used as the splitter between parameter and value (e.g.in A=B, EQU is just =). The parameter TAB is used to separate whole parameter & value sets (e.g. for A=B;C=D, the TAB is ;). You can see how these two variables are used in the final TASK line of this dynamic script file.

16. Press Save in the next screen.

17. Press save again

18. Press save again. Now, we created the package.

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

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. NOTE: This is the step that most end users who perform allocations will work with. All previous steps would be performed by power users or BPC Administrators.1. Login to the BPC Excel client.

2. Choose Data Input.

3. Choose Build a schedule using a dynamic template

4. Click Entity-Trend and choose Open.

5. Change the current view to the following to plan on data for all of Asia:

6. Enter the following numbers:

7. Click Send data.

8. Click Send active worksheet

9. Click Yes.

10. Click Close.

11. Change Current View to the following:

12. Click Home

13. Click Manage Data

14. Click Run a data management package

15. Choose Run Historical Allocation and click Run.

16. Enter the following parameters and click Next. Here, we are allocating from 50,000 to RASA from all of Asia in 2008.JAN. (See hierarchy above)

17. Choose the following members, and click Next.

18. Click Finish.

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

3 Appendix3.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=