This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
The Step By Step Solution ............................................................................................................................ 3
Create a piece list in the data warehousing workbench ............................................................................................... 3
Create an Object List in the Translation Environment .................................................................................................. 5
Editing a Worklist in the Translation Environment ...................................................................................................... 10
System Translating BI Object First Time .................................................................................................................... 12
Using Program RSO_AFTER_TRANSLATION.......................................................................................................... 17
Related Content .......................................................................................................................................... 19
Disclaimer and Liability Notice ..................................................................................................................... 20
Translating Custom BI Objects
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
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:
Create a piece list in the data warehousing workbench
Create an object list in the translation environment
Edit a worklist in the translation environment
Transfer texts to the M-version of the BI Objects using program RSO_AFTER_TRANSLATION
Create a transport request for the translated BI Objects in the data warehousing workbench
The Step By Step Solution
Create a piece list in the data warehousing workbench
1. Collect the Relevant Objects in the Data Warehousing Workbench
Transaction RSA1 --> Translation
Translating Custom BI Objects
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
In order to include the piece list in the object list press the “No Entries” button next to “Transports” under “ABAP system”.
8. 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.
Translating Custom BI Objects
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
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.
12. 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.
13. 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”.
Translating Custom BI Objects
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
14. Access Your Personal Worklist Using an Object List This screen appears after having entered your worklist number in the previous screen (SE63Worklist 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..
Translating Custom BI Objects
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
16. 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.
Translating Custom BI Objects
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
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.
21. Execute the program RSO_AFTER_TRANSLATION with the following parameters:
Translating Custom BI Objects
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not
supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and
services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.