To translate the short and long texts of BW metadata objects, you use special functions of the Data Warehousing Workbench in your BW system as well as the translation environment provided by the SAP Web Application Server (ABAP).
The procedure is as follows:
Collect the BW metadata objects to be translated along with all the dependent objects under Translation in the Data Warehousing Workbench.
Create a piece list with the objects to be translated under Translation in the Data Warehousing Workbench.
The standard case is that a piece list is created. Since a piece list cannot be created in a system that has the global setting "cannot be changed" however, you use a workbench request in this case. For more information, see SAP Note 885571 .
Generate an object list in the translation environment
Process the worklist in the translation environment.
Create the M version of the BW objects using program RSO_AFTER_TRANSLATION in the ABAP editor.
You can then transport the translated objects to other systems.
Proceed as follows:
1. Collecting Objects in Data Warehousing Workbench for Translation
Call the Data Warehousing Workbench. (One way to do this is to choose SAP Easy Access screen) In the navigation window or the Goto menu, choose the Translation functional area.from the
The procedure for steps 2-5 mostly corresponds to the procedure for collecting objects. More information: Collecting Objects.
If you want to assign a source system, choose the function. The Choose Source System by Default? dialog box appears.
Change the required settings in the selection lists.
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 BW 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.
In the central area of the screen, choose 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. The worklist automatically includes the following objects for object translation:
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.
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 functional 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 navigation attribute 0COSTCENTER__0RESP_PERS, 0RESP_PERS is not translated. Characteristic 0COSTCENTER is translated with the text of this navigation attribute. If the texts for these navigation attributes are not offered in the translation, run program RADNTLANG. 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 BW system. They therefore do not need to be translated.
Choose . 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.
Choose . The Select Request Type dialog box appears.
Choose Piece List. The Create Request dialog box appears.
If you cannot use a piece list, because the system cannot be changed for example, you can use a workbench request instead.
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.
Choose . The Create Object Catalog Entry dialog box appears.
Enter a package and save your entries.
Choose . The Piece List for Translation dialog box appears again. You have successfully created a piece list for translation.
Choose . The Translation Environment screen appears (transaction 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 LXE_MASTER).
On the Evaluations tab page, select Object Lists. The Object Lists dialog box appears.
Use to create a new object list.
For more information, see Creating Object Lists in the section Maintaining Parameters for Object List According to Piece List (ABAP developments only).
Enter a text in the Description Text field and choose . The Parameters dialog box appears. The number and description of the selected object list is displayed in the upper half of the screen.
In the ABAP System pane next to the Transports field, select No Entries and choose . The Transports/Piece Lists dialog box appears. The number of the selected object list is displayed in the upper half of the screen.
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.
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).
Save your entries for the piece list. The Parameters dialog box appears. The number of selected piece lists is displayed on the pushbutton next to the Transports field.
Save your entries for the parameters of the object list.
Generate the required object list by selecting it and choosing Activate. The Start Time dialog box appears. Here you can schedule the background job. (The name of the job is OBJLIST_xxxx, where xxxx is the number of the object list.)
For more information, see Creating Object Lists in the Generating Object Lists section.
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). The following section only describes the simplest case of this translation type.
For more information, see Translation Tools for Translators (BC-DOC-TTL), especially the sections about
Check your default settings.
Use input help (F4) to select the version of the source and target language ("deDE" for German and "enUS" for English US for example).
Call up your personal worklist with Worklist Standard. The My Worklist: Parameters dialog box appears.
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.
The Get Worklist screen appears.
Choose the Object List tab page.
In the Object List field, select the object list from which you want to call the objects into your personal worklist.
Select Deactivate Selection.
Choose Load Objects.
For more information, see Accessing a Personal Worklist in the 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.
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.
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. When you call the maintenance transactions in the target language, the system therefore 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.
Call ABAP Editor (transaction SE38).
Run program RSO_AFTER_TRANSLATION with the following parameters:
Request/task: Name of the piece list
Language key: Source language
Language key: Target language
The system copies the texts for the objects in the piece list.
The translated texts are available in your BW 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:
Collect the translated objects.
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, all entire objects (not just the texts) are transported. The import runtimes can be time consuming if a large number of objects are involved.
More information: Transporting BW Objects.