SAP TRANS RELEVANT TEXT - Guide
Get Example source ABAP code based on a different SAP table
Translation-Friendly Message Texts
ABAP_BACKGROUND
Message texts are translatable
When the message is sent using the statement
ABAP_RULE
Create placeholders in message texts with the unique names
ABAP_DETAILS
As the syntax in the various languages differs, a translator may need to change the order of the replacement texts when translating message texts. However, the translator can adapt the order of replacement texts only if the different placeholders in a message text each have unique names. In messages with multiple placeholders, you should therefore work with the numbered placeholders
Latest notes:
The same applies to all other constructs in which such placeholders are possible, for example, GUI titles of classic dynpros. In cases where text in text symbols is explicitly replaced by user-defined placeholders, the placeholders in the text symbol must have unique names and must be known clearly to translators as placeholders that are not supposed to be translated.
ABAP_HINT_END
ABAP_EXAMPLE_BAD
A bad example of a message text might look as follows:
If this message text was translated to
this would not cause any problems.
If this message text was translated to
a
ABAP_EXAMPLE_END
ABAP_EXAMPLE_GOOD
The following message text corrects the bad example:
For both translations,
and
a
ABAP_EXAMPLE_END