How to... Configure Drill Through BPC

SAP BOBJ Planning & Consolidation (BPC), version for Netweaver How-To Guide

How To... Configure Drill Through Functionality

Applicable Releases:

SAP BusinessObjects Planning and Consolidation 7.5 , version for NetWeaver, SP00 and higher.

Version 1.0

October 2010

© Copyright 2010 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, 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 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, SAP NetWeaver, 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 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 those features 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 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.

Disclaimer

Some components of this product are based on Java™. Any code 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 only to be used by SAP’s Support Services and may not be modified or altered in any way.

Document History Document Version Description

1.00 First official release of this guide

Typographic Conventions Type Style Description

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text>

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

Icons Icon Description

Caution

Note or Important

Example

Recommendation or Tip

Table of Contents

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

2. Prerequisites ........................................................................................................................ 1

3. Step-by-Step Procedure ...................................................................................................... 2 3.1 Drill Through to BEx Query ........................................................................................... 2

3.1.1 Configure Drill Through Target to BEx Query .................................................. 2 3.1.2 Test Drill Through to BEx Query from BPC Report ......................................... 8

3.2 Drill Through to an ECC Transaction.......................................................................... 13 3.2.1 Configure Drill Through Target to ECC Transaction ...................................... 15 3.2.2 Test Drill Through to an ECC Transaction from BPC Report ........................ 22

4. Appendix ............................................................................................................................ 27 4.1 Create a BEx Query for the BPC Application ............................................................. 27 4.2 Determine Field Names & Function Codes in ECC Transactions .............................. 46


1. Business Scenario In this scenario, the user would like to select a cell within a SAP BusinessObjects Planning and Consolidation, version for Netweaver (BPC) report and drill through to a SAP Netweaver Business Warehouse (BW) Business Explorer (BEx) Report or to an ECC transaction. BPC currently only supports drill through via a parameterized URL. The drill through configuration wizard allows you to define a URL as well as URL parameters, whose values can be filled by properties values at runtime.

2. Prerequisites Required/recommended expertise or prior knowledge

• SAP BusinessObjects Planning and Consolidation 7.5, version for SAP NetWeaver, SP00 and higher

Additional Documentation • RKT Online Knowledge Product

http://service.sap.com/rkt On the left hand side, navigate to SAP Ramp-Up Knowledge Transfer -> SAP BusinessObjects EPM Solutions -> SAP BO PC 7.5, version for SAP NetWeaver

• Other EPM How-To Guides http://wiki.sdn.sap.com/wiki/display/BPX/Enterprise+Performance+Management+%28EP

M%29+How-to+Guides • SAP Help Library – Business Add Ins

http://help.sap.com/saphelp_nw70/helpdata/en/8f/f2e540f8648431e10000000a1550b0/frameset.htm

October 2010 1

http://service.sap.com/rkt

http://wiki.sdn.sap.com/wiki/display/BPX/Enterprise+Performance+Management+%28EPM%29+How-to+Guides

http://wiki.sdn.sap.com/wiki/display/BPX/Enterprise+Performance+Management+%28EPM%29+How-to+Guides

http://help.sap.com/saphelp_nw70/helpdata/en/8f/f2e540f8648431e10000000a1550b0/frameset.htm


3. Step-by-Step Procedure In this section, we will show how to configure a drill through target for both a BEx Report as well as to an ECC transaction. This guide assumes that a BEx Report has already been created with parameter variables configured. This guide also assumes that an Internet Transaction Server (ITS) Webgui is also accessible within the ECC system.

3.1 Drill Through to BEx Query This section will focus on how to configure a drill through target to a BEx Query. In this example, we will configure a drill through target to a pre-existing BEx query called ZDT_PLANNING. This query was created using the 7.x version of the Query Designer, but the 3.x URL format will be used when defining the drill through target in BPC. The reason is that, at the time of this writing, there are limitations when using the 7.x URL format. For example, the parameter names used in the 7.x format are too long to be used when configuring the parameters in the BPC Admin client. A future BPC support package will address these limitations, but until then the 3.x format should be used. This BEx query has been created with two variable parameters called ZDTACCT and ZDTTIME. Values from a BPC report will be passed to these parameter variables when triggering the BEx Query. Note: If you are interested in how this query was created, please see the step-by-step instructions in Appendix 4.1

3.1.1 Configure Drill Through Target to BEx Query

1. Log on to the BPC Admin Client and click on “Drill Through“ from the appropriate Application.

October 2010 2


2. From the action pane, click “Add Drill Through”.

3. Enter the Drill Through ID and a description, then click “Next“.

4. Next, enter the URL for the BEx Query. Again, the 3.x URL format works best here. An example URL would be: http://<host>:<port>/sap/bw/bex?&query=<query_name>

October 2010 3


5. Enter the parameters as shown below. BEx Query uses specific parameter names such as VAR_NAME_1, VAR_VALUE_EXT_1. This is how the parameter values are passed through the URL. You must supply the name of the parameter as well as the actual value assignment. So for each parameter variable defined in your BEx Query, you must define a pair of parameters here, one for the name of the variable in the BEx Query, and the other for the actual value to be passed.

6. Next, click the “Test” button.

October 2010 4


7. Click “Run Test”.

8. The report is then displayed. Notice the parameters have been passed successfully to the BEx query.

October 2010 5


9. Click “Close”.

10. Click “Next”.

October 2010 6


11. Click “Apply”.

12. The drill through target is now configured successfully.

October 2010 7


3.1.2 Test Drill Through to BEx Query from BPC Report

1. Log on to BPC Excel client and set the current view as shown below.

2. From the action pane, click “Reporting and Analysis“.

October 2010 8


3. Click “Open a blank workbook.

4. Enter EVDRE() into an empty cell and press “Enter”.

5. Next, click “Refresh Workbook”.

October 2010 9


6. From the EVDRE Builder, change the member selection to read as SELF,BAS and click “Ok”.

October 2010 10


7. Select the cell as shown in the image below.

8. From the action pane, click “Drill Through”.

October 2010 11


9. Select the drill through target, and click the green check.

10. The BEx Report is then shown in the browser. Notice that the parameters have been passed to

the query, and that only the CE0004010 account is shown for 2006.MAR.

October 2010 12


3.2 Drill Through to an ECC Transaction This section will focus on how to drill through to an ECC transaction. In this example, the user will configure a drill through target to the FAGLB03 transaction in ECC. The ECC company code and ECC account, which are properties of the associated BPC dimensions, will be passed to the drill through target via URL parameters. The images below show the dimension property values which have already been configured. Note: This guide assumes that the user knows how to update the dimension properties as well as the property values via the BPC Admin console. Furthermore, it is assumed that these steps have already been carried out before configuring the drill through target. The P_CC dimension has one addition property called ECC_COMP_CODE. Notice that the ECC_COMP_CODE property value for the All_CC cost center has been updated in the member sheet.

October 2010 13


The P_ACCT dimension has one addition property called ECC_ACCT. Notice that the ECC_ACCT property value for the CE00010000 account has been updated in the member sheet.

October 2010 14


3.2.1 Configure Drill Through Target to ECC Transaction

1. Log on to the BPC Admin Client and click on “Drill Through“ from the appropriate Application.

2. From the action pane, click “Add Drill Through”.

October 2010 15


3. Enter the Drill Through ID and a description as shown in the image below. Then click “Next“.

4. In the next screen, insert the URL for the ITS webgui transaction. Example URL would be http://<host>:<port>/sap/bc/gui/sap/its/webgui?sap-language=EN&sap-client=<Client>&~transaction=<TransactionCode>

October 2010 16


5. Next, configure the URL parameters as shown below. In this example, we want to pass the ECC_COMP_CODE and the ECC_ACCT values to the appropripate screen parameter fields of the ECC transaction. Notice the ~okcode parameter. This is the global variable for function codes in ECC and needs to be set set so that the ECC transaction will continue pass the selection screen, and show the actual output screen of the transaction. Note: If you are interested in how to determine the field names or function codes of an ECC transaction, see Appenedix 4.2

6. Click the “Test“ button to test the drill through configuration.

October 2010 17


7. Enter the parameter values as shown here and click “Run Test“.

October 2010 18


8. The ITS session will then be launched in the browser. If required, enter the user id and password for this system. The transaction will then be shown. Notice the parameters have been passed through to the transaction.

October 2010 19


9. Click “Close”.

10. Click “Next”.

October 2010 20


11. Click “Apply”.

12. The drill through target has been successfully created.

October 2010 21


3.2.2 Test Drill Through to an ECC Transaction from BPC Report

1. Log on to BPC Excel client and set the current view as shown below.

2. From the action pane, click “Reporting and Analysis“.

October 2010 22


3. Click “Open a blank workbook.

4. Enter EVDRE() into an empty cell and press “Enter”.

5. Next, click “Refresh Workbook”.

October 2010 23


6. From the EVDRE Builder, make sure that the Member Selection is set to SELF,DEP and click

“Ok”.

October 2010 24


7. Select the cell as shown in the image below.

8. From the action pane, click “Drill Through”.

October 2010 25


9. Select the drill through target, and click the green check.

10. The ECC transaction will then be launched in the browser via ITS webgui. Notice that the parameters have been passed through via the URL from the actual report.

October 2010 26


4. Appendix

4.1 Create a BEx Query for the BPC Application This section will show how to create a BEx Query for a BPC Application or Cube. For this example, we will create the query for the same cube used in the drill through configuration.

1. Launch the BEx Query Designer and log on to the backend BW system.

2. From the Query menu, choose “New”.

October 2010 27


3. In the following dialog, choose “InfoAreas” from the list box at the top, then double click on “Business Planning and Consolidation”.

October 2010 28


4. Double click the appropriate InfoArea which corresponds to your BPC AppSet.

5. Double click on the cube which corresponds to the BPC Application,

October 2010 29


6. The query designer should now look like this.

October 2010 30


7. Expand the P_ACCT and TIME dimensions as shown below.

8. In the middle section of the designer, click on “Rows/Columns”.

October 2010 31


9. Drag and drop the P_ACCT dimension from the structure on the left to the “Columns” box.

October 2010 32


10. Drag and drop the TIME dimension from the structure on the left to the “Rows” box.

11. Drag and drop the SignData key figure from the structure on the left to the “Columns” box.

October 2010 33


12. Click on the “Filter” button in the middle section of the Designer.

13. Drag and drop the P_ACCT and TIME dimensions from the “Default Values” box into the

“Characteristic Restrictions” box as shown below.

14. Right-click on P_ACCT in the “Characteristic Restrictions” box, and choose “Restrict”.

October 2010 34


15. Choose “Variables” from the list box at the top. Then choose “Characteristic Value Variable” in the list box below. Finally, click the “Create” button.

October 2010 35


16. On the “General” tab, enter the description and technical name as “ZDTACCT”.

October 2010 36


17. From the details tab, change to “Mandatory” and click “OK”.

18. Click “OK”.

October 2010 37


19. Select ZDTACCT from the left side, and then click the “Arrow” to move it to the right side. Then click “Ok”.

20. Next, do the same thing for the TIME dimension, right click and choose “Restrict”.

October 2010 38


21. Choose “Variables” from the list box at the top. Then choose “Characteristic Value Variable” in the list box below. Finally, click the “Create” button.

October 2010 39


22. On the “General” tab, enter the description and technical name as “ZDTTIME”.

October 2010 40


23. From the details tab, change to “Mandatory” and click “OK”.

24. Click “OK”.

October 2010 41


25. Select ZDTTIME from the left side, and then click the “Arrow” to move it to the right side. Then click “Ok”.

26. From the Query menu, choose “Save As”.

October 2010 42


27. Save the BEx Query with a meaningful technical name and description. This technical name will

be important later when configuring the drill through target.

28. The message section shows that the query has been saved successfully.

October 2010 43


29. You can now test the query using the “Test” button in the designer. This will launch the query via the 7.x URL format. When configuring the drill through target in BPC, the 3.x URL format will be used instead.

7.x URL Format: http://<host>:<port>/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.pct!2fplatform_add_ons!2fcom.sap.ip.bi!2fiViews!2fcom.sap.ip.bi.bex?QUERY=ZDT_PLANNING&VARIABLE_SCREEN=X&DUMMY=2

30. Enter the filter values as shown here and click “Ok”.

31. The query is rendered with only the filtered intersection. The output is the 7.x output, so the BEx

query will look a little different when rendered using the 3.x URL format.

October 2010 44


32. If you were to manually enter the 3.x format into the browser, the filter value screen would look like the below screenshot. Enter the values as shown and click “Execute”. 3.x Format: http://<host>:<port>/sap/bw/bex?&query=ZDT_PLANNING

33. The output of the query show look like the image below.

October 2010 45


4.2 Determine Field Names & Function Codes in ECC Transactions

If you are configuring a drill through for an ECC transaction, you will need to find the field names associated with the screen of the transaction. In this example we will show how to determine the field names of transaction FAGLB03. You must log on to the ECC server via SAPgui.

1. Log on to the ECC system and go to transaction FAGLB03. Put the cursor in the “Account Number” field and press F1.

October 2010 46


2. Click on the “Technical Information” icon.

3. From this screen, you can get the screen field name. In this example, it is RACCT-LOW. Click the green check to exit this screen.

October 2010 47


4. Next, determine the function code of a button on the screen. Use the “Tab” key to place the cursor on the “Execute” button. Keep hitting “Tab” until you see the icon outlined as shown in the image below. Then press F1.

5. Click the “Technical Information” icon.

6. The function code is then shown in the dialog box.

October 2010 48

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

How to... Configure Drill Through BPC

Documents

party web

bpc admin

bpc excel

characteristic

sap businessobjects

click refresh

technical

click run