Ansicht
Dokumentation

PAK_TRANSLATION_DEPTH_TEXT - Translation-Relevance

PAK_TRANSLATION_DEPTH_TEXT - Translation-Relevance

CPI1466 during Backup   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Internal SAP classification defining the languages into which a development package is translated

Meaning

The translation relevance determines the languages into which the repository objects in a development package are translated.

You choose the translation relevance based on the target group of each development package. If you are in any doubt, contact your translation delivery manager maintained in Sirius for your program.

The options are:

  • End User UI - All Languages

    Use this classification if the objects in the package contain texts visible to business end users. Texts in objects in the package are then translated into all languages in which the product is available. For business applications, this is usually the correct classification.
  • End User UI - Reduced Translation Scope

    Choose this classification if
  • Either the package is aimed at business end users and contains country-specific developments, such as Payroll for France. Texts in objects in the package only require translation into the language(s) for the country/countries concerned.

  • Or you want to restrict translation to fewer languages than the languages in which the full product is available.

In both cases, contact your translation delivery manager, who will then make the necessary settings in the translation system for the language(s) required

  • Administrator UI - Admin Languages

    Use this classification only for packages in the ABAP Platform, which are intended for system administrators. Texts in objects in the package are then translated into English, German, French, and Japanese for 7.0 - 7.30, plus into Portuguese, Russian, and Simplified Chinese as of 7.31. Do not choose this classification if the package contains objects intended for end users of business applications.

  • Developer UI - German/English Only

    Use this classification only for packages in the ABAP Platform, which are intended for system developers. This type of package usually consists of ABAP Workbench applications, such as tools for development, testing, and analysis, plus other support tools and methods for modifying or enhancing code. Texts in objects in the package are then translated into German and English only. Do not choose this classification if the package contains objects intended for end users of business applications.
  • Not Translation-Relevant

    Choose this classification if the package is not relevant for translation, because the package is, for example, not delivered or is only used internally or by hosting partners, and not by any customer.

Use

When you define the translation relevance of a package, you decide whether the UI texts in the objects in the package are translated and into which languages.

The classification is not inherited by any subpackages. You must classify subpackages separately. They can have a different classification from the structure package.

There is no technical default. Translation Relevance is a mandatory field and must be defined as soon as you create a package. If you need to change the translation relevance of a package after you have classified it, contact your translation delivery manager. Please note that the number of target languages can never be reduced once the package has been shipped (see explanation under CAUTION below).

CAUTION

  • Any changes to the classification that lead to a reduction in the number of translation languages can cause the following problem:
If the package already contains translated texts for languages that are no longer translated as a result of this change, then these texts are no longer included in the translation process for these languages. As a result, any updates to the source texts are not reflected in the obsolete translation language. The system continues to display outdated translations, even if the system is a customer system.
  • The above problem also affects repository objects that are moved between packages if the new package is translated into fewer languages than the old package. It is particularly important to bear this in mind because there is no warning when you move an object from one package to another. In this case, contact your translation delivery manager.

NOTE

Local packages, such as temporary packages ($TMP) and HOME packages (from the software component HOME), are never translated. Package Builder hides the Translation Relevance field for these packages.

Structure packages and main packages cannot contain development objects (except subpackages and package interfaces). When you create a structure package, the translation relevance is automatically set to “Not Translation-Relevant”, no matter what you enter.






TXBHW - Original Tax Base Amount in Local Currency   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 5435 Date: 20240329 Time: 112301     sap01-206 ( 111 ms )