How to Add a Private AI Layer to Hyperion and Essbase On-Prem
how to add AI to Hyperion Essbase on-prem
Also searched as
- Essbase MDX LLM natural language query on-premises
- Hyperion Planning AI integration without cloud
- Essbase REST API AI assistant
Short answer
Essbase is a multidimensional cube, so the AI layer should call approved, parameterised MDX or report tools rather than letting a model write free queries. Authenticate as the end user so Shared Services provisioning and Essbase filters apply, pull narrative context from planning documents and commentary into a local index, and run the model on your own GPUs. Writes to plans stay in Planning forms, with human approval.
Applies to: Oracle EPM (Hyperion) 11.1.2.4 and 11.2.x on-prem with Planning, Financial Management and Essbase; standalone Essbase 21c has a REST API, older Essbase relies on MaxL, Java API and Smart View
Build order for an EPM private AI layer
- 1List the cubes (applications and databases) that matter and which questions finance asks of them: variance by entity, forecast vs actual, driver changes. Start with one cube.
- 2Document the dimensions, hierarchies, aliases and member naming, and publish them as a semantic layer the tool server can use to validate member names.
- 3Build parameterised tools (for example variance for entity, account, period, scenario) that generate MDX from validated members. The model chooses a tool and parameters; it does not write MDX.
- 4Authenticate as the end user via SSO and your EPM security provider, so Shared Services provisioning, Essbase filters and Planning access permissions apply.
- 5Index commentary, planning documents, supporting detail text and board packs in a local vector store with entity and scenario as the access label.
- 6Serve the model locally with vLLM or Ollama and render answers with the returned numbers cited next to the tool call.
- 7Keep plan updates in Planning forms or Data Management loads, with an approver, never from the model.
How EPM data is reached
Essbase stores numbers in a multidimensional database addressed by members, such as Year, Scenario, Account, Entity and Product. The documented access paths are MDX queries, report scripts, MaxL for administration, Smart View for Excel, and, in Essbase 21c, a REST API that can list applications and databases and run queries and jobs. Older on-prem releases rely on the Java API and Smart View. Hyperion Planning keeps its metadata in a relational repository and its data in Essbase; Financial Management (HFM) has its own application tables and APIs.
The key design choice: treat the cube as a calculation engine with a strict vocabulary. A model that invents a member name or an unsafe cross-dimensional query produces nonsense or a heavy query. A tool layer that validates member names against the dimension hierarchy, and caps the number of cells returned, prevents both.
-- MDX built by the tool, parameters validated against the hierarchy
SELECT {[Jan],[Feb],[Mar]} ON COLUMNS,
{[Actual],[Budget]} ON ROWS
FROM [Sample].[Basic]
WHERE ([Sales],[East],[Cola])Reference architecture
The EPM stack stays where it is. A tool server connects to Essbase (or Planning and HFM through their supported interfaces) over an internal service account only for metadata, and uses per-user sessions for data. Commentary and supporting documents come from Planning supporting detail, cell text and the file shares where board packs live; they go to a local index. Generation runs on local GPUs so unpublished forecasts, covenant calculations and board material never reach a third party.
An audit service records user, tool, members requested, cell count and answer. For air-gapped finance networks, the only inbound path is the analyst's browser or Teams-equivalent on the internal network; model weights are imported through an approved transfer.
Security: provisioning, filters and access
On-prem EPM security is managed in Shared Services provisioning (native directory or an external LDAP/AD), with Essbase filters restricting members and data access by role, and Planning access permissions on members and forms. A shared service account that can read the whole cube defeats this, so connect as the end user wherever the platform allows it, and test with a user who has a restricted filter to prove cells outside that filter never return.
Where per-user sessions are not possible, restrict the service account to specific slices, apply the same filters in the tool server from a mapping you verify with the EPM administrator, and treat that mapping as production security code with change control.
Rollout, sizing and honest limits
Phase 1 is read-only variance and trend questions on one cube in 6 to 10 weeks; phase 2 adds explanations that combine numbers with commentary; phase 3 prepares plan inputs as drafts for a planner to enter. Sizing is small: the numbers are tiny compared with document corpora, so one GPU node for a 30B-class model is often enough, and the index is limited to commentary and documents.
Limits: free-form natural language to MDX is unreliable on large, sparse cubes with custom calculations and Dynamic Calc members; results depend on calc scripts and consolidation order, so verify numbers against Smart View; and if your finance team mostly needs better dashboards, Smart View, Financial Reporting or Oracle's own cloud EPM may be simpler than a custom layer.
Try it here, free
Hyperion and Essbase Private AI Layer Blueprint Generator
Fill in your Hyperion and Essbase version, database, hosting and users to get a shareable architecture plan for a private, on-prem AI assistant.
Common pitfalls
- !Letting the model write MDX freely. It will guess member names and may request millions of cells.
- !Using one broad Essbase account so every user sees the full cube.
- !Ignoring Dynamic Calc and shared members, which can make returned values differ from a Smart View result.
- !Allowing a model to update plans. Plan changes should go through forms or loads with approvals.
- !Indexing board packs without access labels, exposing confidential forecasts to wider audiences.
How an ERP-grounded AI assistant handles this
ERPray can sit in front of an on-prem Essbase or Planning application as a tool layer: it validates members, runs the approved query as the asking user, shows the MDX or report behind the answer, and combines the numbers with local commentary. It does not change plan data; it drafts inputs for a planner.
Frequently asked questions
Can an LLM generate MDX for Essbase?
It can for simple queries, but reliability drops on large cubes. A safer design uses parameterised tools with validated members and result caps, and reserves free-form MDX for an analyst who reviews it.
Does Essbase have a REST API on-prem?
Essbase 21c provides a REST API. Older 11.1.2.x on-prem relies on MaxL, the Java API and Smart View, so check your version before designing the integration.
How do we keep Shared Services security intact?
Authenticate as the end user, let Essbase filters and Planning permissions apply, and test with a restricted user. If you must use a service account, replicate filters in the tool server and review that mapping like production security code.
Is this worth it versus Smart View?
For analysts who are comfortable in Smart View, probably not for pure number retrieval. The value is in combining numbers with commentary and documents, and in giving non-analysts safe access.
Related
How to Add a Private AI Layer to PeopleSoft On-Prem
Reach PeopleSoft through its own mechanisms: PS Query exposed through Query Access Services, Integration Broker service operations, and Component Interfaces for writes. For bulk reads use a replica with the security join tables applied. Add a local retrieval index over file attachments and an open-weight model on your own GPUs, and keep row security equal to what the user sees in the application.
CIO briefingOn-Prem vs Cloud ERP AI for Regulated Manufacturers
For ITAR, CMMC, and export-controlled manufacturers, the deciding question is not on-prem versus cloud in general but whether controlled unclassified information (CUI) or export-controlled technical data ever leaves your boundary to reach an AI model. An on-prem or private-VPC-deployed AI layer keeps that data inside your control boundary; a vendor's shared cloud AI service usually does not, regardless of how the core ERP itself is hosted.
AdvancedHow to Add a Private AI Layer to Oracle EBS 12.2 On-Prem
Do not point a model at the production APPS schema. Read from an Active Data Guard or GoldenGate copy through a small tool server that applies Multi-Org and responsibility security, retrieve from FND attachments in a local index, and serve an open-weight model on your own GPUs. Any write goes through Integrated SOA Gateway or the standard open interfaces with a human approval step.
AdvancedHow to add a private AI layer to Infor LX / BPCS on-prem
BPCS and Infor LX run on IBM i with their data in Db2 for i, in files that carry short coded names by module. A private AI layer reads those files through read-only SQL views over a replica, indexes documents and attachments separately, exposes approved queries through a tool server, and serves an open-weight model on local GPUs. Writes, if any, go through the supported transaction programs with human approval.
AdvancedHow to add a private AI layer to Infor System21 on-prem
System21 runs on IBM i with its business data in Db2 for i. The practical private AI pattern is a read-only replica or extract, SQL views that give files readable names, a retrieval index over documents, a tool server of approved queries, and a locally served open-weight model. User visibility is carried over from System21 security and company set-up, and writes only go through its supported entry points after approval.
AdvancedHow to add a private AI layer to Infor EAM on-prem
On-prem Infor EAM stores its data in an Oracle or SQL Server schema whose tables use the R5 prefix, and it exposes web services for supported access. A private AI layer reads equipment, work order and parts data through read-only views on a reporting copy, indexes failure notes and manuals for retrieval, mirrors EAM organisation security, and serves an open-weight model locally. Work orders created or changed by the assistant go through EAM's web services after a person approves.
AI for ERPOracle ERP AI Consulting: What a Partner Should Deliver
Choosing an Oracle JDE partner for AI: what to demand across JD Edwards (Orchestrator, AIS), EBS, NetSuite and Fusion Cloud, plus the buyer questions to ask.
AI for ERPAI across Oracle Agile PLM and your ERP: engineering changes without the swivel chair
Ground AI on Agile PLM engineering change orders and BOMs alongside ERP, so engineers and planners get accurate ECO impact answers without swivel-chair lookups.
Stuck on Oracle Hyperion and Essbase on-prem?
Talk to engineers who work inside Oracle Hyperion and Essbase on-prem every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Hyperion and Essbase Private AI Layer Blueprint GeneratorFill in your Hyperion and Essbase version, database, hosting and users to get a shareable architecture plan for a private, on-prem AI assistant.
- Hyperion and Essbase AI Assistant Sizing and Value CalculatorEstimate peak load, GPUs, index size, hours saved and payback for an on-prem AI assistant on Hyperion and Essbase.