Translating Text for BI Objects 

Use

In the Translation functional area of the Data Warehousing Workbench you can collect all the objects for one or more metadata objects in the BI system and then translate the short and long texts.

Integration

...

In the Translation functional area of the Data Warehousing Workbench, the system creates a piece list with the objects that are to be translated.

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.

You use this to call the translation planner (transaction SLWB).

After translation, you have to call program RSO_AFTER_TRANSLATION in the ABAP Editor (transaction 38).

In the Transport functional area of the Data Warehousing Workbench, you transport the translated objects.

Features

The worklist automatically includes the following objects for object translation.

Worklist for an Object

Object Included	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 a query in which the query is embedded.

Activities

Collecting Objects in Data Warehousing Workbench for Translation

...

       1.      Call 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 to 5 is very much the same as the procedure for installing Business Content (steps 2 to 5). For more information, see Installing Business Content .

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

       3.      Change the required settings in the  Grouping selection list and the Collection Mode.

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

You 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&Drop to transfer them into the right-hand Collected Objects area of the screen.

In the Collected Objects area of the screen, the system displays the selected objects and all dependent objects.

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 Transportfunctional 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. When 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.

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

Creating a Piece List in the Data Warehousing Workbench

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

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

       8.      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.

       9.      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.

   10.      Choose  Continue. The Create Object Catalog Entry dialog box appears.

   11.      Enter a package and save your entries.

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

   13.      Choose  Continue. The Translation Planner Overview screen appears.

Creating an Object List and Editing a Worklist 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 planner.

   14.      On the Translation Planner Overview screen, choose the Object Lists tab page. Use Create to create a new object list:

                            a.      In the Description field, enter a text.

                            b.      In the Transport Evaluation area of the screen, use input help to select Single Transport.

                            c.      In the Parameter field, enter the name of the piece list that you selected or created in the Data Warehousing Workbench.

                            d.      Set the indicator for the Start Evaluation in Next Step option.

                            e.      To schedule a job for the evaluation, choose  Continue.

For more information, see Creating Object Lists.

   15.      In order to create and process a worklist in transaction SE63, proceed as described in the documentation for the translation environment (see Tools for Translators (BC-DOC-TTL)).

Postprocessing Using Program in 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 if you want to be able to see the newly translated texts in your system for objects that have the modified version (M) too.

   16.      Call the ABAP Editor (transaction SE38).

   17.      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.

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 functional area of the Data Warehousing Workbench. For more information, see Transport Systems.

   18.      Collect the translated objects.

   19.      To transport the translated objects, choose Transport All Below from 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 runtimes may take some time.

Result

The translated texts are available in your system and in additional BI systems.