Go to primary content
Oracle® Retail Warehouse Management System Implementation Guide
Release 15.0
E68108-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

9 Internationalization

Internationalization is the process of creating software that can be translated more easily. Changes to the code are not specific to any particular market. This chapter describes configuration settings and features of the software that ensure that the base application can handle multiple languages.

Oracle Retail applications have been internationalized to support multiple languages.

RWMS supports and displays languages other than English, but does not have the full capability of supporting multi-byte languages. RWMS is dependent on RF devices that have limitations on the amount of data that can be displayed.

Translation

Translation is the process of interpreting and adapting text from one language into another. Although the code itself is not translated, components of the application that are translated include the following:

  • Graphical user interface (GUI)

  • Error messages

  • Reports

The following components are not translated:

  • Documentation (online help, release notes, installation guide, user guide, operations guide)

  • Batch programs and messages

  • Log files

  • Configuration tools

  • Demonstration data

  • Training materials

The user interface has been translated into the following languages:

Table 9-1 Languages and Language Codes

Language Language Code

American English

en

Chinese (Simplified)

zh

Chinese (Traditional)

zh_TW

Croatian

hr

Dutch

nl

French

fr

German

de

Greek

el

Hungarian

hu

Italian

it

Japanese

ja

Korean

ko

Polish

pl

Portuguese (Brazilian)

pt

Russian

ru

Spanish

es

Swedish

sv

Turkish

tr


RWMS Enhanced Navigation application uses two translation mechanisms:

  • For the embedded oracle forms, translation of the boiler texts is achieved through database tables as described in detail in the following section.

  • For the ADF web application, translation is achieved through J2EE techniques, i.e., translatable language property files. The localization files have a base name called uiresources_xx where xx represents the user language code.

    • The localization files are placed in the build project under rwms web application source code.

    • Translation of the login page is achieved through a configurable property default_locale which is set by the customer in the application.properties file placed in the server classpath.

    • Each web page (.jspx file) will contain a <f:view> tag which will have the locale for the entire page. All page fragments which get loaded at runtime will use the same locale for translation.

    • During application login, the authenticated user's language code is fetched from the DMS_USER table and is set at the ADF context. The base name of the resource bundle also gets set at the ADF context and is used for picking up the correct language bundle file.

    • To add a new supported language, a new entry has to be added to the SUPPORTED_LANGUAGE table. Translated texts for the menu and the boiler texts for forms need to be added to DMS_LANGUAGE_MENU, TRANSLATOR, USER_LANGUAGE_MESSAGE and CODE_TRANSLATOR tables. A new entry for the language code needs to be made in the faces-config.xml file under <supported_locales> tag and the translated language property file needs to be added to the build project under rwms webapp. The application ear file needs to be redeployed in order to bring the new locale into effect. Once this is done, a new application user can be created with the newly created locale to verify the translation.

BI Publisher Reports Translation

  • When displayed/printed from RWMS Application, all the label reports are translated using the language in System Control Parameter default_language. Label reports do not have language specific XLF files.

  • When displayed/printed from RWMS Application, all other reports are translated using the language in System Control Parameter print_locale_bi. For these reports the language specific XLF files need to be uploaded for each report.

  • User can log into BI Publisher and directly view the report. In this case the locale of the BI User is used for translation except for Label reports which will always use the language in System Control Parameter default_language.

Uploading XLF files in BI Publisher

Perform the following steps to upload a XLF file:

  1. Login to BI Publisher Application.

    Figure 9-1 Login

    Surrounding text describes Figure 9-1 .
  2. Select a report in RWMS System Repository or RWMS Repository. All the reports in RWMS Repository can be viewed using only BI Publisher.

    Figure 9-2 Select Report

    Surrounding text describes Figure 9-2 .
  3. Click Edit link.

    Figure 9-3 Edit

    Surrounding text describes Figure 9-3 .
  4. Click Properties link.

    Figure 9-4 Properties

    Surrounding text describes Figure 9-4 .
  5. If no Templates are available, then click Upload button under Templates.

    Figure 9-5 Upload

    Surrounding text describes Figure 9-5 .
  6. Select the default RTF file. For example, for asn_receiving_receipt_sys report, the default RTF file is asn_receiving_receipt_sys.rtf. Select Locale as English. Click OK.

    Figure 9-6 Select Default RTF

    Surrounding text describes Figure 9-6 .
  7. Click Upload button under Translations.

  8. Select the Locale and the XLF file and click OK.

    The last two characters in the XLF file name denote the language. Below de stands for German.

    Figure 9-7 Select Locale

    Surrounding text describes Figure 9-7 .

RWMS Tables

RWMS stores translated text for each installed language in four main tables shown in Table 9-2.

Table 9-2 Internationalization Tables

Table Description

SUPPORTED_LANGUAGE

Contains the list of supported languages

DMS_LANGUAGE_MENU

Contains the strings for the menus

TRANSLATOR

Contains the strings for the forms

USER_LANGUAGE_MESSAGE

Contains the strings for the messages and alert

CODE_TRANSLATOR

Contains the strings for translating codes and reports


Table 9-3 describes the DMS_LANGUAGE_MENU table. Table 9-4 shows an example of the DMS_LANGUAGE_MENU table.

Table 9-3 DMS_LANGUAGE_MENU Table

Column Name Description

FACILITY_ID

A unique identifier for an operating facility

MENU_NAME

Name of the parent menu that the option is on

OPTION_TITLE

Title of the option (as seen as on the menu)

LANGUAGE_CODE

Used to separate code descriptions and extended descriptions from each other based on language

OPTION_TEXT

Text of the option


Table 9-4 Example of DMS_LANGUAGE_MENU Table

FACILITY_ID MENU_NAME OPTION_TITLE LANGUAGE_CODE OPTION_TEXT

PR

ITEM_SETUP_MENU

Transport Asset Editor

en (American English)

Transport Asset Editor

PR

ITEM_SETUP_MENU

Transport Asset Editor

fr (French)

Editeur transport élément d'actif

PR

DISTRIBUTION_MENU

Order Query Editor

en

Order Query Editor

PR

DISTRIBUTION_MENU

Order Query Editor

fr

Editeur demande commande


Table 9-5 describes the TRANSLATOR table. Table 9-6 shows an example of the TRANSLATOR table.

Table 9-5 TRANSLATOR Table

Column Name Description

FACILITY_ID

A unique identifier for an operating facility

LANGUAGE_CODE

Used to separate code descriptions and extended descriptions from each other based on language

DATA_BASE_VALUE

Indicates the database value for a field to be translated

DISPLAY_VALUE

Indicates the value that is displayed


Table 9-6 Example of TRANSLATOR Table

FACILITY_ID LANGUAGE_CODE DATA_BASE_VALUE DISPLAY_VALUE

PR

en (American English)

APPROVE

Approve

PR

fr (French)

APPROVE

Approuver

PR

en

PRODUCT

Product

PR

fr

PRODUCT

Produit


Table 9-7 describes the USER_LANGUAGE_MESSAGE table. Table 9-8 shows an example of the USER_LANGUAGE_MESSAGE table.

Table 9-7 USER_LANGUAGE_MESSAGE Table

Column Name Description

FACILITY_ID

A unique identifier for an operating facility

LANGUAGE_CODE

Used to separate code descriptions and extended descriptions from each other based on language

MESSAGE_CODE

A code that uniquely identifies a user message

MESSAGE_TEXT

An explanation of the user message (related to MESSAGE_CODE) which is used as the on-screen prompt for the message


Table 9-8 Example of USER_LANGUAGE_MESSAGE Table

FACILITY_ID LANGUAGE_CODE MESSAGE_CODE MESSAGE_TEXT

PR

en (American English)

ITEM_NOT_AVAIL

Required item not available.

PR

fr (French)

ITEM_NOT_AVAIL

Article requis non disponible.

PR

en

DUP_WAVE_ITEM

Item already exists from a different wave.

PR

fr

DUP_WAVE_ITEM

Article existe déjà pour une rafale différente.


Table 9-9 describes the CODE_TRANSLATOR table. Table 9-10 shows an example of the CODE_TRANSLATOR table.

Table 9-9 CODE_TRANSLATOR Table

Column Name Description

FACILITY_ID

A unique identifier for an operating facility

CODE_TYPE

Used to determine what type of code it is and provide a way to distinguish what translation value has to be acquired when the codes are the same

CODE

What the application uses in its background processing

LANGUAGE_CODE

Used to separate code descriptions and extended descriptions from each other based on language

CODE_DESCRIPTION

A translated version of what the code is; used to display a short meaningful description of what it is to the users

EXTENDED_DESCRIPTION

A translated version of what the code is in more detail

CODE_SEQ

Provides a mechanism in which managers can reorder the lists that the codes are displayed in


Table 9-10 Example of CODE_TRANSLATOR Table

FACILITY_ID CODE_TYPE CODE LANGUAGE_CODE CODE_DESCRIPTION EXTENDED_DESCRIPTION CODE_SEQ

PR

ATTRIBUTES

CONFIRM_LOCATION

en (American English)

CONFIRM LOCATION

Validate Location

8

PR

ATTRIBUTES

CONFIRM_LOCATION

fr (French)

CONFIRMER SITE

Validation site

8

PR

ATTRIBUTES

LOT_NBR

en

LOT NBR

Lot Number

16

PR

ATTRIBUTES

LOT_NBR

fr

N° LOT

N° du lot

16