Objective
Design dimension governance so values and hierarchies stay consistent across finance systems.
Case study 16
Portfolio knowledge project
EDM Dimension Governance Model
Enterprise dimension governance for CoA and EPM — request workflows, hierarchy ownership, validation rules, and sync checkpoints across Fusion and EPM Cloud.
Knowledge / portfolio case study only. Not employment history, not a named client engagement, and not a certification claim.
Context
When dimensions drift between GL and EPM, plans and actuals stop aligning.
Scope
Request-to-publish workflow, owner model, validation rules, and sync checkpoints.
Approach
Define dimensions in scope → assign owners → design request form → set validations → publish cadence → verify consumers (GL/EPM).
- 01Dimension inventoryWhat must be governed.
- 02Ownership modelBusiness + finance owners.
- 03Workflow designRequest, validate, approve, publish.
- 04Validation rulesFormat, hierarchy, duplicates.
- 05Consumer syncGL/EPM confirmation.
01Dimension
02Ownership model
03Workflow design
04Validation rules
EDM Dimension Governance Model
Key design decisions
- One master for shared dimensions
- EDM as control point.
- Publish on a known cadence
- Reduce surprise breaks.
- Reject incomplete hierarchy parents
- Protect rollups.
Walkthrough
Request new cost center → validate → approve → publish → confirm availability in GL and planning.
Controls
No direct rogue values in consumers; every change has requester + approver; hierarchy orphans blocked.
Oracle modules in focus
EDM
GL
EPBCS
FCCS
Deliverables
Dimension owner matrix
request workflow
validation catalog
sync checklist.
Outcomes
Demonstrates cross-system dimension discipline for Fusion + EPM.