Show TOC

Defining Translation ClientsLocate this document in the navigation structure

Prerequisites

You have defined the target language(s).

For more information, see Defining Target Languages .

Context

You need to define the client(s) of the system in which translation is to take place.

The client in which you translate should be the client in which the client-specific objects are available.

If translation-relevant, client-specific objects are contained in several clients, you can define multiple clients as translation clients.

You then need to take care with how you run the evaluations and the sequence in which translators translate the objects in their worklists. See the Example below for information on how to tackle translation in more than one client.

Procedure


  1. Call transaction LXE_MASTER.

  2. On the tab page, choose Languages per Client.

    A dialog box appears that lists all the available clients in the system.

  3. Double-click the client in which you want to translate.

    The Clients dialog box appears.

  4. If all the languages that you defined as target languages are to be translated in this client, choose Insert Translation Languages .

    The system inserts all defined target languages.

    Note

    You can delete a target language from this list by selecting the language from the list in this dialog box and choosing the Delete icon.

  5. Choose Save.

  6. Repeat this steps for all of the clients in which texts need translating.

Results

The client(s) for which you performed the above procedure are now defined as the translation client(s) in this system.

You can only run evaluations in a client defined as the translation client and for those target languages entered as target languages for this client.

You can now continue with the next step for setting up the translation environment. For more information, see Defining Object Types for Translation .

Example

You need to translate in both client 805 and 855 of a specific system. Client 805 is where you perform Customizing and needs to be translated into all defined target languages. Client 855 contains client-specific test data which needs to be translated into English only. You need to proceed as follows:

  1. Start of the navigation path LXE_MASTER Next navigation step Languages Next navigation step Languages per Client End of the navigation path.

  2. Double-click client 805 and choose Insert Translation Languages , then Save.

  3. Choose Languages per Client again and double-click client 855.

  4. Enter enUS in the first line under the Target Lang. column and choose Save.

  5. Create an object list in client 805 for all cross-client and client-specific objects that you want to translate and evaluate it.

  6. Trigger translation in client 805. Make sure the translators for English translate the client-specific object types first.

    See below for a list of the client-specific object types for translation.

  7. Once the English translators have finished translating the client-specific objects in client 805, you can create an object list for the client-specific objects only in client 855 and evaluate it.

  8. English translators can now log on in client 805 to continue translation of cross-client objects in client 805 and log on to client 855 to translate the client-specific objects for client 855.

  9. Repeat steps 5 to 8 of this procedure until development is finished and all objects are translated.

Client-Specific Object Types for Translation

Object Type ID

Object Type Description

Belongs to Object Group

ACGR

Roles

A5 - User Interface Texts

FEL1 to FEL4

Field Selection

A5 - User Interface Texts

FORM

Forms

B5 - SAPscript: Forms and Styles

HLD

HR Long Texts (Client-Specific)

D5 - HR Texts

HSD

HR Short Texts (Client-Specific)

D5 - HR Texts

STYL

Styles

B5 - SAPscript: Forms and Styles

TAD*

Tables

A6 - Table Entries

UPK

Authorization Profiles

G5 - Technical Short Texts

UPT

Authorizations

G5 - Technical Short Texts

VARI

Report Variants

A5 - User Interface Texts