Essbase. TM1. JD Edwards.
Automated without an ETL tool.
The old paradigm is out. The new paradigm is AI. AI automation is InTouch AI. The systems that run enterprise finance, planning, and ERP aren't going anywhere — and now a general AI-native engine drives them. InTouch AI ships first-class tools for Oracle Essbase, IBM TM1 (now Planning Analytics), and JD Edwards — decades of production experience baked into every parameter. A specialized ETL suite can't grow an AI core; a general engine already has one. No DataStage license, no Informatica seat, no fragile Perl script from 2008. Just a configurable tool, scheduled, audited, RBAC'd — with an AI center that reads a failed close and tells you why.
Built From Experience, Not Specification
A general engine eats specialized tools. Everything a config-era ETL suite does for these systems, InTouch AI does — and then keeps going, because the AI sits at the center, not bolted on the side.
Oracle Essbase
Nine distinct operations: MaxL calc scripts, data loads, outline updates, export, clear, substitution variable updates, backup, restore, and custom CDF execution. Intelligent mutual exclusion — the tool holds an exclusive lock against the cube during destructive operations so two jobs don't collide. A decade of production use across Fortune 500 finance departments.
IBM TM1 / Planning Analytics
Run chores, run TI processes with parameters, read and write cube slices, trigger rebuilds. Fanatical session management — TM1's session limit is a real thing and the tool respects it, with reconnection, timeout tuning, and exclusive-lock patterns for concurrent-run safety. Replaces expensive ETL tooling one job at a time.
JD Edwards Report
Submit UBE reports, monitor completion, retrieve output. Report queue management, per-environment targeting, output routing. The piece that turns "someone needs to run the UBE and email the result" from a daily ticket into a scheduled job.
These Systems Don't Die. They Deserve Modern Automation.
The config-era way of running these — a rule that retries N times and emails a log nobody reads — is dead. The contract is now intelligent: tell InTouch AI what to run, when, what to do when it works, what to do when it doesn't, and who to notify. When a chore or a calc fails, it reads the failure, knows why, and surfaces the one sentence that matters. It broke. Here's why. I fixed it. No legacy ETL tool can say that.
The Replacement Never Quite Comes
Finance and planning orgs have been "migrating away from Essbase" for 15 years. TM1 was supposed to be replaced by cloud planning tools. JDE was supposed to be replaced by Oracle Cloud. Somehow, they're all still in production. InTouch AI takes that reality seriously.
The Expert Always Leaves
The person who knew the calc scripts, who knew which TI had to run before which chore, who knew the JDE environment variables — they left. Their scripts went with them. InTouch AI jobs are declarative, documented, and versioned. The knowledge survives the employee.
Enterprise-Grade Access to Enterprise-Grade Systems
This is the trust floor. Essbase, TM1, and JDE credentials live in the AES-256 credential vault, referenced by name, never written into a script — and never exposed even to the AI itself. RBAC on the job object controls who can run the "month-end close" sequence. The full audit log records every run: who, what, when, how long, what rows moved. Self-hosted, on your hardware, from a laptop to the data center — production-hardened in Fortune 500 finance long before "AI automation" was a phrase.
Replace the Script You've Been Meaning to Rewrite
Stop feeding a dead paradigm. The script that runs your close should read its own failures and heal them. Start with the free Personal edition — Essbase, TM1, and JDE tools ship in every edition.