Show TOC

Overriding the Original Language of Customizing Tables for TranslationLocate this document in the navigation structure

Context

The original language is a basic concept in translation and a mandatory attribute of every translation object. An object needs an original language to prevent it from being overwritten, for example, and to facilitate the definition of consistent translation graphs.

Customizing table entries have no original language of their own. Instead, they inherit the original language definition of the table to which they belong. This is a problem if you create Customizing entries in a language that is not the original language of the table definition. You can translate these entries in transaction SE63 by accessing objects directly for translation. (If the target language is the same as the original language of the table definition, note that this requires you to override a warning that you are about to overwrite original language texts.) However, you cannot include them in the mass processing functionalities of transaction LXE_MASTER. For example, you cannot include them in an evaluation to generate a worklist, nor can you use the externalization function to export them for translation outside the system.

To solve this problem, you can configure the translation environment so that a fixed, customer-specified original language is assigned to all table classes that are normally relevant for Customizing and master data maintenance.

Procedure

  1. Call transaction SE16.
  2. In the field Table Name, enter LXE_KEY_VALUE.
  3. Choose Create Entries Create Entries or press F5.
  4. In the field PKEY, enter FORCE_ORIG_LANG_CUS.
  5. In the field PVALUE, enter the required single-digit language code such as E for English.
  6. Enter your user name in the field CR USER followed by the date and time in the fields CR DATE and CR TIME.
  7. Enter a comment in the field PCOMMENT, if required.
  8. Choose Start of the navigation path Table Entry Next navigation step Save End of the navigation path.

Results

This setting affects the following translation object types:

  • TADC Tables (Customizing - Maintenance by Customers Only)
  • TADE Tables (Control - SAP and Customer Key Areas)
  • TADG Tables (Customizing - No SAP UPD, Only INS)
  • TADA Tables (Application - Master and Transaction Data)
  • TAIC Tables (Customizing - Maintenance by Customers Only)
  • TAIE Tables (Control - SAP and Customer Key Areas)
  • TAIG Tables (Customizing - No SAP UPD, Only INS)
  • TAIA Tables (Application - Master and Transaction Data)

The results of this global parameter are as follows:

  • If you translate a Customizing table entry by accessing it directly in transaction SE63, and if the target language is the same as the original language of the table definition, SE63 no longer issues a warning that you are about to overwrite original language texts.
  • You can include such Customizing table entries in the mass processing functionalities of transaction LXE_MASTER. For example, you can include them in an evaluation to generate a worklist, or you can use the externalization function to export them for translation outside the system.
Note

You can only configure the translation environment so that one fixed, customer-specified original language is assigned to all table classes that are normally relevant for Customizing and master data maintenance. For example, if you have created French and English Customizing entries that belong to a table whose original language definition is German, you can define either French or English (but not both French and English) as the fixed, customer-specified original language