Skip to main content

Translating Labels for Operations and Operation Items in Flexible File Framework

Missing translations for operation and tab labels lead to incorrect or incomplete UI display in different logon languages.

S
Written by Strutzke, Marcel

Product Area

FS² CCC


Problem

Applications based on the Flexible File Framework require translations for all operation labels and operation item tabs in every installed logon language.

If translations are missing:

  • UI texts may appear incomplete or inconsistent.

  • Users see incorrect or fallback language labels.

  • System usability decreases for non-default language users.

Additionally:

  • Translations are language-dependent customizing entries.

  • They must be maintained in the development system.

  • They must be transported to production systems.


Solution Steps

1. Access File Customizing

Navigate to:

  • Menu Path: Administration → FS² Credit / FS² Collections / FS² Compliance → File Customizing


2. Translate Tab Labels

  1. Open Tabs in File.

  2. Select all entries:

    • Click Select All or press F7.

  3. Navigate to:

    • Menu → Goto → Translation

  4. Choose the target language (e.g., French) and confirm.

  5. In the translation popup:

    • Maintain all missing labels in the target language column.

  6. Save your changes.

  7. Assign a transport request when prompted.


3. Translate Tabs Derived from Operations

Some tabs inherit labels from operation types.

If translations are missing:

  1. Navigate to Operation Type Customizing.

  2. Select the relevant operation.

  3. Open Tabs for Operation.

  4. Repeat the same translation steps described in Step 2.


4. Translate Operation Labels

  1. In the same customizing area, select all operation types

  2. Mark all entries.

  3. Go to Translation.

  4. Maintain all missing translations.

  5. Save and assign to a transport request.


Known Limitations

  • Translations must be maintained manually for each installed logon language.

  • Missing any language will result in inconsistent UI behavior.

  • Changes are not active until transported and imported into target systems.

Did this answer your question?