Oracle EDM June 2026: What's New and Why It Matters for Your Business

Oracle released 12 enhancements to Enterprise Data Management in the June 2026 update. I've gone through all of them — not just what they do technically, but what they actually mean for the business users, data stewards, and finance teams who rely on EDM every day.

Some of these will change how end users interact with the system entirely. Others are quality-of-life improvements that save time in ways that quietly add up. Here's my take on all of them.

Change Management AI Assistant

Who benefits most: Data stewards, finance users, anyone who finds EDM's interface intimidating

This is the feature most end users will notice first, and it's worth spending time on.

Imagine a finance manager needs to update the cost centre property across 50 members because of a restructure. Today, that means logging into EDM, building filters, selecting members one by one or writing an expression, and submitting a request — a process that usually requires IT or a power user to do it right.

With the Change Management AI Assistant, that same finance manager can click "Ask Oracle" and type: "Update the cost centre property to CC-104 for all members under the APAC Sales hierarchy." EDM generates the request automatically. The user reviews it, confirms, and submits.

That's a meaningful shift in who can actually use EDM independently versus who has to rely on a consultant or IT team for routine changes.

Beyond bulk updates, the assistant also lets users:

• Query data in plain language — "Show me all accounts where the account type is Revenue and the posting type is blank"
• Explore node history — "What changes were made to this cost centre in the last 30 days?"
• Review open requests — "What requests are waiting for my approval?"

My honest take: The potential here is real, especially for organisations where EDM adoption has been limited because the interface feels complex to non-technical users. That said, AI making bulk changes to master data requires careful review — a misunderstood prompt could update the wrong set of members. The fact that it's optional and must be enabled in settings is the right call. I'd treat this as a tool for empowered users with good data literacy, not a free-for-all for everyone. Test it thoroughly in a non-production environment with realistic scenarios before rolling it out.

Granular Templates for Metadata Migration

Who benefits most: IT teams, EDM administrators, implementation teams

Here's a scenario I see constantly: a new custom validation has been built and tested in the Dev environment and needs to go to Production. The only way to move it? Export the entire application and import it — which means coordinating a full environment migration just to push one change.

Granular templates solve this. You can now select exactly which artifacts you want to migrate — just that one custom validation, or a handful of new extracts, or a set of updated policies — export them as a template file, and import only those artifacts into the target environment.

What this means in practice:

• Faster deployments — no more waiting for a full migration window to push a small change
• Less risk — moving only what changed means less chance of overwriting something in the target environment unintentionally
• More agile governance — IT teams can respond to business requests faster without big change management overhead

Supported artifact types: Custom Validations, Extracts, Extract Packages, Global Connections, Lookup Sets, Policies, Properties, Subscriptions.

If you manage multiple EDM environments, this changes your deployment process for the better.

External Custom Validations

Who benefits most: Governance teams, compliance officers, data stewards

Think about a rule like this: "A cost centre should not be deleted from EDM if it still has open purchase orders in the ERP system."

That sounds like a perfectly reasonable governance rule. But until now, EDM had no way to enforce it — because the data to check that condition lives outside of EDM, in an ERP system. Workarounds meant manual checks, or a downstream reconciliation after the fact.

External custom validations change this. When a user submits a request in EDM — say, to delete a cost centre — EDM can now call an external system via API to validate that change before it's approved. If the ERP reports open purchase orders against that cost centre, EDM returns an error to the user right there in the request workflow.

Business impact: governance rules that were previously enforced manually (or not at all) can now be automated and enforced at the point of change. For compliance-heavy organisations, this is significant.

Technical note: the external system needs to expose a REST API endpoint conforming to Oracle's specification. There's integration work involved, so this isn't a day-one feature for most environments — but for clients with mature API infrastructure, it's worth scoping.

Cross-Application Support for Node and Node List Properties

Who benefits most: Finance teams, data architects, anyone managing shared master data across multiple applications

Here's a common EDM scenario: you have a Chart of Accounts application and a Cost Centre application. A property on cost centres needs to reference a specific account — but because those lived in separate applications, you couldn't create a direct link. The workaround was to sync accounts into the cost centre application via subscriptions just to make them referenceable. More complexity, more maintenance.

That workaround is now gone. Node and Node List properties can reference data in a completely different application directly. You configure which application and dimension to reference in the property settings, and EDM handles the rest.

What this means for the business: data relationships that mirror how your organisation actually works — accounts linked to cost centres, entities linked to projects — can now be modelled cleanly in EDM without architectural gymnastics. Cleaner data model, easier to maintain, fewer moving parts.

Download Match and Deduplicate Results to File

Who benefits most: Data quality teams, data stewards, business stakeholders reviewing duplicates

When you run a deduplication exercise in EDM — say, identifying duplicate vendor records or consolidating cost centre hierarchies after a merger — the results often run into hundreds or thousands of matches to review.

Working through that volume in the EDM UI is painful. Sharing results with a business stakeholder who needs to sign off on which duplicates to merge? Even harder.

Now you can download the full result set to a file. Each row shows the matching node names, the property values compared, the match status, which rule triggered the match, and the match score. Take it to Excel, filter it, share it with whoever needs to review it, annotate it, bring it back.

A simple addition that makes data quality projects considerably more manageable.

Viewpoint Download in Visualized Request State

Who benefits most: Business approvers, change management teams, anyone reviewing hierarchy changes offline

Hierarchy change requests in EDM are easy to review inside the application — nodes that are being added, moved, or deleted are visually highlighted. But the moment you download a viewpoint to share with a business approver who isn't in EDM, that visual context disappears. You're left with a flat spreadsheet.

This feature brings the visualization into the download. When you export a viewpoint containing pending request items, the Excel file now color-codes each row the same way EDM does — additions in one color, deletions in another, property updates called out clearly.

For organisations where business approvers review hierarchy changes outside the system (which is common), this makes offline review actually meaningful rather than just a data dump.

Filter Compared Properties to Differences Only

Who benefits most: Data stewards, migration teams, anyone doing hierarchy reconciliation

When you're comparing two viewpoints side by side in EDM — say, comparing a Planning hierarchy against a source GL hierarchy to spot gaps — the Properties pane shows all common properties between the two. If a dimension has 30+ properties and you're looking for discrepancies, scrolling through all of them to find the ones that differ is tedious.

A new filter button now shows only the properties that are different. Toggle it on and the noise disappears — you see only what needs attention.

Small change. Real time saving on any reconciliation or alignment project.

Expression Engine: Distinct and Sort for String Lists

Who benefits most: EDM administrators, technical implementers

Business problem it solves: derived properties that pull values from multiple sources sometimes return duplicate or unordered values, making the output messy and unreliable for downstream use.

Two new methods — Distinct (removes duplicates) and Sort (orders values ascending or descending) — clean this up directly in the expression. No more workaround expressions to strip duplicates or reorder values manually.

If you have derived properties feeding downstream extracts or integrations, this means cleaner, more predictable output with less expression complexity to maintain.

Expression Engine: Find Method and List Property for Descendants

Who benefits most: EDM administrators, implementers building hierarchy-aware logic

Business problem it solves: sometimes a property value or validation on a parent node needs to depend on what exists in its subtree. For example: a department node should be flagged as "active" only if it has at least one active cost centre beneath it.

The new Find method on the Descendants collection makes this possible — search a node's descendants for members meeting specific criteria, and use that result in derived properties or custom validations.

List data type properties are also now fully supported when working with Descendants, closing a gap that previously limited what hierarchy-aware expressions could evaluate.

Data Chain Columns for System Event Audit

Who benefits most: Auditors, EDM administrators, compliance teams

Business problem it solves: after a metadata migration (especially with the new granular templates), it can be hard to trace exactly which part of which application was affected by a specific import event.

Four new columns in the System Event Audit screen — Application, Dimension, Node Type, Hierarchy Set — are now populated for data chain events. After an import, you can see at a glance exactly what was touched and where.

For audit and compliance purposes, this makes post-migration traceability much cleaner.

Viewpoint Chart Display Improvements

Who benefits most: Anyone who manages hierarchies using chart view

Business problem it solves: when adding multiple child nodes to a parent in chart display, the view would shift focus to each new child as it was added — making it disorienting to add a set of siblings.

Now child nodes appear below the centered parent instead of displacing it. The parent stays in focus while you work. The chart is also more compact, with the centered node easier to identify visually.

A UX improvement rather than a functional one, but the kind of thing that matters when you're doing a lot of hierarchy building.

Additional FX Source Movement Properties for Tax Reporting

Who benefits most: Tax Reporting application users, finance teams managing FX translation

Business problem it solves: Tax Reporting applications need to manage how foreign exchange rates are applied when translating movements. Two new properties on the Movement dimension — Is FX Source Rate Movement and FX Source Rate Movement — give administrators the control to specify which source movement to use for FX rate translation.

A built-in validation also prevents conflicting FX settings from being configured simultaneously, catching a potential misconfiguration before it affects translation results.

If you're running Tax Reporting, check your Movement dimension registrations — these properties are added automatically for new registrations and available when modifying existing ones.

My Summary

The three features I'd prioritise exploring first are the AI Assistant, External Custom Validations, and Granular Templates — they represent the biggest shift in what's possible in EDM, both for end users and for the teams who implement and maintain it.

What's caught your attention from this release? Always happy to discuss — drop a comment or get in touch.