This action might not be possible to undo. Are you sure you want to continue?
SAP 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 Management
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.
In this scenario, we will try to run a top down allocation within BPC NW.
The 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. We’re 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:
we will start with ApShell. click on “Entity” and choose “Maintain dimension property” . we will pass parameters for top down allocations from Data Manager thru to Script Logic. and load some sample data to build a scenario to demonstrate top-down allocations. Within the Dimension Library.1 Setup Pre-requisite data To show this example. Log in the BPC Admin Console 2. 1.The Step By Step Solution Within this solution. 2.
Click OK. Enter a new property called “ALLOC_PERCENT” with length 5 and click “Modify Dimension Property”. 5.3. Under the Dimension Library. choose “Entity” and click “Maintain dimension members” . 4.
. Click “Save to Server”. Paste the dimension members from the attached “Entity” excel file into this Dimension Member Sheet.6. 7.
Click “Process dimension” 9. Choose “Entity” and click OK.8. .
Click OK.10. 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. .
However.15.2 Create Process Chain After we have the sample dimension members loaded. if you want to customize the user interface. Double click on the “BPC: Allocation” process chain. There is a delivered process chain to “RUN_ALLOCATIONS”. 2. Go to transaction RSPC 2. we will build a process chain for our custom scenario. In this example. 1. you can build a process chain for your scenario. . we’ll want to configure a process chain to use for our allocations scenario. Click OK.
5. Double click on the “Start” variant.3. In the menu. Name the process chain “ZBPC_RUN_ALLOC2” and call it “Run Top Down Allocation Based on History”. choose “Process chain” -> “Copy” 4. .
Click the Green Check. Specify the process variant as “ZBPC_RUN_ALLOC2_START” and call it “Start Allocation 2”. Click the “Change Selections” button. .6. 8. Click “New” 7.
Click “Immediate” and click the “Save” button. . Click Save and then click back. Right click on the “Start” type and choose “Exchange Variant”. 11.9. 10.
. Choose the selector. Click the Green Check. 14.12. Double click on “ZBPC_RUN_ALLOC2_START”. 13.
3) of the package or prompt the user for the script file (explained in Appendix section). . 16. Double click on the “Run Logic” process variant. 17. You can pass the script file dynamically either in the data manager dynamic script (explained in section 3. You don’t have to create new process chain for each script file you want to execute. Please note that currently you can create only one Data Manager package per process chain.15. Click Activate to activate the process chain. Ensure the following field names are set and click Save and the Back.
Navigate to the AppSet/Application where you want to create the script Logic.2. 1. we’re working with a copy of ApShell. we will develop the script with parameters which will replaced by data manager prompts. 2. In the action pane. . Login to the BPC Administration.3 Develop the required script In this step. click “Create New Logic”. 3. In this case.
Use $ character before and after name to be replaced. $SOURCE$ and $TARGET$ will be replaced at run time with prompt value. Enter the script logic code here.4.4 Build the Data Manager Package In this step.LGF” and click OK. (Sample code is provided in the appendix). Name the Logic File “ALLOCATEHISTORICAL. 2. we will build the data manager package for running our allocation . 5. 6. Save the script logic.
2. Click on “Manage Data” in the Action pane. . Login to the BPC Excel client.1.
. Then. click on “Manage packages (organize list)”.3. Click on “Maintain data management” in the next menu. 4.
In this example. we’re creating it under the “Financial Processes” folder.5. 6. Click on open folder button to select a process chain for this package 7. . Choose the desired team and click on “Create package” to add a new package. Choose the process chain which we created in the earlier step.
click Save. Enter Package name and Description (Avoid using special characters for naming the package. and choose a group as well. You will get a message that package list successfully updated. Make sure to select the desired task type as well. Next screen. click save to store the package in the system. Then. . 10. In this case.8. we’re calling the package “Run Historical Allocation” 9.
11. . Go back to “Manage packages (organize list)” to modify the package 12. Click “view package” (button next to open folder on the same line as process chain). Right click on the “Run Historical Allocation” package and choose “Modify Package”. 13.
The parameter “TAB” is used to separate whole parameter & value sets (e. Then. Press Save in the next screen. You can see how these two variables are used in the final TASK line of this dynamic script file. the TAB is “.14. . The parameter “EQU” is used as the splitter between parameter and value (e. 16.g. EQU is just “=”). Note: There are two INFO statements here. Here.in A=B. click ok.”).C=D. maintain the dynamic script (sample code is provided in the appendix).g. Click on “Advanced” button. for A=B. 15.
You will get a message that says “Package list successfully updated”. Now. we created the package. Press save again. 19. Press save again 18.17. Click OK. .
Login to the BPC Excel client. we will enter data for the “RENT” account and all entities under “Asia” within 2008. Then we’ll run an allocation to allocate a number across the “Asia” entities based on historical percentages within 2008. Choose “Data Input”.JAN. NOTE: This is the step that most end users who perform allocations will work with.5 Scenario 1 . 1.Enter Data and Allocate based on historical data In this step. All previous steps would be performed by power users or BPC Administrators. 2.2. .JAN.
Choose “Build a schedule using a dynamic template” 4. .3. Click “Entity-Trend” and choose Open.
Change the current view to the following to plan on data for all of “Asia”: 6. .5. Enter the following numbers: 7. Click “Send data”.
8. Click Yes. Click “Close”. . Click “Send active worksheet” 9. 10.
Click “Home” 13. Click “Manage Data” .11. Change Current View to the following: 12.
16. Choose “Run Historical Allocation” and click “Run”.000 to RASA from all of Asia in 2008. (See hierarchy above) . Click “Run a data management package” 15. Enter the following parameters and click Next.JAN.14. Here. we are allocating from 50.
. 19. and you will see your allocated data. Choose the following members. Click “Finish”.17. 18. and click Next. Refresh your report.
%CURRENCY_DIM%. . TOTAL=<<< *ENDALLOCATION *WHEN ENTITY *IS "ASA" *REC (EXPRESSION=0.Sample Source Code for dynamic script in the package: PROMPT(SELECTINPUT.LGF) TASK(/CPMB/ALLOCATION_LOGIC. WHERE=BAS($TARGET$).JAN.=) INFO(%TAB%. TOTAL=<<< *DIM TIME WHAT=>>>.%TARGET%.) PROMPT(TEXT.%USER%) TASK(/CPMB/ALLOCATION_LOGIC."%CATEGORY_DIM%. TOTAL=<<< *DIM ENTITY WHAT=$SOURCE$."Enter Target Entities".) TASK(/CPMB/ALLOCATION_LOGIC.$TARGET$ *WHEN ENTITY *IS "ASA" *REC (EXPRESSION=$ASARENT$.JAN *XDIM_MEMBERSET P_ACCT=RENT *XDIM_MEMBERSET CATEGORY=PLAN.JAN. WHERE=2009."How much do you want to allocate?". USING=<<<.%ASARENT%.3 Appendix 3.) INFO(%EQU%.TIME=2009.ASARENT%EQU%%ASARENT%%TAB%SOURCE%EQU%%SOURCE%%TAB %TARGET%EQU%%TARGET%) REPLACEPARAM in the last TASK basically builds a look up table with variable name & its value entered by the users. WHERE=<<<. WHERE=PLAN.SUSER."Enter Source Entity".2 Scenario 2 ..SAPP.%EQU%) TASK(/CPMB/ALLOCATION_LOGIC.SAPPSET.REPLACEPARAM.JAN..CATEGORY=PLAN) *ENDWHEN Note the $ sign at the beginning and end of the variables.%TIME_DIM%") PROMPT(TEXT.JAN.) PROMPT(TEXT. 3.1 Scenario 1 . USING=2008..JAN.%SELECTION%) TASK(/CPMB/ALLOCATION_LOGIC.LOGICFILENAME.2009.SELECTION. before execution of the script.CATEGORY=PLAN) *ENDWHEN *COMMIT *RUNALLOCATION *FACTOR=USING/TOTAL *DIM P_ACCT WHAT=RENT. USING=ACTUAL.TIME=2009.TAB.ACTUAL *XDIM_MEMBERSET ENTITY=$SOURCE$. wherever the variables appear in the script.%APPSET%) TASK(/CPMB/ALLOCATION_LOGIC. USING=<<<.%TAB%) TASK(/CPMB/ALLOCATION_LOGIC.ALLOCATEHISTORICAL..Sample Source Code for Script Logic file: *XDIM_MEMBERSET TIME=2008. During execution of the script logic.%SOURCE%. TOTAL=<<< *DIM CATEGORY WHAT=>>>. they will first replaced by the user entered value.EQU.%APP%) TASK(/CPMB/ALLOCATION_LOGIC.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.