How Oracle Fusion CRM Handles Multilingual Implementations

January 23, 2012

Oracle Fusion CRM comes with an interesting architecture for handling multi-language implementations. This means during the initial deployment phase itself, a number of languages can be configured so that the user can choose their preference during login.

Fusion CRM Provides two language choices when any user logs in:

  • Default Application Language
  • Current Session Language

Once these two are setup, whenever the same user logs in again, they will only see the Oracle Fusion CRM interfaces in “Default Application Language,” They can change it to a different language in “Current Session Language” temporarily. Still, it is not a permanent change until the “Default Application Language” is changed.

As far as the support for multiple languages goes, Oracle Fusion CRM Provides a user-friendly interface for translating labels and other text from one language to another. This goes through an approval cycle before it is shown to the end users. Any corrections/rework can be done at this stage.

Technically speaking, all these language-specific texts are stored in a Strings Repository. It has three tables:

  • Base Table (English)
  • Translation Table (All installed languages)
  • Languages Table

If you have 100 labels in your Fusion CRM application and 5 languages installed (Including English), “Base Table” will have 100 labels, and “Translation Table” will have 400.

Similar to this, Fusion CRM also supports multiple currencies, number/date/time formats, Territory preferences, and many more. Indeed a global CRM application!

Tags: CRM Applications, How Oracle Fusion CRM Handles Multilingual Implementations, Two Languages Choices

0 replies on “How Oracle Fusion CRM Handles Multilingual Implementations”

Leave a Reply

Your email address will not be published. Required fields are marked *