Oracle EPM Cloud · Spine
Data Management to Data Integration, the map
Oracle has been retiring Data Management piece by piece since 2023, and the loudest complaint in the forums is simply not knowing where things went. This page is the map: what moved, when, and where it lives now.
◆ The handover, in order— the dates that matter, verified against Oracle's update notes.
| When | What changed |
|---|---|
| March and July 2023 | The first configuration items became Data Integration only, period mapping among them. The quiet start of the retirement. |
| June 2023 | Pipeline shipped as the replacement for Data Management's Batch, and made Oracle's own Spotlight list for the year. Existing batches migrate to Pipelines automatically. |
| September 2024 | The Data Management scheduler was deprecated. The EPM Platform Job Scheduler replaces it, with a migration utility that moves integration, batch, and maintenance schedules, in preview mode first if you want to see before you leap. Profitability and Account Reconciliation are excluded; Account Reconciliation schedules through EPM Automate or REST instead. |
| May 2025 | Copy Pipeline arrived, whole pipelines duplicated for reuse across cases and environments. |
| August 2025 | Pipelines reached Account Reconciliation, importing balances and creating reconciliations as pipeline jobs. |
| Now | Load rules, mappings, and the workbench exist in both places, but every new capability since has landed in Data Integration only. The full switch is a matter of when, not if. |
◆ Where things live now— the old name, the new home, and the catch.
| You are looking for | Where it went, and the catch |
|---|---|
| Data Management itself | Data Integration, under the Data Exchange task. The same objects are there, load rules, mappings, source and target applications, wearing a newer interface. |
| Batch | Pipeline. Stages hold jobs, jobs can run in parallel inside a stage, variables carry period and mode at runtime, and each run can email its status with the logs attached. Batches migrate automatically. |
| The scheduler | The EPM Platform Job Scheduler console. The catch that fills the forums: schedules built in old Data Management do not show in the Jobs console, they look like they vanished. They did not; run the migration utility and they appear where everything else runs. |
| Script orchestration | Increasingly, Pipelines. A pipeline chains loads, clears, and business rules with their parameters in one named unit, callable as one command, runPipeline, or one REST call. Less glue script, fewer places for logic to hide. |
| runDataRule in old scripts | runIntegration, or a pipeline. Both belong to the current framework, and both sidestep the old command's missing process identifier. |
| Full workflow mode habits | Unchanged location, same old trap: full workflow archives every run into staging tables that bloat the application. Simple mode plus periodic cleanup, unless you truly need the drill trail. |
For extraction to a warehouse, none of this changes the recommended path: named export jobs called on a schedule, the extraction pattern as written. Pipelines earn their place on the load and orchestration side, where they genuinely retire glue scripts. Dates and behavior verified against Oracle's update notes and current documentation, July 2026.
Sitting on old Data Management automation?
We map what you have, migrate the schedules, rebuild the batches as pipelines, and hand over a runbook, before Oracle's calendar decides for you.
Terms on this page
- Data Exchange
- The task card where Data Integration lives.
- Pipeline
- A named chain of integration jobs in stages. The Batch replacement, and the current orchestration unit.
- Platform Job Scheduler
- The one console where schedules now run. Old Data Management schedules must be migrated into it.
- migration utility
- Oracle's tool that moves old schedules across, with a preview mode. Found in maintenance tasks.
- full workflow mode
- The archive-everything integration mode. The staging bloat trap survived the rename.