You are an Oracle EDM Cloud Consultant engaged by a mid-size financial services firm (Meridian Financial Group) to lead their migration from on-premise Oracle EDM (Primous) to Oracle EDM Cloud.
Meridian Financial Group is a diversified financial services company with operations across commercial banking, wealth management, and insurance. They have used on-premise Oracle EDM (Primous) for the past 8 years to manage their master data hierarchies — primarily the Chart of Accounts (CoA) hierarchy and the Entity/Legal Entity hierarchy. These hierarchies feed directly into Oracle FCCS (Financial Consolidation and Close Service) for their monthly and quarterly financial close process.
Meridian needs to migrate from on-premise Primous to Oracle EDM Cloud while maintaining uninterrupted financial close operations. Key constraints:
You have been brought in as the Oracle EDM Cloud Consultant to lead this migration end-to-end. Meridian's internal team has Oracle EPM experience but limited EDM Cloud-specific knowledge. They are relying on you for:
Honor these constraints in your deliverables. They reflect Meridian's real operating environment.
Meridian's Chart of Accounts and Entity hierarchies feed directly into Oracle FCCS for financial consolidation. Any hierarchy change in EDM must be validated against FCCS mapping requirements before going live. You cannot treat EDM as a standalone system — every configuration and migration decision must account for downstream FCCS impact.
Meridian's data governance team requires all hierarchy changes to go through a formal approval workflow:
Request → Review → Approve → Publish
The migration cannot bypass existing governance processes. Your EDM Cloud solution must replicate or improve the current approval workflow — not eliminate it.
| Phase | Weeks | Activities |
|---|---|---|
| Analysis & Design | 1–4 | Requirements gathering, current-state assessment, EDM Cloud design |
| Migration Execution | 5–8 | Data migration, configuration build, integration setup |
| Testing & Stabilization | 9–12 | UAT, parallel validation, go-live readiness |
| Fiscal Year-End Close | 14+ | No buffer — migration must be complete |
There is no buffer. Your plan must be scoped to fit this window — if something cannot be completed in 12 weeks, explicitly state what gets deferred and why.
The Primous environment contains 90+ quarterly hierarchy snapshots spanning 6+ years. Migrating all versions to EDM Cloud is neither required nor practical. You must define:
Design an Oracle EDM Cloud configuration with production-grade governance controls for a financial services hierarchy
Build a 12-week migration plan from Primous to EDM Cloud that maintains FCCS integration continuity
Define a versioning and archival strategy for 90+ historical hierarchy snapshots under regulatory requirements
Communicate migration impacts to technically diverse business stakeholders
Demonstrate critical evaluation and iterative use of AI tools in an Oracle EDM context
On this page
