The gap between what Oracle EPM can do and what most implementations deliver
Oracle Hyperion Planning and Oracle FCCS are technically capable of operating in a fully Arabic-language environment. Account descriptions, entity names, dimension labels, data entry forms, and reporting outputs can all be configured in Arabic. The platform supports right-to-left text rendering, Arabic numeral formats, and Hijri calendar integration where required by local regulatory practice.
In most GCC implementations, some or none of these capabilities are configured. The system operates in English, with Arabic names appearing in some fields and not others, with mixed-direction text in forms that confuses users, and with calendar and date formatting that does not match the reporting requirements of the jurisdiction.
The result is a system that technically functions and practically fails for the Arabic-speaking users who are supposed to be its primary operators.
What a complete Arabic-language configuration requires
Bilingual dimension metadata. Every dimension in the system — entities, accounts, cost centres, scenarios, time periods — needs to carry both English and Arabic labels. The English labels serve the technical configuration and the international reporting layer. The Arabic labels serve the local users, the local regulators, and the Arabic-language reports that the business produces. Setting up bilingual metadata requires a structured mapping exercise, not an afterthought at the end of implementation.
Right-to-left interface configuration. Oracle EPM’s web interface supports right-to-left rendering for Arabic-language users. This applies to data entry forms, workflow screens, and the navigation structure. Configuring this correctly — so that Arabic text appears correctly, mixed Arabic and English content displays without alignment errors, and numeric data appears in the correct position — requires specific setup that is separate from the functional configuration of the planning model.
Arabic report templates. Management reports and regulatory submissions produced from the EPM system need to display correctly in Arabic. This means report templates designed for right-to-left layout, with account labels in Arabic, and with the number formatting conventions that local regulatory requirements specify. A report template designed for an English-language output cannot simply be translated — it needs to be rebuilt for the Arabic-language layout.
Hijri calendar support where required. Saudi Arabia’s statutory financial reporting requirements reference the Hijri calendar in specific regulatory submissions. For organizations subject to SOCPA requirements or submitting to Saudi regulatory bodies, the EPM system needs to be able to generate outputs with Hijri dates correctly applied. This is a configuration that requires explicit setup and is missed in almost every implementation not delivered by a team with direct Saudi regulatory experience.
Arabic data entry validation. When users enter data, notes, or commentary in Arabic — in budget justification fields, forecast assumption notes, or management commentary — the system needs to handle Arabic-language text input without encoding errors and without truncating text that contains Arabic characters. Validating this in the test phase, rather than discovering it in production, requires Arabic-language test scripts — which most implementation teams do not prepare.
The training and adoption dimension
A finance team operating in Arabic and trained to use a system configured in English will adopt that system slowly and incompletely. The training materials, user guides, and support documentation all need to be in Arabic if the adoption target is Arabic-speaking users.
This is obvious in principle and consistently overlooked in practice. Implementation teams produce English-language training documentation because that is what they produce for every implementation. The Arabic-language version — if it exists at all — is a translation, not a document written for the user’s actual working context.
The organizations that reach the highest adoption levels among Arabic-speaking finance teams are those that invested in Arabic-language training materials built around the specific workflows their teams perform — not translated versions of generic system training guides.
What to check in your current implementation
If your organization is running Oracle EPM in the GCC and the system is primarily configured in English, the questions worth asking are: which of the Arabic-language capabilities listed above are currently configured, which ones matter for your specific regulatory and reporting requirements, and what would it take to complete the configuration that was not done at go-live?
In most cases, completing Arabic-language configuration is a targeted project — not a reimplementation. The functional configuration of the planning model or consolidation engine does not need to change. The language layer needs to be built on top of what already exists.
Loop Wise Solutions configures Oracle EPM environments for Arabic-language operation across the GCC, with direct experience in Saudi SOCPA requirements, Hijri calendar integration, and bilingual dimension metadata.
Contact: epm@loop-wise.com | www.loop-wise.com
