Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-TOO-PAK (Application Component) Package Tools⤷
SPAK_API (Package) Package API
Basic Data
| Data Element | PAK_TRANSLATION_DEPTH_TEXT |
| Short Description | Translation-Relevance |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AS4TEXT | |
| Data Type | CHAR | Character String |
| Length | 60 | |
| Decimal Places | 0 | |
| Output Length | 60 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 20 | Transl.-Relevance |
| Long | 40 | Translation-Relevance |
| Heading | 55 | Translation-Relevance |
Documentation
Internal SAP classification of the translation depth (number of target languages) of the texts in a development package
Meaning
The classification of translation-relevance determines the amount of translation required in follow-on translation systems for the repository objects in a development package.
The translation-relevance of a development package is classified by an indicator set for the package in question, and is not inherited by subpackages that may underlie this package in a hierarchy. Any subpackages must be classified separately, and they can have a different classification from the superpackage.
Structure packages and main packages can not contain development objects (except subpackages and package interfaces). When creating such a package, the translation relevance is automatically set to 'No Translation' irrespective of the value for the translation relevance entered by the user.
The classification of translation-relevance is based on various roles or target groups. You can select precisely one of the following translation-relevance options for each development package:
- Administration Tools
The packages with this classification contain texts intended for system administrators. This target group is provided with administration tools available in four standard language versions: English, German, French, and Japanese. A package with this classification must not contain any texts intended for the end users of business applications. - End User - Translation into all Supported Languages
The applications in packages with this classification are aimed at business end users. The texts in the packages are translated into all supported languages. This means that projects including packages with this classification incur the highest level of translation costs. - End User - Reduced Translation Scope
The applications in packages with this classification are also aimed at business end users. However, the translation-relevant texts in these packages are usually translated according to country-specific requirements. This reduces the number of translation languages from the previous option. In this case, the target languages are not predefined and the translation scope must be discussed with the responsible translation coordinator (SLS Account Manager). - Development Tools
Packages with this classification contain texts for developers. These packages generally consist of ABAP Workbench applications, such as tools for development, testing, and analysis, plus additional support tools, and methods for modifying or enhancing code. - No Translation
Packages with this classification are not translated.
Use
When you select a classification of translation-relevance, you decide whether the text components in the package in question (such as UI texts, message texts, or long texts for F1 help) are translated, and into which target languages.
There are no defaults for the classification of translation-relevance; the package property Translation-Relevance is a mandatory field and must be defined as soon as you create a package. You cannot change this property in Package Builder once you have created the package.
NOTE
Local packages, such as the temporary packages ($TMP), and the 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 can not contain development objects (except subpackages and package interfaces). When creating such a package, the translation relevance is automatically set to 'No Translation' irrespective of the value for the translation relevance entered by the user.
CAUTION!
Note that any changes to the classification that incur a reduction in translation scope can cause the following problem:
If the package in question already contains translated texts for languages eliminated by this change, then these texts will no longer be included in the translation process for these languages. This would also mean that systems would display obsolete texts in the eliminated languages, and not the most up-to-date versions.
CAUTION!
The problem described above also affects repository objects that are moved between packages, when the target package has a classification with a lower translation scope than the old package. It is particularly important to bear this in mind because you do not see a pertinent warning when moving an object to another package.
NOTE
This classification only determines the target languages into which a package is translated. The original language of the repository objects in a package, however, can be defined independently of the translation classification.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 740 |
