Académique Documents
Professionnel Documents
Culture Documents
1
ATTENTION – AUDIO INFORMATION
Section Divider
10
Workflow
11
Workflow (Right-to-Left)
12
Desktop Integration
13
Field Service / Laptop
14
XML Publisher (PDF Reports)
15
Oracle E-Business Suite standard languages
16
<Insert Picture Here>
Section Divider
• 37 Languages Supported
• NLS/MLS is not related with Tax Localizations (ie: JE, JG, etc), Multi-Org
or MRC
18
NLS/MLS Basics – Directories
19
MLS Architecture
JDBC
Database UTF-8
Forms
Server Java
OA Application Application
Definitions Mobile Application
Foundation (JTM)
Publisher
Templates JTM
Mobile
NLS_LANG XML Publisher Application
Net8
Translation
(Base-TL tables)
iAS PDF/RTF/HTML
User Profiles Reports
20
MLS Architecture
21
Base Table and Translation Table
Translation
Base Table Table
22
Any Number of Languages
Arabic
English
23
One Language View
Language
View
Language View
joins non-textual
and textual
attributes
Base
Table Translation Table
24
<Insert Picture Here>
Section Divider
26
Characterset selection for Install
Recommendations :
• Release 11i : UTF8
• Release 12 : AL32UTF8
For the Thai language it is recommended to use the Thai specific Characterset.
28
NLS/MLS Installation
29
NLS / MLS Installation
• The rows in the Translation Tables are maintained with the
Utility adadmin via the process ‘Maintain multi-lingual tables’
for example :
$FND_TOP/sql/FNDNLINS.sql
$AD_TOP/sql/ADNLINS.sql
30
NLS / MLS Installation
Release
Which document to be reviewed for NLS / MLS Installation ?
12.0.4 Note 550206.1 Oracle Applications NLS Release Notes, Release 12.0.4
12.1.1 Note 788053.1 Oracle Applications NLS Release Notes, Release 12.1.1
12.1.2
31
Translation Synchronization Patch
Release Which action finished currently ? Which Media to use ?
32
Adding More Languages
33
NLS / MLS Patches
• Some patches require translation, some don't.
The line 'compatible requires_translation yes' is specified in the Patch driver.
34
<Insert Picture Here>
Section Divider
36
37
Configuration:
Site Level Profile Options
• ICX: Client IANA Encoding
• Should be set to the equivalent of DB Character set
• Determines the character set of the application tier
• Should not be set at other than site level (some releases of
Apps allow it to be set at other levels, but we recommend not
setting it)
38
Configuration:
User Level Profile Options
• ICX: Language
• Should be set to the user preferred language
• Determines the language used for UI, Reporting etc.
• ICX: Territory
• Should be set to the user's territory (country)
• Used to determine default formatting types such as Date
Format, Numeric Format etc.
39
Configuration:
User Level Profile Options
• Client Timezone
• Should be set to the user's time zone
• FND: NATIVE CLIENT ENCODING
• Should be set to the Desktop PC's encoding
• Determines the encoding of the filename and content
• While exporting/importing spreadsheet data
• While uploading a file (e.g., Text file)
40
Configuration:
User Level Profile Options
• ICX: Date format mask
• Can be set to user's preferred date format
• If the date format includes 'MON', and the database is
UTF8, 'MON' will be changed to MM, if the language
is NUMERIC_DATE_LANGUAGE
• e.g., for Chinese in UTF8, DD-MON-RRRR will work
as DD-MM-RRRR
• ICX: Numeric characters
• Can be set to 10,000.00 or 10.000,00
41
Implementation:
Customer Setup Data Translation
• Click on Globe Icon and edit translation values for the language
• Use FNDLOAD (Data Loader) for mass-translation
42
43
<Insert Picture Here>
Section Divider
• Check if you can use conversion in steps (with fewer conversion errors):
• Initial character set -> Intermediary character set
• Intermediary character set -> Final Character set
Example:
If your WE8ISO8859P1 database has for example Hebrew stored you
need to go most likely to IW8MSWIN1255 before going to AL32UTF8/UTF8.
45
Character Set Conversion
Example of errors reported by csscan conversion:
46
Character Set Conversion
scan.txt
User : APPLSYS
Table : FND_FLEX_VALUES_TL
Column: DESCRIPTION
Type : VARCHAR2(240)
Number of Exceptions : 589
Max Post Conversion Data Size: 253
-> lossy conversion
User : APPLSYS
Table : DR$FND_LOBS_CTX$I
Column: TOKEN_TEXT
Type : VARCHAR2(64)
Number of Exceptions : 982550
Max Post Conversion Data Size: 192
-> lossy conversion
47
Character Set Conversion
• NLS data inserted by you.
48
Character Set Conversion
Usual issue during conversion:
• DR$FND_LOBS_CTX$I is used internally for the FND_LOBS_CTX intermedia
(context) index on the FND_LOBS table. The data stored in this table is in oracle
internal format to represent the context index. It is possible that this internal
representation doesn't comply with the charset, since the data is never accessed
directly on these tables it doesn't matter what is the charset.
• To able to complete your charset conversion, you can simply drop this index before
conversion and then recreate afterwards using aflobbld.sql.
49
Character Set Conversion
• Check if some tables can be purged.
For example:
• FND_LOG_UNIQUE_EXCEPTIONS;
• FND_LOG_EXCEPTIONS;
• FND_LOG_MESSAGES
50
Invalid Characters / Junk
51
Invalid Characters / Junk
52
Invalid Characters / Junk
How to solve:
Restore from a full file system and database backup, and add the
languages again using the correct Characterset.
53
Invalid Characters / Junk
Verify if needed fonts are installed:
Note 433435.1 Japanese characters are displayed like square boxes in Ebusiness
Suite
Note 296547.1 Japanese Characters Appear As Square Boxes In Oracle Applications
If only few cases: Identify .ldt associated and reload (see Partial translations section)
54
Changing the Base Language
• Applications that are not NLS enabled, have their product seed data only
in the base language.
• On _TL table generation data are multiplied in base language
55
Change Basic language
Did you recently changed the base language ?
The perl script adchgbase.pl is excluding the US ldt files because of the date
restriction imposed when selecting the from AD_PATCH_COMMON_ACTION.
The WHERE clause in adchgbase.pl in the gen_sql sub proc, only selects rows
where the last update date is greater or equal to June 1, 2004, but several of the
US rows have a date that is older than June 1, 2004 (i.e last update was in 2003).
How to solve:
• 12.0.4 - patch 8848134 -> bug 8848134
• 12.1 - patch 9001300 -> bug 9001300
56
De-Installation of a language
57
NLS / MLS Forms Compilation Issues
Use adadmin and generate the form. Check adadmin.log (only last part with this
session) and related adworker.log (only last part with this session).
• Compile both US and NLS form:
Run adadmin and choose:
Enter list of products ('all' for all products) [all] : CS
Generate specific forms objects for each selected product [No] ? Yes
Choose form: CSCCCCRC.fmx
• Verify the version of US and NLS form
adident Header $AU_TOP/forms/US/CSCCCCRC.fmb
adident Header $CSC_TOP/forms/US/CSCCCCRC.fmx
adident Header $AU_TOP/forms/F/CSCCCCRC.fmb
adident Header $CSC_TOP/forms/F/CSCCCCRC.fmx
58
NLS / MLS Forms Compilation (Cont.)
• Same version for .fmb and .fmx, then it was compiled successfully
59
Calendar related
Option 1:
• From System Administrator Responsibility, Unset the Profile Option :
ICX: Date Language (at all the levels)
Note 396153.1 Months in the calendar are not translated in any language
Note 305367.1 Dates Appears in English After Upgrading to 11.5.10 or After Applying ATG-
PF.H
Option 2:
The translation is included in $AU_TOP/forms/NLS/APPSTAND.fmb. Check the version
of these files:
adident Header $AU_TOP/forms/US/APPSTAND.fmb
adident Header $AU_TOP/forms/NLS/APPSTAND.fmb
Ensure they are same version, and if necessary use adadmin to regenerate this form
for both languages. (Reference Bug 2486014 and Bug 6156263)
60
Partial translation
Check if this should be translated:
11i: Note:185637.1 Oracle Applications 11i Translation Scope and Availability
12: Note:405992.1 Oracle Applications Release 12 Translation Scope and
Availability
61
Partial translation
62
Partial translation
Note 252422.1 Requesting Translation Synchronization Patches
This will not load information if these are customized (need to load them
using force option – discussed in next slides)
63
Partial translation
If the issue is :
64
Partial translations in Forms
65
Partial translations in Forms
How to check the select behind the data :
Help -> Diagnostic -> Examine
66
Partial translations in Forms
Check the select used:
Help -> Diagnostic -> Examine
67
Partial translations in Forms
Find the related files with data reported (using table name, an US string
or an NLS string):
$ cd $PRODUCT_TOP/patch/115/import/US
$ find ./ -name "*.*" -exec grep -Hsi ‘value in US language' {} \;
$ cd $JG_TOP/patch/115/import/US
$ find ./ -name "*.*" -exec grep -Hsi 'JG: Company Operating Unit' {} \;
./jgscprof.ldt: USER_PROFILE_OPTION_NAME = "JG: Company Operating Unit"
./jgjlprof.ldt: USER_PROFILE_OPTION_NAME = "JG: Company Operating Unit"
./jgjaprof.ldt: USER_PROFILE_OPTION_NAME = "JG: Company Operating Unit"
./jgjeprof.ldt: USER_PROFILE_OPTION_NAME = "JG: Company Operating Unit"
68
Partial translations in Forms
If the translations in the files are correct:
Be aware ! - If you have any Customization (e.g. your own translations) stored in
the tables touched via the FNDLOAD command – they will be lost !
69
Partial translations in Forms
cd $PRODUCT_TOP/patch/115/import/NLS
find ./ -name "*.*" -exec grep -Hsi 'menu in specific language' {} \;
70
Partial translations in Forms
71
Forms label(s) not translated
IF the label is in the form => try to have the correct form:
• regenerate the form via adadmin
• verify that NLS form version is the same like US form version
• Oracle Support can provide you with a newer version of the Forms file
IF the label is NOT in the form, search for the file delivering the labels:
Example:
cd $GL_TOP/patch/115/import/US
find ./ -name "*.*" -exec grep -Hsi 'Posting status' {} \;
./glprog.ldt: BEGIN DFF_SEGMENT "Posting Status" "ATTRIBUTE2"
./glprog.ldt: FORM_LEFT_PROMPT = "Posting Status"
./glprog.ldt: FORM_ABOVE_PROMPT = "Posting Status"
cd $PRODUCT_TOP/patch/115/import/NLS
find ./ -name "*.*" -exec grep -Hsi 'label in specific language' {} \;
Check the NLS file
Reload the NLS file using FNDLOAD:
72
Partial translation
When you are creating a SR, please provide following Information :
1)The responsibility and full navigation path to get to the translations issue -
this has to be supplied in both the translated language and US English
so that Development can find the problem form/report/source code.
2)The full name and version of the form / self service page with the issue.
Note! Please be aware that the support analysts working on your NLS
SRs don’t speak all languages available in Ebusiness Suite (they are
from Install team) !
73
Partial translations in online help
• See if online help for that particular module is translated in that particular language
• Note 317136.1 – ‘Translation Scope for Oracle Applications Release 11i Online Help’
• Note 969716.1 – ‘Release 12.1.1 Product Level Online Help Translation Matrix’
• Verify if the online help patch was correctly applied (without errors).
74
Partial translations in online help
Identify what is the target for that particular online help:
75
Partial translations in online help
Identify what is the file which brings for that particular online help:
US file :
select hd.file_id, hd.file_name, hd.title
from fnd_help_targets ht, fnd_help_documents hd
Where ht.file_id = hd.file_id
And ht.target_name='ARXTWMAI_BGW_BATCH‘
And hd.language = 'US’;
result : 1592828 AR00072542.HTM Batching Transactions for Easy Entry and Retrieval
(Oracle Receivables)
NLS file :
select hd.file_id, hd.file_name, hd.title
from fnd_help_targets ht, fnd_help_documents hd
where ht.file_id=hd.file_id
and ht.target_name='ARXTWMAI_BGW_BATCH‘
And hd.language='F’;
76
Partial translations in online help
If the NLS query does not return anything then load the htm
file into the database using following command:
FNDGFU apps/apps 0 Y PROGRAM_NAME=FND_HELP \
CONTENT_MAP=$FND_TOP/admin/import/fndgfu.txt LANGUAGE=<NLS> \
<PROD_TOP>/help/<NLS>/<filename>.htm
For example :
77
Partial translations in Self-Service
78
Partial translations in Self-Service
• Set the profile "FND: Diagnostics" to 'Yes' in order to see ‘About this page’
• Go to ‘About this page’ (right bottom side) and identify the page name:
/oracle/apps/fnd/framework/customjrad/webui/CustomJRADViewUpdatePage
79
Partial translations in Self-Service
for US version:
exec jdr_utils.PRINTDOCUMENT \
('/oracle/apps/fnd/framework/customjrad/webui/CustomJRADViewUpdatePage');
exec jdr_utils.PRINTTRANSLATIONS \
('/oracle/apps/fnd/framework/customjrad/webui/CustomJRADViewUpdatePage', \
'fr-FR',100);
80
Partial translations in Self-Service
US version
adident Header \
$FND_TOP/mds/framework/customjrad/webui/CustomJRADViewUpdatePage.xml
NLS version
adident Header \
$FND_TOP/mds/framework/customjrad/webui/F/CustomJRADViewUpdatePage.xlf
81
Partial translations in Self-Service
If there is a de-synchronization between database information and filesystem
Information re-load the self service pages:
82
Error accessing NLS Forms
When you try to access a Forms Responsibility in a language other than US, you are receiving the error
APP-FND-02950. In the most cases this error is received, after the Database has been upgraded to
Release 10g or 11g.
Solution :
For RAC enabled database set the environmental variable for the cluster :
• srvctl setenv database -d dbname -t ORA_NLS10=$ORACLE_HOME/nls/data/9idata
83
How to log a NLS / MLS Service Request
Use Product: Oracle Applications Translation
84
References
Note 399789.1 - NLS Frequently Asked Questions
Note 333785.1 - Oracle Applications Internationalization Guide
Note 393861.1 - Globalization Guide for Oracle Applications Release 12
Note:185637.1 - Oracle Applications 11i Translation Scope and Availability
Note:314411.1 - Translation Scope for Oracle Applications Release 11i Software
Note:317136.1 - Translation Scope for Oracle Applications Release 11i Online Help
Note:405992.1 - Oracle Applications Release 12 Translation Scope and Availability
Note 969716.1 - Release 12.1.1 Product Level Online Help Translation Matrix
Note 412218.1 - Software Translation Matrix
Note:168678.1 - Introduction To Patch Translation For Oracle Applications NLS Patches
Note:211708.1 - Detailed Explanations of How NLS/MLS is Being Handled in 11i
Note:299080.1 - Troubleshooting Incorrect Translations with FNDLOAD
Note 252422.1 - Requesting Translation Synchronization Patches
85
For More Information
Do you have any requests for future EBS - ATG Webcast Events?
Please email your suggestions to ruediger.ziegler@oracle.com,
subject: Topics of Interest.