The app has rich internationalization features and multi-language support. It supports translation to over 50 languages and includes features for Arabic and Hebrew users, such as right-to-left layout mirroring and bidirectional text.
The internationalization features include:
- The ability for users to choose the language they want to use when using the app
- Out-the-box translations for Applaud-delivered text for the most common languages
- Auto-translation of your own customer-defined text using Applaud Cloud
- Options to allow administrators to configure the person name formats according to requirements
- The ability for Arabic users to use the Islamic (Hijri) calendar when interacting with dates
A user's language can be set in a number of ways:
- By choosing the language when logging in via Oracle E-Business Suite pages
- By choosing the language when logging in via in-app login pages
- By setting the user's language preferences on the Oracle preferences page
- By setting the profile options ICX: Language and ICX: Territory at the site or user level
The base language is used if none of the above are set.
When a user's language is set to Arabic or Hebrew the user interface will automatically mirror the layout to right-to-left.
Applaud-delivered text is translated and installed during the regular patch install process. It:
- Analyses the languages you have installed, and then
- Automatically loads translations for Applaud-delivered text for the installed languages
You do not need to install separate NLS patches for each language; you simply install the regular patch and the above will happen automatically.
Translations of Applaud-delivered text is installed for the following languages:
- Arabic (AR)
- Brazilian Portuguese (PTB)
- Canadian French (FRC)
- Dutch (NL)
- French (F)
- German (D)
- Greek (EL)
- Hebrew (IW)
- Hungarian (HU)
- Indonesian (IN)
- Italian (I)
- Japanese (JA)
- Korean (KO)
- Latin American Spanish (ESA)
- Polish (PL)
- Simplified Chinese (ZHS)
- Spanish (E)
- Thai (TH)
- Traditional Chinese (ZHT)
- Turkish (TR)
- Vietnamese (VN)
Installing new languages
If you install a new language into Oracle and wish to load the Applaud translations, you should:
- Install the Oracle language, following My Oracle Support and Oracle Product Documentation guidelines
- Re-install the Applaud patch
This will ensure the Applaud-specific translations are loaded.
Auto-translating customer text
Applaud seeded text is translated and installed during the normal patch install process. See Out-the-box translations. You can also automatically translate your own customer-defined text using Applaud Cloud.
This feature is only available to Enterprise-tier customers.
This feature will translate any metadata that can be seen by end-users in the Applaud application. For example:
- Page and block titles
- Button labels and hover text
- Informational, warning, and error messages
- Field labels
- Search facet labels
It does not translate:
- Transactional data. For example, organization and job data.
- Descriptive or key flexfield attributes and segments.
- Metadata that is not seen by end-users, such as FND Function names and FND Menu names.
- Translatable dependent and translatable independent value set values.
- Messages or Lookups not attached to the Applaud Solutions application
- Lookups not used as a list provider in an Applaud form
- Menu entries not used in the Applaud app
To translate text automatically:
- Ensure you have the latest software patch installed
- Ensure that your E-Business Suite environment has a working connection to Applaud Cloud. See Connecting Oracle E-Business Suite to Applaud Cloud.
- Navigate to the Applaud Administrator responsibility and run the Localize Text concurrent program.
This will analyze the configuration in your environment and automatically translate the text. These are some important things you should note:
- The program will complete in error if any single piece of text cannot be translated. However, the program will still process all pieces of text. You should analyze these errors and take corrective action.
- If the error is listing a 400 Bad Request error, this is probably because the text contains corrupted characters. Please correct the base text and re-run the process.
- The program will stop processing if it hits 20 errors.
- The program will complete with a warning if any pieces of text were truncated because the underlying Oracle columns do not have enough space. You should review these warnings and consider reducing the label of the base text, or manually updating the translations for these items.
- You can re-run the program as often as you like. For example, you might wish to schedule it daily so that any new configuration is automatically translated. Please ensure you always review warnings and errors in the concurrent request log file.
- You can opt to translate configuration on a development environment, and then load the translations into other environments using FNDLOAD. For example, if you don't want to enable Applaud Cloud access to your production environment. The translations consist of FND Messages, FND Menu Entries, FND Lookup Types, and the Search Facets User Defined Table. Standard Oracle loaders are available for all these items except the Search Facets User Defined Table, which can be loaded through an Applaud-delivered loader. Please refer to Importing and exporting.
Person name formats
Throughout the app, people's names are displayed in a consistent format. This format can be configured according to your requirements.
By default, a person's name uses this format: <Known As or if that's blank First Name> <Last Name>. For example, John Doe.
Alternatively, you can make use of Oracle’s own Person Name Formats functionality. The name will be displayed based on the following rules (applied in the given order):
- If the HR: Local or Global Name Format profile option is set to Local, it displays the person’s local name.
- If the HR: Local or Global Name Format profile option is set to Global, it displays the person’s global name.
- If the HR: Local or Global Name Format profile option is not set and HR:Display Person Name is set to Full Name, it displays the person’s full name.
- If HR: Local or Global Name Format is not set and HR:Display Person Name is not set or is set to anything other than Full Name, it uses the default specified above.
Please refer to the Oracle HR Implementation Guides available on oracle.com for more information on how to configure the standard Oracle Person Name Format functionality.
Arabic users can choose to use the Hijri calendar when viewing or selecting dates:
This is a touch-friendly calendar that allows a user to choose dates using the Islamic calendar or switch to the Gregorian calendar.
Display of the Islamic calendar uses the Oracle-standard FND: Forms User Calendar profile option to determine a user's calendar preference. When this option is set to English Hijrah, the calendar will display the Islamic calendar in English, and conversely when this option is set to Arabic Hijrah the calendar displays in Arabic. In both cases, the user has the option to swap to Gregorian on a field-by-field basis.
When viewing a date form field in view-only and the user's preference is set to use the Islamic calendar, the date will show the Hijri date with the Gregorian equivalent in brackets.
to_char(SYSDATE,'DD/MM/YYYY','NLS_CALENDAR = ''ARABIC HIJRAH''')
|| ' ('
|| to_char(SYSDATE,'DD/MM/YYYY','NLS_CALENDAR = ''GREGORIAN''')