Understanding Multi Language Support (MLS) in Oracle E-Business Suite

Understanding MLS in Oracle EBS

Introduction
Multi Language Support (MLS) is a feature in Oracle E-Business (EBS) Suite of applications that enables users to run their applications in many different languages. MLS has opened the doors for global rollout of Oracle EBS with users in different countries able to use the application in their own language at the same time.

Difference with NLS

National Language Support (NLS) refers to the ability of Oracle EBS to run in any one of the supported languages other than American English. However, MLS refers to the ability in which the instance can be run in as many as languages as are supported at the same time.

Entering and viewing data in local language

When a user wants to use the MLS features of an instance which is MLS enabled, then he/she would change the language parameter in the Preferences after logging in. This would make the forms to appear in the language selected and give other MLS capabilities. In order to enter the data translated in the local language in a given form, user has to click the Global Icon that would show in an MLS enabled instance.

www.sigmora.com

Page 2 of 4

Understanding MLS in Oracle EBS

What can be seen and entered in local language in MLS

Just because MLS is enabled, not every bit of information can be seen and entered in the local language of choice. The following are the items that are MLS compliant: Boiler-plate text in the Forms (the text next to the user-enterable fields in the selfservice and core applications forms) will show in the local language. Chart of Accounts description, Item description, Asset description and lookups can be translated and entered into local languages. The data thus entered is stored in separate translation tables in the database. Then when a user changes his preference to a local language and enters EBS, the data is fetched from these translation tables and the local language descriptions and lookup values would be displayed in the relevant forms, reports etc.
Some of the Oracle seeded documents like Bill of Lading, Sales Order

Acknowledgement, Print Invoice Notice, Printed Change Order report etc.

Making an instance MLS

Making an Oracle EBS instance MLS involves applying a lot of patches and some system administration tasks. Care has to be taken to test thoroughly the important transactions before moving these changes into production.

Alternatives to MLS
If the end users who use self-service responsibilities like iExpense, iProc etc., can read English and if the finance users who use core application responsibilities can understand seeded reports like trial balance etc., in English then there is no need to make the instance MLS. Some APAC countries however need external facing documents like customer invoice, PO etc., to be in local language. In order to fulfil this requirement, you can make the backend database as UTF-8 enabled, which would allow multi-byte character set. The users can then use segments in descriptive flexfields to enter the names in the local language for supplier, customer etc. The documents like customer invoice or PO can then be customized to pull the local language names from these segments for these specific countries. In this way, English names can show up for the English speaking countries and local names can show up for others.

www.sigmora.com

Page 3 of 4

Understanding MLS in Oracle EBS

Flowchart for MLS consideration

Can end-users using self-service responsibilities read English? No Yes

Consider MLS
Can core users understand seeded reports like Trial balance in English ? No

Yes

Do the localization requirements for some countries need external facing documents (invoices, POs etc) in local language?

English only EBS instance

No

Yes

1. Enable UTF-8 2. Enable segments in DFFs and enter local names for suppliers/customers 3. Customize invoices, POs to pull local names from the above segments for these countries

www.sigmora.com

Page 4 of 4