Globalization

Translation

Merchandising supports operating the user interface in 19 languages, including English. As part of the install options, you'll designate one language as "primary". This primary language is 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^Foot 1. The primary language is also what is loaded as a default for all screen labels, error messages, and seeded data in Merchandising at the time of installation. By default, only the primary language you indicated at installation is loaded in Merchandising, 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 for Merchandising 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 store names, item descriptions, and hierarchy names, can be seen in the preferred languages of your users as well.

Translate Retailer Data

When creating data in Merchandising, such as a new item, it is assumed that data is always entered initially in the primary language in the main entity screen. But, you can also enter translations for the data, as needed, by selecting the translation iconic button (). See the "Transl ate Data" chapter in the Oracle Retail Merchandising Do the Basics User Guide for details on how to add translations for your data via the user interface. Additionally, for items that are uploaded via spreadsheet, 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 add translations for other languages^Foot 2 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:

Resource bundles, which contain most of the screen labels, menus, and messages
Database tables, which contain strings used in drop-downs, some labels, error messages, and are used to hold the data level translations for both the seeded data as well as your data

Resource Bundles

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

Database Tables

Most other labels and drop-downs that are not managed in resource bundles are managed in the "Codes and Descriptions" spreadsheet download/upload process. You can use the method described for managing that data to update or add your translations in the designated tab in the spreadsheet.

Error messages and other seeded data entities are also managed via spreadsheet download and upload. For each of these entities, 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. These include:

Computational Value Bases
Cost Change Reasons
Cost Components
Countries
Currencies
Deal Component Types
Error Messages
Inventory Adjustment Reasons, Codes, and Types
Languages
Non-Merchandise Codes
States
Tender Types
Units of Measure
VAT Codes

In a cloud service implementation of Merchandising, there will be some entities where the tables holding the descriptions are not accessible via the UI or spreadsheet download/upload. For these entities, if you require additional translations to be added, you will need to log an SR to have the Oracle Cloud Operations team assist you in a cloud services implementation. The following data entities are impacted:

Address Types
Cost Event Run Types
Mass Change Rejection Reasons
Order Types
Tran Data Codes and References

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). 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 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 item description in the purchase order details 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

Manage Languages

Within Merchandising, languages are used to define and display translations of text. A default list of languages is loaded into Merchandising on initial installation, however modifications can be done to the list to add new values, remove values that are not used, and update descriptions. These updates can be made through spreadsheet download and upload processes, which are accessed through the main Merchandising task list under Foundation Data > Download Foundation Data and Foundation Data > Upload Foundation Data.

To add or update languages, you will select the template type of Administration from the Download Data screen and then the template Languages. Click the Download button and when prompted, choose to either open the .ods file that is generated or save the file and open it separately in the spreadsheet application of your choice. Once opened, there will be two sheets that can be modified - Languages and Language Translations.

Add a Language

To add a new language, start in the Languages tab, and, in a blank line in the template, select the action type of Create. Next enter a unique language identifier (up to 6 digits), and then enter the description for the language in the primary language (as defined in the Merchandising system options) of up to 120 characters. Finally, enter the internationally recognized ISO Code for the language which is published by the International Organization for Standardization (ISO). Note: the Web Help Server, Report Server, and Web Report Server can be entered, but they are no longer used by Merchandising.

If you wish to add translations for the language in languages other than the primary language, this can be done in the Language Translations tab. Navigate to a blank row and select the action type of Create and the language in which the translated description will be entered. Then, enter the language for which the translation applies. Finally, enter the translated description. The translated description can also be up to 120 characters long. This is an optional step.

Update Languages

If you would like to update any details for existing languages, a similar process will be followed as that described above for creating new languages. First, download the spreadsheet, and then navigate to the tab where you would like to make your updates.

The following columns can be updated in each tab:

Languages - Description, Web Help Server, Report Server, Web Report Server, ISO Code
Language Translations - Description

In the tab where you are going to make your updates, select the action type of Update, and then correct the value in the spreadsheet.

Uploading Changes

For all actions defined above, once all the updates have been made to the data in the spreadsheet, save the file and close it. Then, return to the Merchandising screens and select Foundation Data > Upload Foundation Data from the main task list. In this screen, select the template type Administration and the template Languages. This will generate a process description automatically, but this can be updated if desired. Lastly, select the Browse button and navigate to the directory where you saved the updated spreadsheet.

To review the status of the upload and check whether any errors occurred, select the Foundation Data > Review Status task from the main task list.

For more information, see "Download/Upload Data from Spreadsheets" in the Oracle Retail Merchandising Do the Basics User Guide.

Manage Currencies

Within Merchandising, currencies and rates are maintained to support conversions between different currencies where there is need for multi-currency operations. Updates to currencies can be made through spreadsheet download and upload processes. These processes are accessed through the main Merchandising task list under Foundation Data > Download Foundation Data and Foundation Data > Upload Foundation Data.

To add or update currencies, you will select the template type of Finance Administration from the Download Data screen and then the template Currencies. Click the Download button and when prompted, choose to either open the .ods file that is generated or save the file and open it separately in the spreadsheet application of your choice. Once opened, there will be three sheets that can be modified - Currencies, Currency Translations, and Current Exchange Rates.

Add a Currency

To add a new currency, start in the Currencies tab, and, in a blank line in the template, select the action type of Create. Next enter a unique currency code (should be a 3-character code), and then enter the description for the currency in the primary language (as defined in the Merchandising system options) of up to 120 characters. Next, the Currency Cost Format and Currency Retail Format must be entered. These columns contain the display format mask for cost and retail values displayed in the application screens for this currency. Finally, enter Currency Cost Decimal and Currency Retail Decimal values to indicate how many decimal values should be displayed in the application screens for this currency. The decimal values also determine what precision cost and retail values should be stored at in the stock ledger.

If you wish to add translations for the currency in languages other than the primary language, this can be done in the Currency Translations tab. Navigate to a blank row and select the action type of Create and the language in which the translated description will be entered. Then, enter the currency code for which the translation applies. Finally, enter the translated description. The translated description can also be up to 120 characters long. This is an optional step.

Finally, exchange rate details must be defined. Navigate to a blank row in the Currency Exchange Rates tab and select the action type of Create. Enter the from and to currency codes and a date the rate is effective from, using the DD-MON-YYYY format. Select an Exchange Type value and enter an Exchange Rate. While currency rates are normally maintained by the financial system and interfaced into Merchandising this capability to maintain them manually also exists.

Note that different rates may be defined by Exchange Type but at a minimum a rate must be defined for either the Consolidation or Operational types, as determined by the system parameter for "Consolidated Exchange Rate". If the Consolidated Exchange Rate is being used, then an exchange rate must be defined for the Consolidated exchange type, otherwise an Operational rate must be defined.

Update Currencies

If you would like to update any details for existing currencies, a similar process will be followed as that described above for creating new currencies. First, download the spreadsheet, and then navigate to the tab where you would like to make your updates.

The following columns can be updated in each tab:

Currencies - Currency Description, Currency Cost Format, Currency Retail Format, Currency Cost Decimal, and Currency Retail Decimal
Currency Translations - Currency Description
Currency Exchange Rates - no updates are allowed on this tab. To update the exchange rate for a currency code a new row must be added with a future effective date.

In the tab where you are going to make your updates, select the action type of Update, and then correct the value in the spreadsheet.

Delete a Currency

Existing currency codes, translations, and rates can all be deleted by selecting the action type Delete in the row you wish to delete. However, a currency code cannot be deleted if it is referenced elsewhere in Merchandising, such as on a Purchase Order.

Upload Changes

For all actions defined above, once all the updates have been made to the data in the spreadsheet, save the file and close it. Then, return to the Merchandising screens and select Foundation Data > Upload Foundation Data from the main task list. In this screen, select the template type Finance Administration and the template Currencies. This will generate a process description automatically, but this can be updated if desired. Lastly, select the Browse button and navigate to the directory where you saved the updated spreadsheet.

To review the status of the upload and check whether any errors occurred, select the Foundation Data > Review Status task from the main task list.

For more information, see "Download/Upload Data from Spreadsheets" in the Oracle Retail Merchandising Do the Basics User Guide.

Manage Entity Exchange Rate Configuration

Merchandising and Trade Management provide the option to configure which date to use when determining the exchange rate to use for certain transactions. This configuration also allows you to determine whether or not the entities exchange rate should be used or ignored. For example, if an exchange rate is entered on a purchase order, you can determine if that rate should be used or the one in the currency exchange rate table based on the date configuration. This table is seeded initially, but can be updated as needed to support your business. The following entities support configuring the date to use for currency exchange rates:

Table 5-1 Manage Entity Exchange Rate Configuration Options

Entity	Exchange Rate Date Options
Merchandising
Order Cost	Transaction Date*, Original Order Approval Date
Order Expenses	Transaction Date*, Original Order Approval Date
Trade Management
Order Assessments	Transaction Date*, Original Order Approval Date
Transportation	Commercial Invoice Date*, Finalized Date
Customs Entry	Entry Date*, Confirmed Date
Letter of Credit	Application Date*, Confirmed Date
Obligations	Obligation Approval Date, Invoice Date*, Paid Date

* Initial system default

The configuration for this function is accessed through the main Merchandising task list under Foundation Data > Download Foundation Data and Foundation Data > Upload Foundation Data. To update the configuration, you will select the template type of Finance Administration from the Download Data screen and then the template Entity Exchange Rate Configuration. Click the Download button and when prompted, choose to either open the .ods file that is generated or save the file and open it separately in the spreadsheet application of your choice. Once opened, there will be one sheet that can be modified - Entity Exchange Rate Config.

Update Entity Exchange Rate Configuration

If you would like to update the exchange rate date used for any of the above entities, download the spreadsheet, and then navigate to the row where you would like to make your updates and choose the action type of Update.

The following columns in the worksheet can be updated:

Ignore Entity Exchange Rate - this can be set to Yes or No, depending on whether you want to use the exchange rate on the entity or use one in the exchange rate table based on the date configuration. The default for all entity options is No.
Exchange Rate Date - indicate the date you want used for an entity. Valid values are based on the table above.

Uploading Changes

For all actions defined above, once all the updates have been made to the data in the spreadsheet, save the file and close it. Then, return to the Merchandising screens and select Foundation Data > Upload Foundation Data from the main task list. In this screen, select the template type Finance Administration and the template Entity Exchange Rate Configuration. This will generate a process description automatically, but this can be updated if desired. Lastly, select the Browse button and navigate to the directory where you saved the updated spreadsheet.

To review the status of the upload and check whether any errors occurred, select the Foundation Data > Review Status task from the main task list.

See also Download/Upload Data from Spreadsheets in the Oracle Retail Merchandising Do the Basics User Guide.

Currency Cross Reference

Currency Exchange Type mappings exist as a cross reference between the Merchandising currency types and those maintained in an external financial system, if they differ. This cross reference is used when importing current exchange rates from the financial system, where the financial system may maintain a different exchange type than is used in Merchandising. Updates to these mappings can be made through spreadsheet download and upload processes. These processes are accessed through the main Merchandising task list under Foundation Data > Download Foundation Data and Foundation Data > Upload Foundation Data.

To update currencies exchange type mappings, you will select the template type of Finance Administration from the Download Data screen and then the template Currency Exchange Type Mappings. Click the Download button and when prompted, choose to either open the .ods file that is generated or save the file and open it separately in the spreadsheet application of your choice. Once opened, there will be one sheet that can be modified - Currency Exchange Type Mapping.

Update a Mapping

Currency exchange type mappings can only be updated. It is not permitted to add new or delete existing rows. To update existing mappings, first download the spreadsheet. In the Currency Exchange Type Mapping sheet all existing cross reference values will be displayed. To update an existing record, select the action type of Update for the row being updated. Both the External Exchange Types and RMS Exchange Types columns may be updated but both are required.

Uploading Changes

For all actions defined above, once all the updates have been made to the data in the spreadsheet, save the file and close it. Then, return to the Merchandising screens and select Foundation Data > Upload Foundation Data from the main task list. In this screen, select the template type Finance Administration and the template Currency Exchange Type Mappings. This will generate a process description automatically, but this can be updated if desired. Lastly, select the Browse button and navigate to the directory where you saved the updated spreadsheet.

To review the status of the upload and check whether any errors occurred, select the Foundation Data > Review Status task from the main task list.

For more information, see "Download/Upload Data from Spreadsheets" in the Oracle Retail Merchandising Do the Basics User Guide.

Manage VAT Codes/Rates

As part of the base installation, the data below will be seeded into the VAT tables in Merchandising if you are configured to run in Simple VAT mode or Global Tax (see "Install Options"). One VAT region will be added (1000 - VAT Region 1000), which will be assigned as the default VAT region. Four VAT codes will also be created with one rate record added using the date of the install as the active date as shown below. Before you add hierarchies, suppliers, locations, or items, you'll want to refine this data based on your tax requirements. For more details on how to do this configuration of regions, codes, and rates, see the Oracle Retail Merchandising Finance User Guide section for Manage Financial Administration Data.

VAT Code	Description	Rates
S	Standard	10.00
E	Exempt
C	Composite
Z	Zero

For more information on Global Tax and its use of tax codes, see the Merchandising Global Tax Overview white paper.