BW Text Variables of Type Replacement Path

Transcription

1 BW Text Variables of Type Replacement Path Applies to: This article is applicable to SAP BI 7.0. For more information, visit the EDW homepage. Summary This document shows how to use and also helps in the analysis of issues with BW text variables of type replacement path. The document will show how to create a sample query using this feature, discuss some parameters, tables and functions which will help in the analysis of problems in this area. Author: Ricardo de Azeredo Rosa Company: SAP Labs Brazil Created on: 11 July 2010 Author Bio Ricardo is a Support Consultant in SAP Labs Brazil since He has worked extensively on SAP R/3 and BW as a PM Certified and BW Consultant since His knowledge includes PM, CS, DMS, PP, PS modules and BW systems. Since 2004 he has focused his knowledge in Business Warehouse working in various critical projects in this area SAP AG 1

2 Table of Contents Text variables of type Replacement Path:... 3 Replacement Path Tab... 8 Hints Regarding Issues in this area:... 9 Detailing this issue: Replacing texts and/or Key: Tables T009 and T009C text for 0FISCPER Related Content: Copyright SAP AG 2

3 Text variables of type Replacement Path: This is possible to use text variables in order to handle dynamically the descriptions of formulas and selections in the query designer. This is useful, for instance, when you are using date restrictions in your query and you want to show the values listed by these restrictions in the query result. Below you will find some screenshots of a simple example: You have created a query with 3 selections where the characteristic 0FISCPER is restricted by 3 different months as per figure below: Next 3 figures show the details for each selection, where the characteristic 0FISCPER has been restricted by values for selection 1, for selection 2 and for selection3: 2010 SAP AG 3

4 Picture below shows the result when you execute the query (transaction RSRT). The information provided is not clearly understandable because this is showing the description provided for the selections in the query definition ( Selection1, Selection2 and Selection3 ): This is possible to make more understandable the result of this query replacing the static description of these columns by a dynamic description depending on the restriction set. In this case, using text variables you will be able to replace the description for your selection ( SelectionX in the example) by the value that you have restricted the characteristic 0FISCPER on each of these selections. You can follow the steps below in order to use that: In the selection definition, field Description, create a new text variable: Pressing the Create New function: 2010 SAP AG 4

5 In the next screen, you inform the Processing By as Replacement Path and the reference characteristic which you want to replace the information (that is 0FISCPER in our example). The Technical name is automatically suggested by system and it can be edited if necessary (VAR_ in this example): In the tab Replacement Path you need to inform with query object you want to replace the information (infoobject or variable) and also with data from that object should be used for replace. In our example it will be informed as Infoobject and Key respectively. You can find more information regarding the fields from that tab in the online documentation informed in item Replacement Path Tab of this document SAP AG 5

6 After save the new variable, it is going to be available and can be informed in the description field of our selections, as in figure below (if you enter that manually, this will require the tag & before and after the technical name of the variable): This is possible to set the same variable for all 3 selections from our example: 2010 SAP AG 6

7 Now, using the text variable type replacement path, the result is that the description for each selection is going to be replaced by the value from which 0FISCPER has been restricted in that selection, as you can see in the figure below: So, the presentation of data using this feature is more understandable. It also can be dynamically handled in case you restrict you characteristic by a variable in the selections SAP AG 7

8 Replacement Path Tab Some more information about Replacement Path Tab can be found in the online documentation below: Replacement Path: Replacement with a Characteristic Value /03/6ba03cc24efd1de a114084/fram eset.htm Replacement Path: Replacement from Variable 565cd22fc95f6ce a1553f6/frameset.htm 2010 SAP AG 8

9 Hints Regarding Issues in this area: In case the information provided by your variable is not returning the expected value, you can try to analyze that using the debug in transaction RSRT. For instance, in query below using a text replacement path variable, this is returning # instead of the description. In order to analyze this issue you can execute the query in transaction RSRT and entering in debug mode ( /h + enter ) before to press the execute button. When you reach the debug screen you can set a break point in the function module RRSV_CHAVL_TO_VALUE_CONVERT as you can see in figures below: 2010 SAP AG 9

10 After that, you can continue pressing F8. The code should stop in the break-point set as in the image below: In the ABAP Stack area, by double clicking in FORM ELTTXT_VAR_REPLACE this is possible to analyze the values passed to function module RRSV_CHAVL_TO_VALUE_CONVERT: 2010 SAP AG 10

11 Some interesting information is passed to the function module by structure L_S_VAR_LRECH, as you can see below: Backing to the code, you can set a break-point just after the call of FM RRSV_CHAVL_TO_VALUE_CONVERT and verify the value returned by that FM in the variable L_REPLTEXT: Note that in this case L_REPLTEXT is # which is our problem. Checking the values passed to that Function Module in structure L_S_VAR_LRECH, we can see that L_CHAVL in this case is K and the L_S_VAR_LRECH- FOFFSET is This explains the issue: L_S_VAR_LRECH- FOFFSET= 0010 means that an offset of 10 has been set to the value K In this case it will remove all the information from L_CHAVL. In such case system is programmed to show # instead of blank SAP AG 11

12 This is possible to confirm that FOFFSET is responsible by the issue if you change the value for L_S_VAR_LRECH-FOFFSET in the debug mode from 0010 to 0: The L_REPLTEXT should be correctly displayed after execute FM RRSV_CHAVL_TO_VALUE_CONVERT with L_S_VAR_LRECH-FOFFSET=0, as you can see below: 2010 SAP AG 12

13 Detailing this issue: The information from L_S_VAR_LRECH comes from table RSZGLOBV. In this case in order to fix the issue you need to maintain the correct OFFSET for your variable in that table (for this example the variable is TEXT_VAR_1): Replacing the FOFFSET from 10 to 0, for instance: After that, this is required to regenerate the query in transaction RSRT: 2010 SAP AG 13

14 So, it should return the desired results executing the query after the procedure: Note: You can execute the FM RRSV_CHAVL_TO_VALUE_CONVERT in transaction SE37. You can use the values passed to this FM in the debug mode as reference and this is also help in the analysis of issues in this area SAP AG 14

15 Replacing texts and/or Key: You can see in the previous example that this is returning the KEY of characteristic 0FISCPER and not the text as in some other examples from this document ( K instead OCT 2010 ). This is because the information from RSZGLOBV stored in the field FLAGR. If you want to change that you can select the option FLAGR = 3 instead of 1 for that variable: In case it is set to 3, the text is going to be displayed in the query result: Note: It is not recommended to change values directly in the tables. The idea in this case is just to illustrate how it works. You will reach the desired results if you manage the parameters for the variable using the Bex Query Designer in the Replacement Path Tab for the variable definition. Tables T009 and T009C text for 0FISCPER. In case you set your variable to be replaced by the text of 0FISCPER, the information selected by FM RRSV_CHAVL_TO_VALUE_CONVERT in this case is stored in table T009C and this depends on the Fiscal Year Variants settings from table T009. In the example from the previous session these are the values for those tables: T009: T009C: 2010 SAP AG 15

16 And this information is often loaded by the Transferring Global Settings feature as per online documentation below: SAP AG 16

17 Related Content: You will find additional information in the following links: m m For more information, visit the EDW homepage SAP AG 17

18 Copyright 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 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. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this docume nt 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 SAP AG 18