How-to Guide SAP NetWeaver 7.0

How To… translate BI Objects Version 1.00 – March 2007 Applicable Releases: SAP NetWeaver 7.0 Business Intelligence - Enterprise Data Warehousing

© Copyright 2007 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 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.

1 Scenario As many SAP NetWeaver BI systems serve as enterprise data warehouses, worldwide system usage across different time zones using different languages is a frequent scenario today. In order to support your BI system users who utilize the system in their first language, SAP NetWeaver BI offers translation tools that will allow you to translate the descriptions of BI Metadata Objects from their source language to a target language, using the Translation Environment of the SAP Web Application Server (ABAP). This technique applies to BI Objects appearing in the Business Explorer as they are visible to a high number of end users, and also BI InfoProviders or BI data flow objects visible in the data warehousing workbench (or other transactions), especially useful when globally implementing and operating an enterprise data warehouse. As example, we will translate the InfoCube RHSALES01 and all dependent InfoObjects from German to English. Initially, the InfoCube RHSALES01 has been created in German…

… which results in the fact that users logging on in English will only see technical names for most of the (non BI content) objects:

2 Introduction This documents aims at illustrating the entire process for translating BI objects using the above mentioned example. In order to translate BI metadata objects we will use specific tools in SAP NetWeaver BI, as well as the tools provided by the standard translation environment of the SAP Web Application Server (ABAP). No additional coding is necessary. The main steps described in this document will be:

1. Create a piece list in the data warehousing workbench 2. Create an object list in the translation environment 3. Edit a worklist in the translation environment 4. Transfer texts to the M-version of the BI Objects using program

RSO_AFTER_TRANSLATION 5. Create a transport request for the translated BI Objects in the data

warehousing workbench

For prerequisites and additional questions on translating BI Objects, it is strongly advised to refer to the standard documentation: http://help.sap.com/saphelp_nw2004s/helpdata/en/43/a1f5388b99f321e10000000a11402f/frameset.htm Example: In this simple scenario, every single object will be translated individually and sequentially. If you want to translate a high amount of objects more efficiently, you may use proposal pools and automatic distribution. Please refer to the standard documentation on the translation tools for more information on these features: http://help.sap.com/saphelp_nw2004s/helpdata/en/77/5719d2492011d1894a0000e829fbbd/frameset.htm Also, please carefully read the following SAP notes: 496192 Translating and transporting BW objects 885571 Translation connection in system is 'Not changeable' These information sources will provide additional details, for example, on translating navigation attributes, and on how to handle generated data dictionary objects for BI objects.

3 The Step By Step Solution

3.1 Create a Piece List in the Data Warehousing Workbench In the translation functional area of the data warehousing workbench (transaction RSA1), create a piece list with the objects that are to be translated. In this chapter, no additional detail is provided on how to collect BI Objects in the Data Warehousing Workbench (before creating the Piece List). In this context, we utilize the same technique to collect BI objects that is employed in other areas, such as in BI content activation and transport connection.

1. Collect the Relevant Objects in the Data Warehousing Workbench Transaction RSA1 Translation

In this example, InfoCube RHSALES01 has been collected with the grouping option “Only necessary objects”.

Press the “Translate” button.

2. Create a Piece List for Translation At the dialog box for piece list, choose “Create”.

3. Create a Piece List for Translation

At the “select request type” dialog, select “Piece List”.

4. Create a Piece List for Translation Give the piece list a technical name (in customer namespace, starting with “Y” or “Z”) and a description.

Save your piece list.

5. Create a Piece List for Translation

Assign your piece list to a package.

6. Create a Piece List for Translation

Choose “continue” (ENTER) in the “piece list for translation” dialog.

If you collected only a small number of objects, you can skip ahead to step 17 b.). However, if you experience (runtime) problems, please follow the recommended approach and carry on with step 7.

3.2 Create an Object List in the Translation Environment In the administration toolset of the translation environment (transaction LXE_MASTER), create an object list. For additional information on creating object lists, please go to the SAP Help Portal: http://help.sap.com/saphelp_nw2004s/helpdata/en/d4/34196a249711d3b29e0000e817ab98/frameset.htm

7. Create an Object List In the evaluations tab, choose object lists (transaction LXE_MASTER)

8. Create an Object List In the object lists dialog, choose “create”.

9. Create an Object List

Enter a description for your object list and save.

10. Assign the Piece List In order to include the piece list in the object list press the “No Entries” button next to “Transports” (under “ABAP system”.

11. Assign the Piece List Enter the name of the piece list you want to include in the object list. If you want to evaluate several piece lists, create an entry for each one of them.

Enter “*” as the transport type.

Enter “*” as the transport status.

Do not enter any values in the other fields.

Save your entries.

12. Save the Object List Parameters

13. Generate the Object List Choose “Activate”.

14. Generate the Object List Schedule the background job which will generate the object list (the name of the job will be OBJLIST_xxxxx, xxxxx = number of the object list).

3.3 Editing a Worklist in the Translation Environment Once the job for generating the object list is finished, please go to the translation environment (transaction code SE63). In the next steps, all objects contained in the object List will be translated using a worklist. For additional information on working with personal worklists, please go to the SAP Help Portal:

http://help.sap.com/saphelp_nw2004s/helpdata/en/77/5719d2492011d1894a0000e829fbbd/frameset.htm

15. Check Your Default Settings In the translation environment (SE63), from the Utilities menu, choose Settings).

In particular, ensure that the Source Language and the Target Language settings correspond to your translation objective.

Be sure to check the specific format setting in which the languages must be entered (for example “US English” is Language code “enUS” and not simply “EN”). If necessary, choose the correct default entries using the value help.

Save your settings.

16. Access Your Personal Worklist

In the translation environment (SE63), from the Worklist menu, choose Standard.

Enter a 4-digit Worklist Number.

If you want to reset an existing personal worklist and/or a reservation number for accessing a personal worklist, select the Reset Worklist / Reservation checkbox.

Choose “continue”.

17. a) Access Your Personal Worklist Using an Object List (recommended approach) This screen appears after having entered your worklist number in the previous screen (SE63 Worklist Standard) and choosing “continue”. Select your object list using the value help.

Deactivate (all other) selections using the flag “Deactivate Selection”.

Load the worklist using the “Load objects” button.

.

17. b) Access Your Personal Worklist ------Using a Piece List

(alternative approach for small number of objects only) Enter your piece list using the value help (transport object or transport request).

Deactivate (all other) selections using the flag “Deactivate Selection”.

Load the Worklist using the “Load objects” button.

18. Enter target language texts for the BI Objects in the Worklist In order to translate a single object you have to double-click on it.

In this simple scenario every single object will be translated individually and sequentially.

If you want to translate a high amount of objects more efficiently, you may use proposal pools and automatic distribution. Please refer to the standard documentation on the translation tools for more information on these features.

19. Enter the equivalent text in the target language Save.

20. Set the standard quality status to

“S” by clicking on the “toolbox” icon (hammer and wrench).

21. … Choose the button “Status S”.

22. Save the completed Worklist

3.4 Transfer Texts to the M-Version of the BI Objects Using Program RSO_AFTER_TRANSLATION

Texts are only translated for objects in the A or D versions. Texts of objects in the modified version (M) are not translated. Therefore, a specific step is required - otherwise, when you call the maintenance transactions in the target language, the system displays the old texts (if available) for these objects first. This program will transfer the newly translated texts to the modified version (M) of the BI objects.

23. Call the ABAP editor (transaction SE38) and run program RSO_AFTER_TRANSLATION

24. Execute the program RSO_AFTER_TRANSLATION with the following parameters: Request/Task: Name of your piece list Language Key: source language Language Key: target language

25. Verify the translation in the respective object maintenance screen Log on to the BI system in target language.

For example: InfoCube maintenance in the data warehousing workbench.

3.5 Create a transport request for the translated BI objects in the data warehousing workbench

(Excerpt from the standard documentation on http://help.sap.com/saphelp_nw2004s/helpdata/en/43/a1f5388b99f321e10000000a11402f/frameset.htm) Transports for the translated objects are created in the transport connection of the data warehousing workbench (transaction RSA1). During the transport, entire objects (not just their texts) are transported. Depending on the number of objects, the import runtimes may be somewhat extended.

26. Transport the translated objects In transaction RSA1, under Transport Connection

Choose the BI object or objects that were your starting point for translation. Choose “Transport All Below” from the context menu. This writes all the collected objects directly to a workbench request. This is necessary if some of the objects have already been transported and therefore are not selected by default.

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