Translating Text for BI Objects 

Use

To translate the short and long texts of BI metadata objects, you use special functions of the Data Warehousing Workbench in your BI system as well as the translation environment provided by the SAP Web Application Server (ABAP).

Procedure

Do the following:

Step	Description
1	Collect the BI metadata objects to be translated along with all the dependent objects in the functional area Translation of the Data Warehousing Workbench.
2	Create a piece list with the objects to be translated in the functional area Translation of the Data Warehousing Workbench. The standard case is that a piece list is created. However, since a piece list cannot be created in a system that has the global setting “cannot be changed”, you use a workbench request in this case. For more information, see SAP Note 885571.
3	Generate an object list in the translation environment.
4	Process the worklist in the translation environment.
5	Create the M version of the BI objects using program RSO_AFTER_TRANSLATION in the ABAP editor.

You can then transport the translated objects to other systems.

Proceed as follows:

1. Collect objects for translation in the Data Warehousing Workbench

...

       1.      Start the Data Warehousing Workbench. (One way to do this is to choose Modeling → Data Warehousing Workbench: Modeling on the SAP Easy Access screen.) In the navigation window or the Goto menu, choose the Translation functional area.

The procedure for steps 2-5 mostly corresponds to the procedure for collecting objects. More information: Collecting Objects.

       2.      If you want to assign a source system, select  Source System Assignment. The Choose Source System by Default dialog box appears.

       3.      Make your settings in the selection lists  Grouping and Collection Mode.

       4.      In the navigation window of the Data Warehousing Workbench, select Object Types. In the central area of the screen, the system shows all the object types in the BI system that can be translated.

You can use Grouping to include all the objects before or after the selected object in the data flow in the translation. This allows you to translate a structured source system scenario, for example, from InfoSources and InfoCubes through to queries and workbooks.

       5.      In the central area of the screen, choose  Select Objects to select the required object type of the object(s) that you want to translate. Use drag and drop to transfer them to Collected Objects in the right-hand area of the screen.

       6.      In the Collected Objects area of the screen, the system displays the selected objects and all their dependent objects. The worklist automatically includes the following objects for object translation:

Worklist for an Object

Object	Example
BI Object	Query
Sub-objects for this object	For a query: InfoObjects (characteristics and key figures) and the predefined structures of an InfoProvider.
Objects connected to this object	For a query: those workbooks in which the query is embedded.

Note the following features:

○       The system only writes the selected objects to the piece list for the translation.

○       Objects in the SAP namespace (beginning with digit 0) are automatically not selected.

○       Like the Transport Connectionfunctional area, in the context menu you can select everything for a node or delete selections.

○       Texts are only translated if they belong to an object that is in the active version (A) or in a Business Content development system in the delivery version (D) because only these objects are transported. If you have changed the object texts, you must activate these objects before translation.

○       Navigation attributes have to be translated in addition to InfoObjects if their texts are not copied from the attribute characteristic. For the navigation attribute 0COSTCENTER__0RESP_PERS, 0RESP_PERS is not translated; characteristic 0COSTCENTER is translated with the text of this navigation attribute. Execute program RADNTLANG if the texts of the navigation attribute are not provided for translation. For more information, see SAP Note 480671.

○       The texts of the DDIC objects generated for the metadata objects are not displayed on the interface in the BI system. Therefore they do not need to be translated.

       7.      Choose  Translate. The Piece List for Translation screen appears.

2. Generate a piece list in the Data Warehousing Workbench

A piece list containing the objects to be translated is required to generate a worklist.

...

       1.      Choose  Create. The Select Request Type dialog box appears.

       2.      Choose Piece List. The Request dialog box appears.

If you cannot use a piece list because, for example, the system cannot be changed, you can use a workbench request instead.

       3.      Enter a name (the name has to be in the customer namespace [start with Y or Z]) and a short description for the piece list and save your entries. The Object Editing: Initial Screen dialog box appears.

       4.      Choose  Continue. The Create Object Directory Entry dialog box appears.

       5.      Enter a package and save your entries.

       6.      Choose  Continue. The Piece List for Translation dialog box appears again. You have successfully created a piece list for translation.

       7.      Choose  Continue. The Translation Environment screen appears (transaction code LXE_MASTER).

3. Generate an object list in the translation environment

In order to generate a worklist in the translation environment, you first have to create an object list for the piece list in the translation environment (transaction code LXE_MASTER).

...

       1.      On the Evaluations tab page, select Object Lists. The Object Lists dialog box appears.

       2.      You can create a new object list with  Create.

More information: Creating Object Lists in section Maintain parameters for object list according to piece list (ABAP developments only).

                            a.      Enter a text in the field Description Text and choose  Save. The Parameters dialog box appears. The number and description of the selected object list is displayed in the upper half of the screen.

                            b.      In the ABAP System pane next to the Transports field, select No Entries and choose  Continue. The Transports/Piece Lists dialog box appears. The number of the selected object list is displayed in the upper half of the screen.

                            c.      Enter the name of the piece list you want to include in the object list. If you want to evaluate more than one piece list, you must create an entry for each piece list.

                            d.      In the next two columns, enter * as the transport type and transport status; do not enter a value in the other fields (date and time).

                            e.      Save your entries for the piece list. The Parameters dialog box appears. The number of selected piece lists is given on the pushbutton next to the field Transports.

                              f.      Save your entries for the parameters of the object list.

       3.      Generate the required object list by selecting it and choosing Activate. The Start Time dialog box appears and you can schedule the background job. (The name of the job is OBJLIST_xxxx, where xxxx is the number of the object list.)

More information: Creating Object Lists in section Generate object list

4. Process the worklist in the translation environment

...

Once the job for generating the object list has ended, you can translate the objects contained in this list from a worklist in the translation environment (transaction code SE63). Only the simplest case of such a translation is described below.

More information: Translation Tools for Translators (BC-DOC-TTL), especially the sections about Personal Worklists.

       1.      Check your default settings.

                            a.      Choose Utilities → Default Settings.

                            b.      From the input help, select the version of the source and target language (for example "deDE" for German and "enUS" for English US).

       2.      Call up your personal worklist with Worklist → Standard. The My Worklist: Parameters dialog box appears.

                            a.      Define your parameters (source language, target language, worklist number).

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

                            b.      Choose  Apply.

The Get Worklist screen appears.

       3.      Choose the Object List tab page.

                            a.      In the field Object List, select the object list from which you want to call the objects in your personal worklist.

                            b.      Select Deactivate Selection.

                            c.      Choose Load Objects.

More information: Accessing a Personal Worklist in section Accessing a personal worklist using an object list.

The Worklist screen appears containing the objects of your object list that are to be translated.

       4.      Enter a text in the target language for the objects to be translated, save your entries, and define the standard quality status "S" by choosing  .

More information: Translating Objects via a Worklist.

       5.      Once you have completed translation, save the entire worklist.

5. Postprocess using the program in the ABAP Editor

Texts are only translated for objects in the A or D version. Texts of objects in the modified version (M) are not translated. Therefore, when you call the maintenance transactions in the target language, the system displays the old texts (if available) for these objects first.

A program is available for viewing the newly translated texts in the system, also for objects in the modified version (M).

...

       1.      Call the ABAP Editor (transaction SE38).

       2.      Execute program RSO_AFTER_TRANSLATION with the following parameters:

Request/Task: Name of piece list

Language Key: Source language

Language Key: Target language

The system copies the texts for the objects in the piece list.

Result

The translated texts are available in your BI system.

Transporting the Translated Texts in the Data Warehousing Workbench

If you want to make the new texts available in other systems, you can transport them in the Transport Connection functional area of the Data Warehousing Workbench:

...

       1.      Collect the translated objects.

       2.      To transport the translated objects, choose Transport All Belowfrom the context menu. This writes all the collected objects explicitly to a request. This is necessary if some of the objects have already been transported and therefore are not selected by default.

During the transport the entire objects (not just the texts) are transported. Depending on the number of objects, the import may take some time.

More information: Transporting BI Objects.