Activating Pseudo-Translation
Prerequisites
- The system must be Unicode.
- You must activate the following technical language key for the sole purpose of pseudo-translating your ABAP developments :2Q = Technical code 2.
- NLS settings must be maintained for technical language key 2Q in report RSCPINST.
- If technical language key 2Q is not offered for selection, use report RSCPINST to extend the language list.
- Technical language key 닱 (Unicode ID U+B2F1) must be added to system parameter zcsa/installed_languages.
- You must check table T002 to ensure that it includes an entry for technical language key 2Q .
If the entry does not exist, make sure that you activated technical language key 2Q correctly in accordance with SAP Notes 42305
and 1826966
in the SAP Online Service System. -
To execute report RS_LXE_FILL_PSEUDO_LANG, the role assigned to your system user must include authorization object S_ADMI_FCD with activity TRNR.
- SAP Enterprise Search using the TREX Engine (revision 61 or lower) must not be active in the system. After you have activated pseudo- translation, it is no longer possible to activate SAP Enterprise Search using the TREX Engine.
-
As of TREX revision 62, this technical restriction no longer applies. This means it is possible to activate pseudo-translation and SAP Enterprise Search using the TREX Engine.
-
- To prevent the underlying translation framework from automatically logging changes in tables LXE_LOG and SMODILOG when texts are pseudo-translated into language 2Q , you are advised to disable logging for technical languages in accordance with SAP Note 2087655
.
Context
For more information about pseudo-translation, see Pseudo-Translation.
To activate pseudo-translation after the above prerequisites have been met, you run a report that pseudo-translates texts in objects in the system into technical language 2Q.
Procedure
- If you want the report to run for all ABAP short text object types, leave the default value * in the Object Types (ABAP Short Texts) field. The advantage of this default setting is that the report runs for all ABAP short text object types, which maximizes the benefits of this solution. The disadvantage of this default setting is that the report takes longer to complete, because it needs to process every short text object type in the system.
- If you only want the report to run for specific object types, use the input help to select the object types that you require. For example, if you want to restrict the report to texts that appear on the user interface, use the input help for the Object Types (ABAP Short Texts) field to select all of the object types that belong to object group A5 User Interface Texts. The advantage of restricting the report to specific object types is that the report takes less time to complete, because it does not need to process every object type in the system. The disadvantage of restricting the report to specific object types is that it does not maximize the benefits of this solution, because translation objects skipped by the report are not pseudo-translated.
-
Periodic (Initial + Delta)
If you select this radio button and schedule the report to run periodically, the initial run evaluates all of the objects that you selected for the report. All subsequent delta runs are restricted to transport requests that were created or modified since the last report run.
For example, if you enter DTEL Data Elements in the Object Types (ABAP Short Texts) field and select the Periodic (Initial + Delta) radio button, the initial run pseudo-translates every data element short text object in the system. Subsequent delta runs pseudo-translate the data element short text objects contained in transport requests that were created or modified since the last report run.
The time stamp is refreshed every time that the report starts to run. If you choose Reset Date, an initial run takes place the next time that the report is executed.
-
Single Run
If you select this radio button, you can execute the report just once without the report preparing itself for subsequent delta runs.
For example, if you enter MESS Messages in the Object Types (ABAP Short Texts) field and select the Single Run radio button, the report runs just once to pseudo-translate every message short text object in the system.
-
Transport/Task
If you select this radio button, you can restrict the report to a transport request or task. Use the input help to select the transport request or task that you require.
For example, if you enter TLGS Lockable Logical Objects in the Object Types (ABAP Short Texts) field, select the Transport/Task radio button and specify transport request YI3K000309, the report runs just once to pseudo-translate every lockable logical short text object in transport request YI3K000309.
-
Translation Object List
If you select this radio button, you can restrict the report to objects in an object list. To do this, you must first create an object list in transaction LXE_MASTER. For more information, see Object Lists.
For example, if you enter * in the Object Types (ABAP Short Texts) field, select the Translation Object List radio button and select object list 10, the report runs just once to pseudo-translate every short text object in object list 10.
-
Client-specific Objects Only
If you need to pseudo-translate texts in client-specific objects in several different clients, then you must execute RS_LXE_FILL_PSEUDO_LANG in each of them. If you have already executed the report in one client, select this checkbox to restrict it to client-specific objects in all other clients so that you do not waste time running the report more than once for the same cross-client objects.
-
Exclude Translation Exceptions
If you select this checkbox, the report ignores all of the translation objects that are listed in tables LXE_PEXPT (which you are not allowed to maintain) and LXE_LEXPT. There are two ways for you to add translation objects to table LXE_LEXPT:
- You can maintain the table directly in transaction SE16. For more information, see Locking Individual Objects for Translation.
- You can choose Define Exception, specify a transport object in the Enter Transport Object dialog box, and choose Enter. This creates one or more entries in table LXE_LEXPT with the note RS_LXE_FILL_PSEUDO_LANG, which clearly indicates why the entries were added to the table.
- Exclude Local Objects
- Exclude Tables with Local Data
-
Exclude MIME Descriptions
You are advised to select this checkbox, because MIME description objects can cause the report to cancel.
Results
The report pseudo-translates texts in the selected objects into technical language 2Q. You can log onto the system with technical language key 2Q to check your pseudo-translated user interfaces, and fix any bugs that you find, before your texts are translated.
