Translation Area

The launchpad itselft

• • • Search bar
    • Menu

Tile text elements

• • • Title
    • Subtitle
    • Catalog Title
    • Group title

Application labels

• • • Fields

Application messages

• • • Notifications

Back-end OData responses

• • • Metadata

The launchpad itself

Includes:

• • • Logon language selector
    • Search
    • Menus

How to translate the launchpad itself

Make sure that the required language pack is installed via transaction SMLT

To enable language selection at logon:

• • 1.  In transaction SICF, open and select service name “FLP” (path: /sap/bc/ui2/)
    2. Enter Edit mode by choosing Display ↔ Change button
    3. Choose Error Pages → Logon Errors → Configuration
    4. Make sure that Language is selected under System Logon Settings → Select Display → Language
    5. Select Input/green checkmark
    6. Save the data by choosing Display ↔ Change button again and hitting Yes to save

Tile text elements

• • • Catalog and group titles are defined in the launchpad designer.
    • The tile title and subtitles are defined in the tile catalog in the launchpad designer as well.
    • Translations are defined through transaction SE63 on SAP Gateway.

How to translate tile/group/catalog titles

• • 1. Open transaction SE63 in the SAP Gateway system hosting the launchpad
    2. Choose Short Texts button or Translation → ABAP Objects → Short Texts
    3. Expand 00 Meta Objects and select TABL Tables (Meta)
    4. Enter object name *WDY_CONF_USERT2*
    5. Set the source and target (translation) languages and choose Edit
    6. Set User Scope to A and use the search help (F4) on Configuration ID
    7. Select configuration ID for desired catalog and execute
    8. Enter the translations for relevant texts and save
    9. Repeat for the other configuration ID for the desired catalog and for the group
    10. It may be necessary to run report /UI2/INVALIDATE_GLOBAL_CACHES

Application labels

• • • Translated via i18n files
    • Editable through SE80
    • Standard applications may be extended to include other i18n files from Web IDE

How to translate application labels

• • 1. Start transaction SE80 in your SAP Gateway system
    2. Copy existing properties file to a new file for your own language
       • Enter the new name under Page. The format is: i18n/i18n_.properties
       • The system will now ask for an object key. Request this via SSCR keys

Note: The following caches must be invalidated after adding i18n file:

• • • /UI2/INVALIDATE_GLOBAL_CACHES
    • Global ICM cache (SMICM → Invalidate Globally)
    • Browser cache

Application messages

• • • These messages are located in a message class on your back-end system.
    • These messages are the ones that pop up automatically.

How to translate application messages

• • 1. Start transaction SE91 and enter the message class (a search help exists, so class can be found via package, application component, etc.)
    2. Select the message and translate each individual text via Goto → Translation
    3. Enter the target language
    4. Enter the translation and save
    5. After the translation is done, refresh your browser
    6. It may be necessary to run report /UI2/INVALIDATE_GLOBAL_CACHES

Back-end Odata

• • • Information from certain OData sources may be translated to reflect the local language settings
    • Since OData sources rely on RFC destinations, a unique RFC destination is required for each supported language
    • Example: Value Help values in apps

Setting the language for back-end Odata

• • 1. Go to transaction /n/iwfnd/maint_services in your SAP Gateway system
    2. Select the OData service your app is using and double-click in the system alias
    3. Choose the Edit button and click the Logon & Security tab
    4. Enter the desired language (If you leave it empty, the language will be the one specified in the login). Save the changes
    5. Now you can see the back-end information in the selected language despite the logon language

Logon language priority

• • The logon language is determined by the following mechanisms (higher priority first):
    1. URL parameter (sap-language), if maintained
    2. HTTP request accept-language header, which is defined by the browser and provides a list of languages with probabilities
    3. The value maintained in SU01 for a particular user
  • More information available in KBA 2420212 and KBA 2422021