What does the EPM Automation Rebuild replace?

The scripts and scheduled jobs that load data and metadata into Oracle EPM Cloud, take backups, and run housekeeping. The existing setup is reviewed first, then replaced in full.

Does it only run overnight?

No. Runs follow a schedule you set: overnight, at set times through the day, or on demand from a guided menu or a one-click button.

Where does the new system run?

On an isolated server of your choice: a new virtual machine or an existing server. The old jobs keep running until you decide to switch.

How are passwords handled?

The password is typed once at setup and encrypted immediately. Plain text is never written to disk, a script, or a log, and the encrypted file only works for the service account that runs the jobs.

What happens if a source file is wrong or missing?

Every file is checked for layout, row count, and age before it loads. A bad or missing file stops the run cleanly, EPM keeps the previous day's good state, and the alert explains the problem and the fix.

Does it write directly to the EPM database?

No. Every load goes through Oracle's supported tools: EPM Automate and EPM jobs.

Which Oracle Cloud EPM business processes does it support?

Any business process loaded through EPM Automate, including Planning, Financial Consolidation and Close, and Account Reconciliation.

Who can run it after handover?

Your administrators. It runs under a service account rather than a person's login, and a new administrator can operate it from the guide on day one.

Services / EPM Automation Rebuild

Automation that protects EPM and explains itself, on any schedule.

Loads run overnight, through the day, or on demand. Every file is checked before it reaches EPM, the last good state is kept when something is wrong, and each run tells you in plain English what changed.

A proven Oracle EPM Cloud automation system, refined over thousands of hours across twenty client environments, fitted to yours. Years of scripts and workarounds are cleared away, leaving one clean system your team can sustain.

Price: $19,500 CAD; fixed, for the outcome
Runs: Any time; overnight, intraday, on demand
Server: Your choice; new VM or existing server
Switch-over: On your call; old jobs run until then

Is this where you are?

Scheduled jobs are a folder of batch scripts built up over years.
Server names, file paths, or passwords sit in plain text inside the scripts.
One person understands how the jobs run, and changing anything means editing code.
Failures come to light when Finance notices the numbers are wrong.
New members fail the load and are added by hand before a reload.
Backups depend on someone remembering to take them.
Data only refreshes overnight, because running loads during the day feels too risky.
A server move or a password change turns into a project.

What changes

Typical setup today

Batch scripts only their author could run.
Passwords in plain text.
Changes meant editing code.
Failures found by Finance.
Data refreshed once a night.
Backups when someone remembered.

After the rebuild

A guided service any administrator can operate.
Loads on any schedule: overnight, intraday, or on demand.
Credentials encrypted and never written in plain text.
Changes are a settings entry.
Problems reported with the fix, before Finance sees them.
A dated backup every night, with retention.

What you get

Passwords that are never exposed

The password is typed once at setup and encrypted on the spot. Plain text never reaches a disk, a script, or a log. The encrypted file is tied to the service account that runs the jobs, so a copy is useless anywhere else. Changing a password is a guided re-entry.

Guided screens for every task

Setup walks IT through each question (drive, environment, schedule, e-mail list, service account) and tests the connection before anything is scheduled. On-demand runs ask which environment and what to run, and confirm before starting. Common tasks are one click.

Folders and reports anyone can follow

Files, Logs, Reports, Backups, and Archive, with the engine kept out of the way. Reports say in plain English what was added, moved, or changed, and what to do when something needs attention.

Settings, not code

One settings file per server, so moving from Test to Production or to a new server is a settings change. One load table drives every load; adding a dimension is a new row.

EPM protected before anything loads

Every file is checked for layout, row count, and age first. A bad or missing file stops the run cleanly, and EPM keeps yesterday's good state. Members missing from the source are flagged, never silently deleted. Brief cloud interruptions get one automatic retry, and a run lock prevents overlapping jobs.

An audit trail and easy recovery

Every file loaded is archived by day, and each run reports only what changed, which gives you a change log. A dated EPM backup is taken nightly. Re-running one dimension after a fix is one click.

Alerts that name the fix

An e-mail after each run, or only when something needs attention. Alerts name the file, the problem, and the fix.

Any schedule, and new members placed on the next run

Runs are a schedule, so loads can run overnight, through the day, or on demand whenever Finance needs current numbers. New members are placed automatically on the next run. Anything that can't be placed lands in a holding parent Finance can see, so loads stop failing over missing members.

How the work runs

1.We review the existing system: every job, script, schedule, file, and dependency, what each one is for, and what can be retired.
2.We fit the proven system to your environment and build it in full on an isolated server: a new virtual machine or your existing server, your choice.
3.Old and new run side by side. You decide when to switch, and the old jobs keep running until you do.
4.We hand over the documentation and walk your administrators through it, so a new administrator can run it from the guide on day one.

What you receive

A complete automation system for your Oracle EPM Cloud loads, backups, and housekeeping, running under a service account on a schedule.
Duplicate, unused, and one-off jobs and scripts retired, so there is far less to maintain.
A README and an operating guide written for your administrators, not for the developer.
Encrypted credentials, file checks, retries, run locks, and nightly backups in place from the first run.
Plain-English run reports and alerts, sent to the people you choose.
A walkthrough with your team, and a switch-over on the date you choose.

Price

$19,500 CAD, fixed

One price for the review, the new system, the switch-over, and the handover. On the call, tell us how your scheduled jobs run today.

Book a call

Questions

What does the EPM Automation Rebuild replace?: The scripts and scheduled jobs that load data and metadata into Oracle EPM Cloud, take backups, and run housekeeping. The existing setup is reviewed first, then replaced in full.
Does it only run overnight?: No. Runs follow a schedule you set: overnight, at set times through the day, or on demand from a guided menu or a one-click button.
How much does the EPM Automation Rebuild cost?: $19,500 CAD, fixed. One price for the review, the new system, the switch-over, and the handover.
Where does the new system run?: On an isolated server of your choice: a new virtual machine or an existing server. The old jobs keep running until you decide to switch.
How are passwords handled?: The password is typed once at setup and encrypted immediately. Plain text is never written to disk, a script, or a log, and the encrypted file only works for the service account that runs the jobs.
What happens if a source file is wrong or missing?: Every file is checked for layout, row count, and age before it loads. A bad or missing file stops the run cleanly, EPM keeps the previous day's good state, and the alert explains the problem and the fix.
Does it write directly to the EPM database?: No. Every load goes through Oracle's supported tools: EPM Automate and EPM jobs.
Which Oracle Cloud EPM business processes does it support?: Any business process loaded through EPM Automate, including Planning, Financial Consolidation and Close, and Account Reconciliation.
Who can run it after handover?: Your administrators. It runs under a service account rather than a person's login, and a new administrator can operate it from the guide on day one.