As part of the source system registration, ERP Integrator gets the list of available source system languages, in addition to the base language. The base language is typically the language selected when the ERP source system is installed. Additional available languages that are not the base language are referred to as the “enabled languages.”
Languages from the source system that are mapped to the languages defined in the target application are independent of the languages available for selection via the ERP Integrator browser selection. It is possible that the languages available in the browser differ from the languages available in the ERP source system and the target EPM application. For information on languages that ERP Integrator supports, see the Oracle Hyperion Enterprise Performance Management System Certification Matrix.
When you register a target application for use with ERP Integrator, the Default Language column on the Target Application Registration page is used as follows:
The languages displayed in the Default Language drop-down list are ERP Integrator supported languages. These languages are mapped behind the scenes to the ERP source system languages.
The Alias dimension in Essbase and Planning applications has a required “Default” member. The ERP Integrator language you select when registering a target application is automatically mapped to the “Default” member. Since the ERP Integrator language is mapped to the source system language, you map either the base or enabled source language in the source system to the “Default” alias member. During processing, all other languages are mapped to the other alias members as long as the alias member matches the ERP Integrator language member exactly.
Note: | Language processing is the same for Essbase and Planning applications created in Performance Management Architect and Classic Planning applications. |
Note: | Financial Management languages are processed based on the Default Language you select on the Target Application Registration page. |
For information on registering target applications, see Registering Target Applications.