The Config Team Ltd
Contact usDemo App
PreBiltâ„¢ for EWM
PreBiltâ„¢ for EWM
  • PreBilt for EWM
    • Overview
    • Functionality
    • Frequently asked questions
    • Release notes
      • v4.13 release notes
      • v4.12 release notes
  • Installation
    • Minimum requirements
    • Prerequisites and assumptions
    • Backend installation
    • Frontend installation
    • UI deployment
  • Configuration Guide
    • EWM RFUI requirements
    • Initial generation of EWM ITS screen templates
    • Overview screen of technical information
    • BC sets
    • Customising the screen layout
      • Logical Transactions and Step Header
      • Detailed screen fields customisation
        • Replacement field labels
        • Field type
        • Toggling a drop-down list
        • Hiding field borders
        • Hiding a field from display
        • Hiding a field from display when empty
        • Making a field read-only
        • Setting the display row for a parameter
        • Setting the visual length of a parameter
        • Setting the position of a parameter on the row
        • Maintaining table types for step-loop table functionality
        • Assigning field roles for table types
        • Maintaining a hint text
        • Defaulting a parameter value
        • Setting a parameter label's font style, size and colour
        • Setting a field value font style, size and colour
        • Adding a new screen field
        • Enhanced UoM selection
        • Defining Extra Screen Elements
        • Function code overrides
        • Menu extras
        • Function code extras
        • Exception code extras
        • Extra element types
        • Voice Fields
    • Translations
      • Downloading translations
      • Transforming the data
      • Uploading translations
    • Configuring PreBilt features
      • Communication Hub
      • Gamification
        • Competitions
        • Challenges
        • Game Monitoring
      • Voice
        • EWM RFUI requirements for Voice
        • Functional scope
        • Initial generation of ITS templates and customising for voice
        • Overview screen of technical information
        • Customising the voice flow for a screen
          • Maintain basic configuration
          • Maintain TCT mobility basic customising
          • Logical transaction and step header
          • Detailed screen field customisation
        • Master data
      • Analytics
        • Installation
        • Embedding Analytics into PreBilt
      • Unified Search Configuration
        • Installation
      • Image Capture
  • Using PreBilt
    • Screen elements
    • Process steps
    • Validation messages and troubleshooting
    • Operator messaging
    • Gamification
    • Troubleshooting
Powered by GitBook

Help

  • Can't find what you're looking for? E-mail us.

© The Config Team 1994 - Present Day

On this page

Was this helpful?

  1. Configuration Guide
  2. Translations

Transforming the data

PreviousDownloading translationsNextUploading translations

Last updated 6 months ago

Was this helpful?

The text file can be updated directly by manually replacing the source language field description with the translated text, then saving the changes after completing the update.

The most efficient way to update the fields is using the power query editor in Excel. To do this, open Excel, navigate to the Data tab, then select Get Data followed by From Text/CSV.

Select the downloaded txt file and select Import.

Select Transform Data then select the Transform tab, select the Split Column option by delimiter and maintain the below split by delimiter settings.

After selecting OK, the screen field description will be separated from the string.

Select File then Close and Load.

Add a new column to the right and start translating the screen field descriptions.

After completing the translation, save the file as a new .txt file. The translation can then be uploaded back into SAP.

Note

Ensure the file only contains the target language when saving.

It may also be necessary to split the menus, function codes and exception codes into a separate .txt file.