Oracle EDM Cloud Consultant Skills Challenge
Oracle EDM Cloud Migration — Meridian Financial Group Engagement Overview 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…
Create a free account to upload your work. Your progress saves as a draft until you submit.
What You'll Be Doing
Oracle EDM Cloud Migration — Meridian Financial Group
Engagement Overview
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.
Background
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.
Current State
- On-premise Oracle EDM (Primous) manages two primary hierarchies:
- Chart of Accounts — ~4,200 nodes across 8 segments
- Entity — ~320 legal entities across 12 countries
- EDM hierarchies are the single source of truth for FCCS — any change to a CoA node or entity mapping in EDM flows downstream to FCCS consolidation rules, intercompany eliminations, and regulatory reporting
- The current Primous environment contains 6+ years of hierarchy versions (quarterly snapshots) — approximately 90 versioned hierarchy snapshots total
- Three business teams interact with EDM daily:
- Corporate Accounting (CoA changes)
- Treasury (entity/legal entity changes)
- Financial Planning (hierarchy views for PBCS budgeting)
- The on-premise infrastructure is end-of-life — Meridian's Oracle license renewal requires cloud migration by Q1 of next fiscal year
The Problem
Meridian needs to migrate from on-premise Primous to Oracle EDM Cloud while maintaining uninterrupted financial close operations. Key constraints:
- Migration window: 12 weeks
- Fiscal year-end close begins: Week 14 — there is no room for slippage
- The migration must preserve data accuracy, maintain governance workflows, and ensure FCCS continues to receive correct hierarchy data throughout the transition
Your Role
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:
- The technical migration plan
- The EDM Cloud configuration design
- Stakeholder coordination through go-live
Constraints
Honor these constraints in your deliverables. They reflect Meridian's real operating environment.
FCCS Dependency
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.
Governance Workflow
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.
12-Week Migration Window
| 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.
Historical Versioning
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:
- What migrates vs. what gets archived
- A rationale that accounts for both business continuity and regulatory audit requirements in a financial services context
What You'll Accomplish
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
How Your Work Will Be Scored
What to Submit
Migration & Configuration Plan
Format: .pdf, .doc, .docx, .rtf, .txt, .md
Deliverable Requirements
Produce a structured document covering the four areas below.
1. EDM Cloud Configuration Design
Define the node types, views, and validation rules you would configure in Oracle EDM Cloud for Meridian's Chart of Accounts hierarchy. Your response must address:
- The proposed EDM Cloud structure and why you designed it this way
- What governance controls are built into the configuration
- How this design differs from the existing on-premise Primous configuration
2. Migration Approach
Outline your end-to-end migration plan from Primous to EDM Cloud within the 12-week window. Your plan must cover:
- Data extraction strategy — how data is extracted from Primous
- Transformation and mapping approach — how on-premise structures are mapped to EDM Cloud equivalents
- Data validation and reconciliation checkpoints — how accuracy is confirmed at each stage
- Phasing across the three migration stages:
| Stage | Weeks | Focus |
|---|---|---|
| Analysis & Design | 1–4 | — |
| Execution | 5–8 | — |
| Testing & Stabilization | 9–12 | — |
3. FCCS Integration Continuity
Explain how you will ensure FCCS continues to receive accurate hierarchy data during and after migration. Your response must address:
- Cutover approach — parallel run, big bang, or phased — and your rationale for the chosen approach
- In-flight hierarchy changes — how change requests are handled during the migration window without disrupting FCCS
- Post-migration reconciliation — what checks you perform to confirm FCCS mapping integrity after go-live
4. Versioning & Archival Strategy
The Primous environment contains 90+ quarterly hierarchy snapshots spanning 6+ years. Define:
- What migrates to EDM Cloud vs. what gets archived
- The rationale driving those decisions, with specific reference to:
- Business continuity requirements
- Regulatory audit requirements applicable to a financial services firm
Sign in to upload files
README Document with Sections A, B, and C
Format: .pdf, .doc, .docx, .rtf, .txt, .md
Evaluation Criteria
Section A — Migration Risk Assessment
300–500 words
Identify the top 3–5 risks to this migration and explain how you would mitigate each. For each risk, address three things:
- What could go wrong
- How you would detect it
- What your contingency is
Consider risks across the following areas:
- Data integrity during extraction and load
- FCCS disruption during cutover
- Governance workflow gaps during transition
- Stakeholder resistance to cloud adoption
- Timeline risk given the fiscal year-end deadline
Section B — Stakeholder Communication & Knowledge Transfer Plan
Three business teams interact with EDM daily, each with different needs and different levels of technical sophistication:
| Team | Primary EDM Activity |
|---|---|
| Corporate Accounting | CoA changes |
| Treasury | Entity / legal entity changes |
| Financial Planning | Hierarchy views for PBCS budgeting |
Part 1 — Stakeholder Communication
For each of the three teams, describe:
- What information they need about the migration timeline, impacts, and required actions
- When they need it
- What format and communication channel works best for their audience
Part 2 — Knowledge Transfer Plan
Outline how Meridian's internal team will be able to operate EDM Cloud independently after your engagement ends. Address:
- What documentation you create
- What training you provide
- How you confirm the team is ready before you disengage
Section C — AI Usage Log (Mandatory)
This is not a trick. We want to see how you work with AI — not whether you used it.
In a short section of your submission, document your AI collaboration process. For each significant interaction with an AI tool, briefly note:
- What you asked the AI to help with
- What it gave you
- What you kept, changed, or rejected — and why
Three interactions documented is sufficient. The log does not need to be exhaustive.
Sign in to upload files
Video Walkthrough
Format: .pdf, .doc, .docx, .rtf, .txt, .md
Video Walkthrough
Record your walkthrough as an MP4 or MOV file and upload it directly on the Provn platform as a separate file.
Structure & Time Targets
1. Summary (~60 seconds)
The migration challenge and your recommended approach — explain it as if you were briefing Meridian's CFO and CIO together.
2. Configuration Walkthrough (~2–3 minutes)
Walk through your EDM Cloud configuration design. Cover:
- Your key design decisions for node types, views, and validations
- Why you structured them the way you did
- What trade-offs you made
3. Migration & Risk Walkthrough (~1–2 minutes)
Walk through your migration approach and the risks you identified. Address:
- What is the single biggest risk to this migration?
- How would you mitigate it?
4. Mandatory AI Question (~1–2 minutes)
Walk through one moment where you disagreed with, pushed back on, or redirected what the AI gave you — and what you did instead. Your response must:
- Name the specific moment
- Explain what the AI produced that did not meet the bar
- Explain what you did differently, and why
5. Reflection (~30–60 seconds)
- What would you do differently with more time?
- What would you want to validate with Meridian's team before executing this plan?
Communication Note
Speak naturally. Communication is assessed on clarity of technical ideas, ability to explain Oracle EDM concepts to a mixed business/technical audience, and structured stakeholder awareness — not verbal polish, accent, or filler words.
Sign in to upload files
Create a free account to upload your work. Your progress saves as a draft until you submit.
On this page