con7701_al-nubani-con7701-ebs_i18n_mls_2014_v03

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |

Oracle E-Business Suite Internationalization Overview & Multilingual Features

Maher Alnubani Senior Development Director E-‐Business Suite Development October 02, 2014

1


Safe Harbor Statement The following is intended to outline our general product direcLon. It is intended for informaLon purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or funcLonality, and should not be relied upon in making purchasing decisions. The development, release, and Lming of any features or funcLonality described for Oracle’s products remains at the sole discreLon of Oracle.

2


Program Agenda

1

2

3

4

5

GlobalizaLon: MeeLng Local and Global Requirements

Unicode & MulLlingual Features

Regional Preferences (Locale)

InternaLonal Calendars

MulLlingual ReporLng

Q&A

3

6


Program Agenda

1

2

3

4

5






Q&A

Oracle ConfidenLal – Internal/Restricted/Highly Restricted 4

6


GlobalizaLon: MeeLng Local and Global Requirements •  Single, Complete Data Model

•  Unicode

•  Multilingual Support (MLS)

•  Regional Preferences (Locale)

•  InternaLonal Calendars •  Currencies •  Timezones •  Address Management


Endeca Extensions for eAM Simplified Chinese


Approvals Mobile App Japanese


Desktop IntegraLon Simplified Chinese


BI Publisher (PDF Reports)


Bi-‐direcLonal Language Support


Bi-‐direcLonal Language Support Rich UI


BI Publisher Sample Report


Program Agenda

3

4

5






Q&A


6

2

1


Unicode Support •  Unicode is a universal character set covering live scripts of the world in a simple and consistent manner

•  Oracle database supports two Unicode character sets: – AL32UTF8: based on latest Unicode standard, currently 7.0 – UTF8: on maintenance mode and supports Unicode 3.0 standard

•  AL32UTF8 is the default database character set of Oracle E-‐Business Suite installaLon in R12.1 and above, when mulLple languages are selected – UTF8 in 11i and R12.0

•  AL32UTF8 is the character set of VISION demo database in R12.1 and above – UTF8 in 11i and R12.0

•  NaLve character sets are sLll supported


Moving to Unicode •  Why convert to AL32UTF8?

– Support more characters and languages (e.g., convert from ZHS16GBK to AL32UTF8 to addiLonally support Korean)

–  Industry Standard – Fusion Apps only support AL32UTF8 character set

•  Oracle Database MigraLon Assistant for Unicode (DMU), a unique next-‐generaLon migraLon tool providing an end-‐to-‐end soluLon for migraLng your databases from legacy encodings to Unicode

•  Oracle consulLng services (OCS) offers character set conversion services •  EBS internaLonalizaLon team provides acLve support for OCS character set conversion projects


Release 12.1 Technology Stack 3-‐Tier Logical Architecture

JSP

Forms

BI Publisher

BC4J

OC4J

Web

Listene

r UIX

Client

RAC & ASM

Global Single Data Model

HTTP/S – CLIENT IAN

A ENCO

DING

10g

ApplicaWon Database

10gR2 | 11g JDBC(UTF-‐8)/SQ

L Net (N

LS_LANG)


EBS Release 12.2 Technology Stack 3-‐Tier Logical Architecture

R2 Database

WebLogic Server JDBC(UTF-‐8)/SQ

L Net (N

LS_LANG)


A ENCO

DING

Client ApplicaWon

RAC & ASM

Global Single Data Model

EdiWon-‐Based RedefiniWon

WebLogic JSP

Forms

BI Publisher

BC4J

Web

Listene

r UIX 11g


A ENCO

DING


NaLonal Language Support NLS

• Ability to run in user’s naLonal language • Ability to use date, number, and currency formats specific to certain country or region

• SomeLmes referred to as Locale • E-‐Business Suite NLS patches are special patches that provide language translaLons including user interface labels, menus, and seed data. The term "translaLons" is ooen used as a synonym


MulLlingual Support MLS

• Oracle E-‐Business Suite supports running mulLple languages in the same instance simultaneously

• Any number of supported languages (aka NLS patches) can be installed in a given instance


E-Business Suite Multilingual Support Language and Country Support

• Supports 38 languages American English, Albanian*, Arabic, Brazilian Portuguese, Canadian French, CroaLan, Czech, Danish, Dutch, French, Finnish, German, Greek, Hebrew, Hungarian, Italian, Indonesian*, Japanese, Kazakh*, Korean, LaLn American Spanish, Lithuanian*, Norwegian, Polish, Portuguese, Romanian, Russian, Simplified Chinese, Serbian* (LaLn & Cyrillic), Slovak, Slovenian, Spanish, Swedish, TradiLonal Chinese, Thai, Turkish, Ukrainian*, and Vietnamese*

• Supports all 120** countries supported by Oracle Database * Introduced in R12.1 and above

** 28 countries added in R12.2.2


Flexible MLS Architecture

Add more language translaLons as you need

E-‐Business Plaqorm

MLS Architecture

US ZHS Trans

AR Trans

F Trans Trans …


Flexible MLS Architecture

• A MulWlingual EnLty(Table) is one for which textual arributes are maintained for all languages

• Base table stores non-‐textual arributes • TranslaLon table stores textual arributes and their translaLons for each installed language

• Language view joins the two tables, displaying textual arributes in user’s language


Base and TranslaLon Tables

Base Table xxxx_B TranslaLon

Table xxxx_TL

For each row in base table, N rows exist in translaLon table corresponding to the N installed languages


Any Number of Languages Base and TranslaWon Table Structure

One row for each installed language contains translated textual arributes

Arabic English Simplified Chinese

Base table row contains language-‐independent arributes


Language view joins non-‐textual and textual

arributes Base Table xxxx_B

TranslaLon Table XXXX_TL

Language View XXXX_VL

One Language View Language View Structure


Lightweight MLS Enable a Language with English UI

• A new feature introduced in R12.1.3 • Ability to enable a language without applying the corresponding NLS patch

– English UI – All supported languages can be lightweight enabled – Fully patched and lightweight languages can coexist at the same instance – SelecLve (parLal) NLS patching is not supported; either full or lightweight MLS is supported for each language, but not both at the same Lme

• Can move to a full translaLon at any Lme, simply by applying corresponding NLS translaLon patches


Lightweight MLS

•  English User Interface – Setup or customer data is shown in the corresponding language – Use loaders such as FNDLOAD to enter and maintain language data – May also use 'globe icon’ in Oracle Forms based UI to translate language data

• Custom Reports – Create custom reports or translate Oracle seeded reports

• No need to apply NLS patches •  In R12.2, it’s possible to move a language from full MLS to lightweight MLS


Lightweight MLS Lightweight-‐Only Languages

•  Introduced in R12.2.3 – Catalan – Bulgarian

• Can be enabled only as a lightweight language because there are no translaLons, i.e., no NLS patches, available

• Allows customers to meet the local laws and statutory requirements • More languages are planned for the future releases


Customer Setup Data TranslaLon

• Oracle provides UI translaLon through NLS patches • Customer can translate setup data using:

– Forms UI globe icon – PersonalizaLon of UI strings – FNDLOAD (data loader) for mass-‐translaLon

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | 30

Forms UI Globe Icon

30


iSetup MulLlingual Support

• Introduced in release R12.1.3 • MulLlingual customers can uLlize iSetup to gradually implement languages

• Customers can choose the set of languages to extract: all, one (session), or a subset of implemented languages


Program Agenda

3

4

5






Q&A


6

2

1


Profile OpLons

• Profile opLons control regional preferences (locale) • Administrators can set profiles at various levels

– Site – ApplicaLon – Responsibility – User

•  Each user can override default sevng with preferred values – User Preference Page


Regional Profile OpLons Locale

•  Site level profile opLons –  Client IANA encoding –  Server Lme zone

•  User level profile opLons –  Language –  Territory –  Timezone –  NaLve client encoding –  Date format –  Numeric characters –  LinguisLc Sort – new in 12.2


User Preference Page


Site Level Profile OpLons • ICX: Client IANA* encoding • IANA character encoding determines character set of HTML-‐based UI on client Ler (Browser)

• Should be set to an IANA encoding equivalent to database character set • Should be set at site level

* IANA: Internet Assigned Numbers Authority


User Level Profile OpLons

•  ICX: Language – Default applicaLon language, if no language is selected at login Lme – Determines language of email noLficaLons – Normally set to user’s preferred language

•  ICX: Territory – Should be set to user's territory (country or region) – Used in conjuncLon with language code to pick the correct translaLon resources such as BI Publisher templates

– Determines certain cultural convenLons in some reports such as local Lme, date, numeric, or monetary convenLons



• FND: NaLve Client Encoding – Should be set to client (user) PC encoding – Determines character encoding of file name and content

• While exporLng/imporLng spreadsheet data • While uploading/downloading text files • We recommend using the pre-‐set default value


User Level Profile OpLons User-‐Preferred Timezone Support

•  Introduced in 11.5.10 CU2 • Users can specify their local Lmezone for both display and entry of date-‐with-‐Lme fields

• Date fields without Lme component are not affected by this feature •  The data in the database conLnues to be stored in the standard corporate Lme zone

• We strongly recommend that the database Lmezone should not be changed once it has been set and data has been entered


User Level Profile OpLons User-‐Preferred Timezone ConfiguraWon

• Database must be set to the standard corporate Lmezone – Configured to use the Wmezlrg.dat file rather than Wmezone.dat file – Server OS Lmezone must be set to the standard corporate Lme zone – Must be started in the standard corporate Lmezone

• ApplicaLon Ler must be set to the standard corporate Lme zone – All servers OS must be set to the standard corporate Lmezone – All JVM’s (Java Virtual Machine) must be started in the standard corporate Lmezone


User Level Profile OpLons User-‐Preferred Timezone ConfiguraWon -‐ conWnued

•  Site level profiles – SERVER_TIMEZONE_ID: ‘Server Timezone’ must be set to the same standard corporate Lmezone as the database. It should not be changed once set because exisLng data won’t be updated

– ENABLE_TIMEZONE_CONVERSIONS: 'Enable Timezone Conversions‘ must be set to 'Yes' (or 'Y')

– CONC_MULTI_TZ: ‘Concurrent: MulLple Time Zones') must be set to 'No’ (or 'N')

• User level profile – CLIENT_TIMEZONE_ID profile opLon (preference ‘Timezone‘) must be set to the user preferred Lme zone



•  ICX: Date format mask – Can be set to user's preferred date format

•  ICX: Numeric characters – Supported combinaLons:

•  Comma / period (10,000.00) •  Period / comma (10.000,00) •  Space / comma (10 000,00): introduced in 12.1.2 •  Space / period (10 000.00): introduced in 12.1.2 •  Single quote / comma (10’000,00): introduced in 12.1.2 •  Single quote / period (10’000.00): introduced in 12.1.2


AddiLonal Number Group Separators


LinguisLc Sort Support

•  Introduced in R12.2.2 •  Earlier releases support binary sort only, which produces reasonable results in naLve character sets but not when using Unicode

•  Languages have their own specific sorLng rules and this is known as linguisLc sort

• When enabled, UI (OA Framework, Forms) shows linguisLcally sorted data based on user preferred linguisLc sort

• No linguisLc indexes are required for linguisLc sort support

44


LinguisLc Sort Support

• User Level Profile OpLon – ICX: NLS Sort (ICX_NLS_SORT ) – Can be set at the user and site level by administrators

•  LinguisLc sort currently not supported for concurrent programs and reports

45


LinguisLc Sort Support Profile OpWon Values – Introduced in 12.2.2


Program Agenda

3

4

5






Q&A


6

2

1


InternaLonal Calendar Support

•  Introduced in release 12.1.1 • Besides Gregorian, 12.1.1 supports the following calendars:

– Arabic Hijrah: The official calendar in Saudi Arabia with Arabic Hijrah month names – English Hijrah: The official calendar in Saudi Arabia with English transliterated Hijrah month names

– Thai: The official Thai solar calendar of Thailand

• Users can choose their preferred calendar •  Internal date representaLon is normalized to Gregorian


InternaLonal Calendar Support Oracle Forms UI Date Picker


InternaLonal Calendar Support Oracle Forms UI Date Fields


InternaLonal Calendar Support OA Framework Date Picker

Thai Calendar Date Picker

Hijrah Calendar Date Pickers


InternaLonal Calendars Support Inline Date Pickers

Thai

English Hijrah Gregorian

Arabic Hijrah


InternaLonal Calendar Support BI Publisher


InternaLonal Calendar Support Gana Chart


First Day of The Week Support

•  Introduced in release 12.1.2 • Users in countries where Sunday is not the first day of the week can now choose their preferred first day of the week

• A new system profile opLon that can be set at the site, applicaLon, responsibility and user levels – FND: Calendar Week Start Day

•  This profile changes first day of the week of Oracle ApplicaLon Framework and Forms date pickers only, but does not affect business logic or reports


First Day of The Week Support


Program Agenda

3

4

5






Q&A


6

2

1


BI Publisher Language Support •  BI Publisher ships with a full set of Unicode Fonts

•  TrueType font embedding and subsevng

•  No need for expensive language-‐specific printers

•  BI Publisher supports – CJKV languages – BiDi languages – Unicode – MLS


BI Publisher Translatability

• Communicate with your partners around the world – No dependency on installed languages – No dependency on DB character set

• Create a template for any language/territory – Translate template or send to 3rd party – Support for XLIFF*

•  Supports 96 locales

* XLIFF: XML LocalisaLon Interchange File Format


ExecuLng MLS Concurrent Programs

• Users can submit a single concurrent program or report requests in mulLple languages at the same Lme using: – Forms Standard Request Submission (SRS) UI – OA Framework (web) SRS UI: introduced in R12.1.1 – Users can specify languages, territories, and numeric characters

• Output can be routed to different printers based on language • CompleLon noLficaLons can be routed to users based on language


ExecuLng MLS Concurrent Programs System AdministraWon: -‐ Requests > Schedule

“Language Sevngs” region allows user to set the NLS opLons


Oracle ApplicaLon Framework Export MulWlingual Support

•  StarLng from 12.1.3 release, you can choose between comma and tab as a delimiter when exporLng files

•  FND_UNICODE_IN_EXPORT profile opLon determines the export file Unicode encoding

•  You can choose between UTF-‐16 lirle endian (UnicodeLirle) or UTF-‐8 for export file Unicode encoding regardless of browser or plaqorm

• Good workaround for some old versions of Microsoo Excel's Unicode data import limitaLons


Oracle ApplicaLon Framework Export MulWlingual Support


Summary

• Upgrade to 12.1.3 or 12.2 to get the latest internaLonalizaLon support • Convert to AL32UTF8 • Adopt lightweight MLS • Use iSetup to support phased language rollouts •  Take advantage of the internaLonalizaLon new features


<Insert Picture Here>

References Reference Material

65


Reference Material •  GlobalizaLon Guide: R12 (MOS 393861.1); R11i (MOS 333785.1) •  I18N Update Notes: R12 (MOS 393320.1); R11i (MOS 222663.1)

•  Hijrah and Thai Calendar Support: R12.1 & R12.2 (MOS 807393.1)

•  Lightweight MLS: R12.1.3 and higher (MOS 1077709.1)

•  MigraLng Oracle ApplicaLons Character Set to Unicode (MOS 124721.1)

•  “Oracle ApplicaLon Concepts Guide”, Chapter 3 •  “Installing Oracle ApplicaLons” for InstallaLon Procedure •  “NLS Release Notes” on Support Site


Q&A


GlobalizaLon – Terminology

•  A sooware design process to make a product flexible to funcLon worldwide •  Such product can handle data of different languages, allow for a choice of locales, and locale specific formats

InternaLonalizaLon -‐ I18N

•  TranslaLng product UI strings and Help from English to another language •  Products must first undergo translatability tesLng to ensure code and files meet translaLon standards

TranslaLon -‐ T9N

•  Developing country-‐specific funcLonality to provide compliance with local statutory requirements

•  Best handled product development teams based on global market requirements LocalizaLon – L10N

69


InternaLonalizaLon – Terminology

• Text processing, data flow, font handling, data entry, search …etc. • Support of Bi-‐DirecLonal scripts, CJKV (Chinese, Japanese, Korean, and Vietnamese), Thai, and Unicode

Data handling and display

• Date format, number format, currency, name/address order …etc. Locale support

• Externalize product UI strings from code logic • Define runLme translaLon process (Catalogs, files, …etc.) • Support for all languages on the same server (MLS)

Translatability and MLS

• InstallaLon, AdministraLon, User • User Profile, Locale, Character set, Format, DirecLon …etc. I18N opLons

70

con7701_al-nubani-con7701-ebs_i18n_mls_2014_v03

Documents

oracle andor

unicode support unicode

sole discrelon of oracle

unicode character sets

eam simplied chinese

latest unicode standard

meelng local

global requirements