Regional Settings

Regionalization is the process of creating software that is able to be translated more easily. Changes to the code are not specific to any particular market. Order Management System supports multiple decimal and thousand separators as well as multiple date formats.

This topic describes the configuration settings and features of the software that ensure that the base application can handle regionalization.

In this chapter:

• Defining Localization Defaults During Installation

• Setting the Default Locale

• Setting the Default Date Format

• Setting the Default Decimal and Thousand Separator Formats

• Reports and Forms Generated through Oracle BI Publisher

• BI Publisher Date and Separator Formats

For more information: See:

• Multi Currency by Offer (E03) for more information on how to configure the system to take orders in more than one currency.

• Using Alternate Currency Pricing for more information on how to configure the system to price offers in a foreign currency.

Recommended Screen Size

In order to align screens correctly, the default size of the application window has been adjusted to 800 x 1200. Displaying the application in this window size is recommended for most screens except the Streamlined Order Inquiry (DORI) menu option.

Defining Localization Defaults During Installation

During installation, the system:

• Sets the base locale for the application. See Setting the Default Locale for more information.

• Prompts for the default date format for the application. See Setting the Default Date Format for more information.

• Prompts for the base decimal separator and thousand separator for numeric fields in the application, such as price and weight. See Setting the Default Decimal and Thousand Separator Formats for more information.

• Assigns the default locale and default date format to the admin user created during installation.

You can reset or override these defaults, as described below.

Setting the Default Locale

During installation, the system:

• Stores the default locale in the DEFAULT_LOCALE property. When you create a new user or company, the system assigns the default locale to the user or company by default.

• Defaults this locale to the Locale field in the Company table for the companies delivered with Order Management System.

• Defaults this locale to the admin user that is created during installation.

Overriding the default locale: You can change the locale for users through Work with Users (WUSR), and you can change the locale for companies through Work with Companies (WCMP).

You can change the DEFAULT_LOCALE property through Work with Properties (PROP).

Where are Locale Settings Applied?

Company locale: The locale specified for the company controls the language on generated reports and emails.

The company locale also controls the date and number formats available for use on reports generated through BI Publisher. See BI Publisher Date and Separator Formats.

User locale: The locale specified for the user controls the language for screen titles, field names, messages on screens (such as confirmation that a record has changed), and the labels of options available on screens.

The locale does not control:

• The content of data fields, such as customer or vendor name or address

• The descriptions of items and other data

• The descriptions of menu options or of periodic functions or processes, although you can populate this seed data to your chosen locale at initial installation; contact your Oracle representative for more information

• The contents of the online help or other documentation

• The descriptions of menus

Supported Locales

Order Management System supports the following locales for companies and users:

• English

• French

• German

• Italian

• Spanish

When the locale is changed for a user, it is necessary for the user to log off and then log back in in order for the locale change to take effect.

Additional Localized Content

The following content can also be set to the language of the selected locale:

• System Control Value names (Description field)

• Secured Feature names (Description field)

• Menu names (Description field; system-delivered menus only)

• Menu Option names (Description field)

• Match Code field names

• Integration Layer Process names (Description field)

• Order Hold Reason descriptions

• Periodic Function titles (Description field; system-delivered functions only)

• Asynchronous Job Control titles (Description field)

• Inventory Transaction Code titles (Description field)

• Application Area names (Description field)

• Application Group Descriptions

• Tickler Event names (Description field)

• Order Line Activity names (Description field)

Note: Updating this content will overwrite any custom entries, such as the names of periodic functions or order hold reason code descriptions.

Contact your Oracle representative for information on how to localize this content after initial installation.

Setting the Default Date Format

During installation, the system prompts for the default date format of Order Management System. The system:

• Stores the default date format in the DEFAULT_DATE_FORMAT property. When you create a new user or company, this date format defaults.

• Defaults this date format to the Date format field in the Company table for the companies delivered with Order Management System.

• Defaults this date format to the admin user that is created during installation.

Note: Regardless of the date format displayed on screens and reports, dates are stored in the database in CYYMMDD format.

Overriding the default date format: You can change the date format for users through Work with Users (WUSR), and you can change the date format for companies through Work with Companies (WCMP).

You can change the DEFAULT_DATE_FORMAT property through Work with Properties (PROP).

Where are Date Formats Applied?

Date Formats on Reports, Forms, and Emails

Company date format: Emails, reports and forms that are not generated using Oracle Business Intelligence Publisher (BI Publisher), display the date in the date format defined for the company.

Note: Reports that are not associated with a company display the date in the format from DEFAULT_DATE_FORMAT property.

Oracle BI Publisher Date Formats

Reports that are generated using Oracle BI Publisher do not use the Date Format defined for the company; instead, they use the format defined in BI Date and Separator Format for the current company where the report is generated. See Reports and Forms Generated through Oracle BI Publisher and BI Publisher Date and Separator Formats for more information.

Date Formats on Screens

User date format: Unless as noted below, dates displayed on screens are in the date format defined for the user. This includes the dates on the Open, Held Order Recap Dollars pie charts and Order Statistics.

Note: When manually entering a date on a screen, such as in a scan field, certain screens in the application require you to include forward slashes in the date. For example, if the Date Format defined for your user ID is MMDDYY, you need to manually enter the date as MM/DD/YY on the screen, such as 12/25/16 and not 122516. If you do not include the forward slashes, the system displays an error message indicating the valid date format and that slashes are required.

Company date format: The expected ship date included in the backorder card message on the Display Order History screen, indicating when a backorder card was generated for the order, is in the format defined for the company, so that the date format in the message matches the date format included on the backorder card/email.

Date Entries in System Control Values

User date format: Date entries in system control values, such as the Tax Inclusive Cutoff Date (E79), are in the date format defined for the user.

Date Format for User-Entered Dates

When a user enters a date in a message or text field, such as an order message or tickler note, the system stores and displays the date in the format it was entered. It is treated as text.

Date Formats in APIs

Dates in APIs do not use the format defined for the user or company. See each specific XML message in XML Messages for more information on the date format for each message.

Date Formats in Uploads

Dates in uploads do not use the format defined for the user or company. See each specific upload in Work with File Uploads (WUPL) for more information on the date format for each upload.

Calendar Widget

When you select a date from the calendar widget, the date is in the format defined for the user.

Setting the Default Decimal and Thousand Separator Formats

During installation, the system prompts for the following values to determine the default decimal and thousand separator of Order Management System.

• Default decimal separator: The character format used to indicate the decimal place in a number. The system stores the default decimal separator in the DECIMAL_SEPARATOR property. This property is used for any numeric field that contains a decimal, such as price, cost, and weight.

• Default thousand separator: The character format used to separate groups of thousands. The system stores the default thousand separator in the THOUSAND_SEPARATOR property. This property is primarily used on reports and is not entered by a user.

You cannot override these properties at the company or user level.

Note: The above properties do not apply to reports generated through BI Publisher, as these reports use the BI Date and Separator Format defined for the company. See Reports and Forms Generated through Oracle BI Publisher and BI Publisher Date and Separator Formats for more information.

Supported Thousand and Decimal Separator Formats

Possible settings for the DECIMAL_SEPARATOR and THOUSAND_SEPARATOR properties are listed below.

Default Thousand Separator	Default Decimal Separator	Results
, (comma)	. (period)	4,294,967,295.00
. (period)	, (comma)	4.294.967.295,00

Where are Number Format Applied?

Number Format on Home Screen

Default number format: The Home screen displays numbers using the characters defined in the DECIMAL_SEPARATOR and THOUSAND_SEPARATOR properties.

Number Format in Menu Options

Default number format: Screens in menu options display numbers using the characters defined in the DECIMAL_SEPARATOR and THOUSAND_SEPARATOR properties.

Number Format on My Jobs, My Docs, My Forms

Default number format: The Job Management (My Jobs), Document Management (My Docs), and Forms Management (My Forms) screens display numbers using the characters defined in the DECIMAL_SEPARATOR and THOUSAND_SEPARATOR properties.

Number Format of User Entered Numbers

Default number format: When a user enters a number, the correct decimal separator must be used and the thousand separator should not be entered since it is implied.

Example: To enter the number one thousand eleven and fifty cents:

• if the default decimal separator is . (period), enter 1011.50

• if the default decimal separator is , (comma), enter 1011,50

Number Format on Reports, Forms, and Emails

Default number format: Emails, reports and forms that are not generated using Oracle BI Publisher display numbers using the characters defined in the DECIMAL_SEPARATOR and THOUSAND_SEPARATOR properties.

Oracle BI Publisher format: Reports and forms generated using Oracle BI Publisher use the number format defined in Oracle BI Publisher for the locale in the Company table.

Number Format in APIs

Numbers in APIs do not use the characters defined in the DECIMAL_SEPARATOR and THOUSAND_SEPARATOR properties. See each specific XML message in XML Messages for more information on the number format used in each message.

Number Format in Uploads

Numbers in uploads do not use the characters defined in the DECIMAL_SEPARATOR and THOUSAND_SEPARATOR properties. See each specific upload in Work with File Uploads (WUPL) for more information on the number format used for each upload.

Reports and Forms Generated through Oracle BI Publisher

The following reports are generated through Oracle BI Publisher, and use the BI Publisher Date and Separator Formats:

• Backorder Card Notification (GBOC)

• Campaign Performance Report (PCPR)

• Carryover Report (PCOR)

• Cart Batch Recap Report (WSPS)

• Cart Bin Picking Report (WSPS)

• Deposit History Detail (PDHD)

• Exchange Reason Report (PERR)

• Gift Acknowledgement in graphical format (WSPS, MDSP)

• Held Order by Reason Code Reports (PHOR)

• Order Broker Aging Report (WOBR)

• Order Receipt (OIOM, DORI)

• Order Type Summary by Delivery Report (PDTS)

• Password Change Report (PUSA)

• Pick Authorization Error Report (WSPS)

• Pick Slip in graphical format (WSPS, MDSP)

• Pick Unit Report (WSPS)

• Picking Pullsheet (WSPS)

• Price Code Upload Errors Report (PCUPLD periodic function)

• Price Override Reason Reports (PROR)

• Product Performance Reports (PPPR)

• Promotion Analysis Report (POPA)

• Promotion Upload Error Records Report (WPRO)

• Purchase Order in graphical format (MDSP, MPOE, MPRP)

• Purged Order List (PURGEOR periodic function)

• Refund Check (MREF)

• Reset Audit Log for Quantity On B/O (MRBO)

• Return Reason Report (PRRR)

• Sales Journal (PROR)

• Soldout Notification (MSON)

• Standard Pick Label (PAPL, WPPV)

• Tax Jurisdiction Report (PTJX)

• User Authority Change Reports (PUSA)

BI Publisher Date and Separator Formats

The date and separator formats available for selection for a company are listed below. The possible date and separator formats are restricted based on the selected locales.

See Setting Up Companies (WCMP) for more information.

See Reports and Forms Generated through Oracle BI Publisher, above, for a listing of reports that use these formats.

Date and time formats for the following languages are supported in BI Publisher reports:

• French

• English

• German

• Italian

• Spanish

French
Format	Date	Decimal Separator	Thousand Separator	Sample Date	Sample Number	Sample Large Number
Belgium	dd-mm-yyyy	comma	space	3/7/2018 8:06	141.420,08	2.983.583,25
Canada	yyyy-mm-dd	comma	space	18-03-07 08:12:08	141 420,08	3 006 139,99
France	dd/mm/yyy	comma	space	07/03/18 14:22 PM	121,25	3 006 139,99
Luxembourg	dd/mm/yy	comma	space	7/3/2018 14:24	121,25	3 006 139,99
Switzerland	dd.mm.yy	period	Apostrophe	07.03.18 14:26	121.25	3'006'139.99

English
Format	Date	Decimal Separator	Thousand Separator	Sample Date	Sample Number	Sample Large Number
Australia	dd-mm-yyyy	dot	comma	15-04-2018 00:44:42	256.53	2,983,583.25
Canada	dd/mm/yy	dot	comma	15/04/18 00:44:42	256.53	2,983,583.25
India	dd/mm/yy	dot	comma	4/15/2018 0:37	256.53	2,983,583.25
Ireland	dd/mm/yy	dot	comma	15/04/18 00:39:26	256.53	2,983,583.25
New Zealand	dd/mm/yy	dot	comma	15/04/18 00:41:55	256.53	2,983,583.25
South Africa	yy/mm/dd	dot	comma	18/04/15 00:42:54	256.53	2,983,583.25
UK	dd/mm/yy	dot	comma	15/04/18 00:44:42	256.53	2,983,583.25
US	mm/dd/yy	dot	comma	4/15/2018 0:45	256.53	2,983,583.25

German
Format	Date	Decimal Separator	Thousand Separator	Sample Date	Sample Number	Sample Large Number
Austria	dd.mm.yyyy	comma	dot	15.04.18 00:48:45	256,53	2.983.583,25
Germany	dd.mm.yy	comma	dot	15.04.18 00:50:08	256,53	2.983.583,25
Luxembourg	dd.mm.yy	comma	dot	15.04.18 00:51:38	256,53	2.983.583,25
Switzerland	dd.mm.yy	dot	Apostrophe	15.04.18 00:52:44	256.53	2'983'583.25

Italian
Format	Date	Decimal Separator	Thousand Separator	Sample Date	Sample Number	Sample Large Number
Italy	dd/mm/yy	comma	dot	15/04/18 00:54:54	256,53	2.983.583,25
Switzerland	dd.mm.yy	dot	Apostrophe	15.04.18 00:56:06	256.53	2'983'583.25

Spanish
Format	Date	Decimal Separator	Thousand Separator	Sample Date	Sample Number	Sample Large Number
Argentina	dd/mm/yy	comma	dot	15/04/18 01:00:20	256,53	2.983.583,25
Bolivia	dd-mm-yy	comma	dot	15-04-18 01:02:01	256,53	2.983.583,25
Chile	dd-mm-yy	comma	dot	15-04-18 01:03:13	256,53	2.983.583,25
Colombia	dd/mm/yy	comma	dot	15/04/18 01:04:16	256,53	2.983.583,25
Costa Rica	dd/mm/yy	comma	dot	15/04/18 01:05:30	256.53	2,983,583.25
Dominican Republic	mm/dd/yy	dot	comma	4/15/2018 1:06	256.53	2,983,583.25
Ecuador	dd/mm/yy	comma	dot	15/04/18 01:08:07	256,53	2.983.583,25
El Salvador	mm-dd-yy	dot	comma	04-15-18 01:16:33	256.53	2,983,583.25
Guatemala	dd/mm/yy	dot	comma	15/04/18 01:18:07	256.53	2,983,583.25
Honduras	mm-dd-yy	dot	comma	04-15-18 01:19:29	256.53	2,983,583.25
Mexico	dd/mm/yy	dot	comma	15/04/18 01:20:55	256.53	2,983,583.25
Nicaragua	mm-dd-yy	dot	comma	04-15-18 01:23:25	256.53	2,983,583.25
Panama	Mm/dd/yy	dot	Comma	04/15/18 01:24:49	256.53	2,983,583.25
Paraguay	dd/mm/yy	comma	dot	15/04/18 01:25:47	256,53	2.983.583,25
Peru	dd/mm/yy	comma	dot	15/04/18 01:31:04	256,53	2.983.583,25
Puerto Rico	mm-dd-yy	dot	comma	04-15-18 01:32:36	256.53	2,983,583.25
Spain	dd/mm/yy	comma	dot	15/04/18 01:33:42	256,53	2.983.583,25
Uruguay	dd/mm/yy	comma	dot	15/04/18 01:34:46	256,53	2.983.583,25
Venezuela	dd/mm/yy	comma	dot	15/04/18 01:35:47	256,53	2.983.583,25