Retiring DRM Without Losing History: Why This EDMCS Idea Matters (and Needs Your Vote)

One of the most common conversations I have with clients migrating from Oracle Data Relationship Management (DRM) to Enterprise Data Management Cloud Service (EDMCS) isn’t about current hierarchies.

It’s about history.

Specifically:

“How do we retain years of historical DRM versions for audit, compliance, and comparison — without keeping DRM alive forever?”

Right now, that answer is… complicated.

---

The Gap Today: Historical DRM Versions vs. EDMCS Time Awareness

EDMCS already has strong native concepts around time labels and time-labeled viewpoints. These are designed exactly for “as-of” analysis and point-in-time comparison.

What’s missing is a first-class, supported way to load historical DRM Versions into EDMCS and bind them to date-based time labels.

During a DRM → EDMCS migration, teams often have:

• Multiple “final” DRM versions per fiscal year

• Regulatory or audit requirements to retain those versions

• A desire to fully decommission DRM once EDMCS is live

Without this capability, customers are forced into:

• Parallel systems (keeping DRM alive “just in case”)

• Custom archival solutions

• Manual exports stored outside governed EDMCS structures

That defeats the purpose of consolidating governance into EDMCS.

---

The Idea: Date-Based Time Labels for Historical Loads

This Idea Lab proposal introduces a clean, native pattern:

• Each historical DRM Version is loaded into EDMCS

• Each load is assigned a specific, date-based time label

• All versions coexist in a single EDMCS application and data chain

Example

• DRM Version FY2020_Final → Time Label 2020-12-31

• DRM Version FY2021_Final → Time Label 2021-12-31

From there, EDMCS can do what it already does best:

• Point-in-time hierarchy comparisons

• “As-of” structure analysis

• Governed access to historical master data

All without custom workarounds.

---

Why This Is Bigger Than Migration

This isn’t just about getting off DRM.

This capability supports:

• Audit and regulatory compliance

• Restatements and historical financial reporting

• M&A pre- and post-transaction analysis

• Long-term reference data retention

• True lineage across time — not just current state

It establishes EDMCS as the system of record for both current and historical hierarchies, not just the present moment.

---

Oracle Has Already Acknowledged Feasibility

This isn’t a blue-sky idea.

Oracle product management has already responded that this enhancement is:

“Potentially feasible with sufficient guardrails in place”
and is being evaluated for a future release.

That matters.

Ideas with:

• Clear use cases

• Multiple customer confirmations

• Product team engagement

…are exactly the ones that move forward — if the community shows demand.

---

👉 Take Action: Vote and Comment in Idea Lab

If you:

• Are migrating from DRM to EDMCS

• Need to retain historical versions for audit or compliance

• Want to fully retire DRM without losing access to the past

• Believe EDMCS should be the authoritative, time-aware source for master data

Please take 30 seconds to help move this forward:

🔗 Vote and comment on the Idea Lab entry:
https://community.oracle.com/CustomerConnect/discussion/933008/support-loading-historical-drm-versions-into-edmcs-using-date-based-time-labels

Even a short comment like “We need this for our DRM decommissioning roadmap” helps establish real customer demand.

Oracle looks closely at votes, comments, and customer breadth when prioritizing roadmap decisions.

Let’s make sure this one gets the visibility it deserves.

 

Restoring Oracle EPM Backups: From Customer-Managed Workarounds to Platform-Native Recovery

By Consilium Technology — Oracle ACE Perspective

---

Why Backup Restore Matters (More Than You Think)

In Oracle EPM Cloud, backups are not about convenience — they are about risk containment, recovery time, and operational credibility. When something goes wrong in PROD, the difference between a clean restore and a scramble often comes down to how much of the process is manual versus platform-managed.

For years, EPM administrators filled gaps with custom processes. Those processes worked — but they also carried friction, fragility, and unnecessary risk.

Oracle’s newer Oracle-managed backup restore capability marks a clear inflection point: restore is no longer a file logistics problem, it is a platform operation.

---

The Legacy Model: Customer-Managed Backup Plumbing

What We Used to Do

Before Oracle exposed native restore access to its nightly backups, customers were forced into a familiar pattern:

1. Generate or capture a snapshot in the EPM environment

2. Rename it to prevent overwrite

3. Copy it out of the Oracle Cloud environment

4. Store it in:

   • Oracle Object Storage, or

   • An on-premises file server

5. Maintain retention, cleanup, and monitoring manually

This approach wasn’t optional — it was the only way to guarantee a restorable point-in-time artifact.

Restoring Under the Legacy Model

When a restore was required:

1. Identify the correct backup file externally

2. Copy it back into the EPM environment

3. Initiate restore

4. Import the snapshot into the application

Every step introduced latency and risk. The restore itself was rarely the problem — getting the right file to the right place at the right time was.

---

The Modern Model: Oracle-Managed Backups, Oracle-Managed Restore

Oracle now exposes backups it already takes as part of nightly maintenance and allows customers to restore directly from those artifacts.

This fundamentally changes the operating model:

• No customer-managed storage

• No file movement

• No renaming conventions

• No staging failures

Backups are identified purely by timestamp and restored through supported APIs or EPM Automate.

---

How the New Restore Flow Works

1) List Oracle-Managed Backups

GET /interop/rest/v2/backups/list

Oracle returns a canonical list of available backups, for example:

2026-01-27T08:56:03/Artifact_Snapshot.zip

This value — timestamp and all — becomes the authoritative restore key.

---

2) Restore a Specific Backup

POST /interop/rest/v2/backups/restore

{
  "backupName": "2026-01-27T08:56:03/Artifact_Snapshot.zip",
  "parameters": {
    "targetName": "Restored_Artifact_Snapshot_012726"
  }
}

Oracle restores the snapshot directly into the environment. No intermediate handling required.

---

Understanding the Restore Response (This Is Critical)

A successful restore request commonly returns:

• HTTP 200 OK

• A response payload showing:

  "status": -1
  

This is expected behavior, not an error.

In Oracle EPM REST semantics:

• status = -1 → Job accepted and running asynchronously

• status = 0 → Synchronous success (rare for restores)

Restore operations are intentionally asynchronous. Oracle queues the job and executes it safely in the background.

The response includes a Job Status link:

GET /interop/rest/v2/status/jobs/{jobId}

This endpoint governs the restore lifecycle.

---

Operational Reality: Job-Driven Restore

A production-grade restore process must:

1. Capture the returned job ID

2. Poll job status

3. Wait for COMPLETED

4. Only then proceed to snapshot import

This is not overhead — it is platform protection.

Large snapshots, shared infrastructure, and uptime guarantees demand controlled execution.

---

Where EPM Automate Fits

EPM Automate follows the same architectural model:

• Discover backups

• Reference the exact timestamp

• Trigger restore

• Monitor job status

• Import snapshot

The tooling differs, but the contract does not.

---

Why This Is a Meaningful Shift

From an architecture and governance perspective, Oracle-managed restore delivers:

• Lower operational risk

• Faster recovery times

• Cleaner automation

• Fewer human failure points

• Clear separation of responsibility

Most importantly, it eliminates an entire class of customer-built plumbing that never should have existed in a managed cloud service.

---

Final Thought (Oracle ACE Perspective)

The legacy backup process was never a best practice — it was a workaround.

Oracle-managed backup restore is what a mature cloud platform should look like:

• Native

• Auditable

• Automated

• Safe

If your organization is still copying snapshots out and back in “just in case,” it’s time to retire that pattern and align with the platform you’re actually paying for.

Less plumbing. More confidence.

Keeping EPM Automate Running Smoothly: What's Up with Monthly Updates & This Big Java Change Coming in August 2025!

If you're using Oracle's EPM Cloud, you probably know EPM Automate is a super handy tool for automating all sorts of tasks. And just like any important piece of your toolkit, keeping it in good shape is key. That's where those monthly updates come in – they're more than just a notification in your inbox.

I've talked before about why it's a good idea to update EPM Automate every month – think new features, fixing those annoying bugs, and making sure everything is secure and stable. Today, I'm diving into a pretty significant tech change from Oracle that really highlights why staying updated is so important: EPM Automate is getting a Java upgrade!

Big News: Java 17 is Coming to EPM Automate!

Starting with the EPM Automate August 2025 update (version 25.08), Oracle is moving away from Java 8 and will be using Java 17 for EPM Automate.

This is a pretty notable shift under the hood for the utility. So, why the change?

• Better Security: Java 17 is a Long-Term Support (LTS) version, which means it gets regular security patches and updates. This makes it a more secure base for EPM Automate compared to older Java 8.
• Improved Performance & New Stuff: Newer versions of Java bring performance improvements and new capabilities that Oracle can use to make EPM Automate even better down the line.
• Staying Up-to-Date: As older tech reaches its end of life, it's important for tools like EPM Automate to evolve to keep things stable and compatible.

What This Java Update Means for You (Especially if You're Automating EDMCS Stuff)

Okay, let's get down to how this affects you. The impact of this Java upgrade on your EPM Automate setup depends on where you're running it:

• Windows Users: Good news! If you're running EPM Automate on a Windows machine, you probably won't need to do anything special with this Java change. The EPM Automate installer for Windows usually includes the Java it needs. So, when you update to 25.08, it should handle the Java 17 thing automatically.
• Linux/UNIX Users: Heads up! This will require a bit of action on your part. EPM Automate on Linux and UNIX systems uses the Java version you've installed. To keep using EPM Automate 25.08 (and later), you needto make sure Java 17 is installed on your Linux/UNIX environment. If not, your EPM Automate scripts won't run.

A Closer Look for Our EDMCS Automation Folks:

If you're using Oracle Enterprise Data Management Cloud Service (EDMCS) and you're automating tasks with EPM Automate (like exporting/importing metadata, running validations, managing load files, etc.), here's what you should know:

• Remember, EPM Automate is a client-side tool. This Java update affects where your EPM Automate scripts run, not the EDMCS cloud service itself. EDMCS will keep doing its thing as usual.

• However, if you're using EPM Automate to automate EDMCS tasks, here's what you need to consider:

  • If You're Running Automation from Linux/UNIX:
    • Important Check: If your EPM Automate scripts that work with EDMCS are run from a Linux or UNIX server, the Java environment on that server is the one that needs to be updated to Java 17 before or when you update to EPM Automate 25.08.
    • No Changes Needed in EDMCS: You don't have to change anything inside your EDMCS application instances because of this EPM Automate client Java update.
    • Scripts Should Still Work: Your existing EPM Automate commands and scripts for EDMCS should continue to work, as long as the EPM Automate client itself is compatible with Java 17 (which version 25.08 will be) and your server has Java 17. The basic EPM Automate commands for EDMCS aren't changing because of this Java switch.
  • If You're Running Automation from Windows:
    • Should Be Smooth: As we mentioned, the EPM Automate installer for Windows should handle the Java 17 update. Your EDMCS automation scripts running from Windows machines should keep working after you update EPM Automate, without needing to install Java separately.
  • Testing is Key:
    • Whenever there's a change like this under the hood, even if it's mostly about the client tool's environment, it's always a good idea to test your EDMCS automation scripts in a non-production environment after you've updated EPM Automate (and your Java setup if you're on Linux/UNIX). This helps catch any unexpected issues with your specific scripts or setup early on.

  Basically, for EDMCS users, the main thing is to make sure the machine you're using to run EPM Automate to manage EDMCS is ready for Java 17, especially if it's a Linux/UNIX system.

What You Need To Do (Before August 2025):

1. Know Your EPM Automate Setup: Figure out where EPM Automate is installed and where your important scripts (including those for EDMCS) are run from.
2. Check Your Operating Systems:
   • Windows: Plan to update EPM Automate like you usually do.
   • Linux/UNIX: Start planning to install or upgrade to Java 17 on these machines before the EPM Automate 25.08 release. Keep an eye out for any specific Java 17 recommendations from Oracle.
3. Schedule Those Updates: Add the EPM Automate update and any needed Java environment updates to your maintenance schedule.
4. Test, Test, Test: After updating, thoroughly test your EPM Automate scripts, especially the ones that work with EDMCS, in a test environment first.

Why Monthly EPM Automate Updates Are a Big Deal (This Java Thing Shows You Why):

This upcoming Java 17 move is a perfect example of why Oracle really recommends keeping up with those monthly EPM Automate updates:

• Easier Transitions: Regular updates mean you're dealing with these behind-the-scenes tech changes bit by bit, instead of one big overhaul.
• Better Security Right Away: You're always getting the latest security improvements, like the ones that come with moving to a newer Java version.
• Keeps Everything Working Together: You make sure EPM Automate continues to work smoothly with your EPM Cloud services, including EDMCS, which also get updated regularly.
• Get the Latest Fixes and Features: You don't miss out on bug fixes or new things that could make your EDMCS automation or other EPM tasks easier.

Looking Ahead:

The move to Java 17 for EPM Automate is a positive step towards a more secure, modern, and efficient automation tool. By staying in the loop and keeping up with your monthly EPM Automate updates, you can make sure this change, and others down the road, go smoothly for your team and your important EPM processes, including your EDMCS work.

Keep an eye out for more info from Oracle as we get closer to August 2025!

Unleash the Power: EDM to EPM Dimension Loads Just Got a Turbo Boost! (No More Shared Member Nightmares!)

For years, the dance between Oracle Enterprise Data Management (EDM) and Enterprise Performance Management (EPM) administrators has been a delicate, sometimes awkward, tango. The culprit? Shared members and the dreaded 'CLEAR' versus 'MERGE' dilemma during dimension loads. We've all been there: the fear of locking up stored members, the heart-stopping moment when a crucial member vanishes, and the constant headache of managing alternate hierarchies.

But hold onto your hats, folks, because Oracle has just dropped a game-changing feature that's about to revolutionize how we handle dimension loads. Buried in the March 2025 EPM release notes (yes, you might have missed it!), lies a gem: the 'Clear Shared Members' option in metadata import files. (See the official docs here: https://docs.oracle.com/en/cloud/saas/readiness/epm/2025/epm-mar25/25mar-epm-wn-f37479.htm)

Why This Matters (and Why You Should Be Excited):

Historically, 'CLEAR' was the necessary evil for dealing with shared member movements and alternate hierarchies. 'MERGE' simply couldn't handle the dynamic shifts, leading to duplicate shares and a messy outline. But 'CLEAR' came with its own set of risks:

• Locked Members: Stored members tied to forms and business rules? Ouch.
• Data Loss: Accidentally wiping out members and the data they held. Double ouch.
• The Shared Member Shuffle: Moving shared members was a recipe for chaos.

The Game Changer:

This new 'Clear Shared Members' option changes everything. It's like having a surgical tool instead of a sledgehammer. Now, you can:

• Precisely Target Shared Members: Clear only the shared instances, leaving your stored members and critical data untouched.
• Effortlessly Manage Alternate Hierarchies: Move shared members without creating duplicates or causing outline inconsistencies.
• Say Goodbye to Anxiety: No more sweating over locked members or accidental deletions.

Imagine: A world where EDM and EPM administrators collaborate seamlessly, where dimension loads are smooth and predictable, and where shared member management is a breeze. That's the power of this new feature.

This isn't just an incremental improvement; it's a paradigm shift. We can finally embrace the 'CLEAR' functionality without the fear of collateral damage.

What are your thoughts? Are you as excited as I am about this game-changing update? Let's discuss in the comments below!"

Ability to sort Requests based on columns in the Request view - DELIVERED

 Oracle EDM Idea Lab post - DELIVERED

 

Ability to sort Requests based on columns in the Request view

 

Description (Required): 

We would like the ability to sort Requests by the columns provided in the request view. 

 

Use Case and Business Need (Required):

The business would like to be able to sort on the requests that return from a request filter by the request Title and Description (and other available columns) to better allow the review of in process, in flight and completed requests.

 

 

 

Delivered: https://docs.oracle.com/en/cloud/saas/readiness/epm/2024/edm-dec24/24dec-edmcs-wn-f36314.htm

 

Sort Listing Pages By Selected Column

Several pages in the Enterprise Data Management user interface now support sorting displayed items by a selected column. The table content can be sorted in ascending or descending order. The following pages can be custom sorted by a particular column:

• Views
• Request Activity
• Applications
• Node Types
• Hierarchy Sets
• Node Sets
• Properties
• Lookup Sets

Business Benefit: Listing pages in Enterprise Data Management can be custom sorted by a selected column to find particular items of interest.

 

Allow Blank Download of Lookup / Legacy GL Viewpoints - DELIVERED

 Oracle EDM Idea Lab post - DELIVERED

 

Allow Blank Download of Lookup / Legacy GL Viewpoints

 

 

Description (Required):

 

Need the ability to download viewpoints that are based on Lookup or Legacy GL Node types.

 

Use Case and Business Need (Required):

For users to easily have a format for running a LOAD to a Lookup or Legacy GL node type, we would like to have the ability to download the viewpoint with no data, just the column headers.

 

 

Delivered: https://docs.oracle.com/en/cloud/saas/readiness/epm/2024/edm-dec24/24dec-edmcs-wn-f36295.htm

 

Download Viewpoint Column Headers Only to File

When downloading a viewpoint to a file, you have the option to download only column headers for the viewpoint rather than all nodes, property values, and relationships in the viewpoint. The resulting output file provides a template for loading data into the viewpoint from a file.

Business Benefit: Users who need to load data into a viewpoint from an external file can easily download a template providing the appropriate file format.

 

Need Extract Package to combine files without placing them in zipped folder - DELIVERED

Oracle EDM Idea Lab post - DELIVERED

Need Extract Package to combine files without placing them in zipped folder

 

 

Description (Required):

We need to combine 2 or more extracts into a single file. Not in a zipped folder.

 

Use Case and Business Need (Required):

To support related value sets for the GL, we need to combine multiple extracts into a single text file and place it the default UCM folder.

 

Enhancement Request / Service Request: 

Currently extract packages force the combined files into a zip file. This is not an acceptable load format for the related value set import within Fusion GL. We need the option to run the package with a combined file and NOT embed it in a zipped file.

 

 

Delivered: https://docs.oracle.com/en/cloud/saas/readiness/epm/2024/edm-dec24/24dec-edmcs-wn-f36301.htm

 

Extract Package Option to Output Individual Files to Global Connection

An extract package which extracts data to a global connection can write individual extract files to the connection target rather than having the files bundled within a zip file. This capability prevents the need to unzip the extract files after writing them to the global connection. The Zip Package option can be disabled in the extract package to output individual files when extracting to a global connection.

Business Benefit: An extract package consisting of many extracts can be run in a single operation and the data files produced by the package can be individually written to a global connection target such as Oracle Cloud ERP, Oracle Cloud EPM, or Oracle Object Storage.