Preparing a System for Translation 

Purpose

There are three ways of translating texts in an SAP system:

·        You can translate ABAP Dictionary-based texts directly be choosing Goto → Translation on the screen in question.

·        You can call up objects for translation directly in transaction SE63. You must know the object type, and the technical name of the object, to do this.

·        You can translate objects via global worklists. Detailed knowledge of individual objects is no longer required.

If you want to use global worklists to translate in an SAP system, you must set up the translation environment in transaction LXE_MASTER. The other two options do not require you to set up the translation environment, but fewer functions are available to you as a result.

Implementation Considerations

Before you start setting up the translation environment, you must clarify the following:

·        The system in which texts need translating

·        The installation of system languages (see notes 15023, 42305, and 73606 in the SAP Online Service System)

·        The installation of available languages (see Language Imports Using Transaction SMLT)

·        The installation of available proposal pools (see Proposal Pool Transports)

·        The administrator of the translation system

You must set up the translation environment before productive translation can start.

Integration

After you have made the above preparations, you start setting up the translation environment in transaction LXE_MASTER.

Translator profiles are used to control authorizations within transaction LXE_MASTER. The first person to set up transaction LXE_MASTER needs the authorization object S_ADMI_FCD to be assigned to his or her system user with the value TRNR.

After you have set up the translation environment, you must create an object list for all languages in transaction LXE_MASTER. The object list contains the objects whose texts need to be translated in the SAP system. You evaluate these objects to create global worklists of objects for translation.

Features

Transaction LXE_MASTER enables you to:

·        Define translation languages

·        Define translation graphs

·        Define translation clients

·        Define which object types need to be translated for each target language

·        Define distribution parameters for each target language

·        Define/activate translator profiles

·        Define priorities/standard servers for evaluation runs

·        Define translators

·        Assign collections to translation graphs

·        Assign collections to translators

·        Create object lists

·        Create language-dependent worklists