A Screening Non-Latin Character Sets
The reference data sources supported by Customer Screening are all provided in the Latin character set, and some in the original scripts. The screening process can also be used with non-Latin data. Non-Latin data can be screened against the Latin reference data sources which are supported by performing transliteration of data from the non-Latin character set to the Latin character set.
Non-Latin customer data can be screened against non-Latin reference data
without any changes to the product, although certain fuzzy text matching algorithms may
not be as effective when used to match data with the non-Latin character set. Text is
processed on a left-to-right basis.
Note:
You may have to install additional language packs to display non-Latin data. For more information, contact My Oracle Support (MOS).The following screenshot shows the transliteration of Cyrillic to the Latin character
set:
Figure A-1 Non-Latin Character Set
Original Script Matching
To match the original script data against reference data, follow these steps:
- Prepare customer and external entity data such that non-Latin names are populated in the Original Script Name fields.
- Enable Original Script Name match rules and clusters.
For more information, see the Oracle Financial Services Customer Data Interfaces
Guides.
Note:
You must make changes to the FCDM Customer Preparation process to support original script matching. For more information, contact My Oracle Support (MOS).