C Multi-Language Support

With the introduction of Multi-Locale Support, you can view the OFSAA Applications' user interfaces in various languages.

OFSAA Login Screen

The Login window allows you to select a display language.

Figure C-1 Multi-Language Support - OFSAA Login Screen


This illustration shows the login page for the OFSAA applications. You can select the required Language, enter valid User ID and Password, and then click Login.

List of Supported Languages

In addition to the base language (American English, for example, en_US), the following languages are currently supported for Profitability Management, by installing the associated Language Pack.

Table C-1 Language Name versus. Java Locale List

Language Name Java Locale
Arabic AR_EG
Portuguese PT_BR
French FR_FR
German DE_DE
Indonesian IN_ID
Italian IT_IT
Japanese JA_JP
Korean KO_KR
Russian RU_RU
Simplified Chinese ZH_CN
Spanish ES_ES
Thai TH_TH
Traditional Chinese ZH_TW
Vietnamese VI_VN
Turkish TR_TR
Hebrew iw_IL
French Canada fr_CA

Depending on the type of the rule, the Name/Description specified during creation or edit either is attached to the login locale or is stored independently of the login locale. The selection of the login locale, therefore, governs which assumptions/rules are visible, and which are not visible.

Table C-2 Visibility of Assumptions and Rules

Assumption or Rules Visible Across all Languages Visible Only in the Creation-Language *
Administration
Process Tuning Yes
Simplified Batch Yes
Master Maintenance
Interest Rate Codes** Yes
Currencies** Yes
Funds Transfer Pricing
Rule Specification
Allocation Specification Yes
Allocation Mode Yes
Static Table Driver Yes
Lookup Table Driver Yes
Allocation History Yes

This table illustrates the visibility of assumptions and rules across languages in this release. This applies to all Summary screens, embedded selections in subsequent screens, and so on.

  • * A future release (TBD) will expand visibility for many of these application object types, to provide visibility regardless of logged-in locale.
  • ** These object-types are visible across all languages because the Name and Descriptions are not stored in translation-compatible structures, which is different from the storage format for AAI objects such as Dimension Management, Filters, and Expressions.