1. Implementation Guide
  2. Globalization

5 Globalization

Translation

Trade Management supports operating the user interface in 19 languages, including English. As part of the install options for Merchandising, you'll designate one language as "primary". This primary language is used by Trade Management as well and determines how labels and data are displayed by default to users, what is held in the base tables for data entities, and what is used in integration to other systems. The primary language is also what is loaded as a default for all screen labels, error messages, and seeded data at the time of installation. By default, only the primary language is loaded in Trade Management, but if you wish to have more languages loaded, then you can request to have the language strings loaded for these languages as well.

In addition to English, the languages that can be supported in the user interface include:

  • Arabic

  • Chinese (simplified)

  • Chinese (traditional)

  • Croatian

  • Dutch

  • French

  • German

  • Greek

  • Hungarian

  • Italian

  • Japanese

  • Korean

  • Polish

  • Portuguese

  • Russian

  • Spanish

  • Swedish

  • Turkish

This means that all screen labels, error messages, and menu options are supported out of the box in these languages and users are able to select from these languages as their preferred language. Data translation is also supported to allow data that you create as part of your implementation, such as HTS codes and chapters, can be seen in the preferred languages of your users as well.

Translate Retailer Data

When creating data in Trade Management it is assumed that data is always entered initially in the primary language for the main entity. But, you can also enter translations for the data, as needed, by selecting the translation iconic button (translation icon). See the Oracle Retail Import Management Do the Basics User Guide section on translation for details on how to add translations for your data via the user interface. Most of the data that may require translation for Trade Management is managed via spreadsheet download/upload. For these entities, translations can be provided via the upload.

Translate Labels and Seeded Data

If you would like to modify the translations for labels, error messages, codes and descriptions, or other seeded data, or to add translations for other languagesFoot 1 that are not included in the list above, there are several methods provided. The method used will depend on the data that needs to be updated/added. Translatable text is held in two different ways for Trade Management, resource bundles and database tables.

Resource Bundles

Screen labels and other UI related data that may require updates/additions for Trade Management are managed in resource bundles. For details on how to make updates to resource bundles see the Resource Bundles section in the Oracle Retail Merchandising Customization and Extension Guide.

Database Tables

Many other labels and drop-downs that are not managed in resource bundles are managed in the Codes and Descriptions spreadsheet download/upload process in Merchandising for the code types describe in this document. You can use the method described for managing codes in the Oracle Retail Merchandising Implementation Guide to update or add your translations in the designated tab in the spreadsheet.

Error messages and other foundational data entities are also managed via spreadsheet download and upload. For each of these entities, where applicable, translations can also be added in the spreadsheet in a separate tab, using the entity ID as a cross reference. The details on the translation for these entities is found with the information on managing these entities in either the user guides or in this document.

For the base strings in English for these tables, see My Oracle Support ID 1608569.1 and select the Merchandising document (rms_translation_pairs.xls), which also include Trade Management. These can be used as a basis for adding your own translations.

Configure User Language

Users can choose their preferred language to have the user interface displayed as part of setting up their user preferences, as described in the Import Management Do the Basics User Guide. As noted above, the values loaded in the base table of an entity are always maintained in the primary language. And as such all users, irrespective of their configured language, will see the primary language in the screens where an entity is created and maintained, and translations (including their preferred language) are shown in separate translation screens. However, if that same screen is accessed in view mode the description will be shown in their preferred language. Similarly, if viewing the entity in another UI - for example, viewing the freight types in the Transportation screen - the description will be shown in their preferred language.

Not Translated

The following information is available in English only:

  • Documentation, including online help, release notes, and product guides

  • Batch programs and messages

  • Log files

  • Configuration tools

  • Demonstration data

  • Training Materials


Footnote Legend

Footnote 1:

Additional support is also available for the following languages by adding your own translations using the tools described in this section for adding your own translations: Czech, Danish, Finnish, Hebrew, Norwegian, Thai, Albanian, Latin Bosnian, Bulgarian, Estonian, Latvian, Cyrillic Serbian, Lithuanian, Romanian, Slovakian, and Slovenian.