The November 2026 update gives Oracle EPM teams direct API access to tasks that used to involve exporting a snapshot, finding an artifact and working through its XML. It also gives agents a way to resolve business terms and find the right form or data intersection before they query a cube.
I’ve been waiting for this since seeing the EPM Modeler agent at KScope 26. My first question after the demo was which REST APIs Oracle would make available to the rest of us. I’ve tried several of the new endpoints, and artifact discovery is already one of my favorites. Oracle’s November 2026 release notes
New REST APIs for Planning and FreeForm
Oracle lists 141 platform APIs for Planning and FreeForm in 26.11. They cover application discovery and metadata, dimensions and members, form and dashboard definitions, Calculation Manager rules and rule sets, and user context such as profiles, preferences and points of view (POVs).
Artifact discovery stands out because it makes a common admin task simpler. When you need to find forms, dashboards, rules or rule sets, you can use the supported discovery and list operations for those artifacts. The authoring APIs go a step further. A tool can create or update a form or dashboard through its documented API, which gives teams a path away from XML workarounds for those operations. New Cloud EPM Platform REST APIs
Give agents a vocabulary with Business Concepts
When someone asks for “O&M expenses for the quarter,” the EPM member names and aliases may only tell part of the story. Which account rollup does Finance mean? Which form does the team use to review it? Business Concepts let you define the term, add synonyms, example phrases and keywords, and associate the concept with relevant objects or members.
That also helps when different teams use different terms for the same measure. A team can map “net earnings,” “bottom line” and “profit after tax” to its Net Income concept if those terms represent the same measure in the application.
For example, an agent answering “How are we tracking on headcount cost for the Sales org?” could use two operations:
- Resolve the term. Pass the question to the business concept resolution API and get candidates such as Compensation Expense.
- Find the relevant artifacts. Use the discovery API to find associated objects and members that could help answer the question, such as a workforce expense form or an account rollup.
The agent can use those results to ground the next step in definitions your team maintains. Business Concept Management APIs
Use Semantic Context to resolve the point of view
Once an agent understands the business term, it still needs to know which period, scenario and other dimension members to use. Oracle’s Semantic Foundation APIs support that work before data retrieval.
| API capability | What it gives the agent |
|---|---|
| Get Semantic Foundation Context | The current fiscal context, plan types, key substitution variables and scenario time windows. This helps interpret phrases such as “this month” and “year to date.” |
| Resolve a Semantic Point of View | Proposed dimension selections for a request such as “Show FY24 total expense,” plus unresolved dimensions such as Scenario or Version. The agent can use those gaps to ask a specific follow-up before retrieving data. |
| Find Forms by Member Slices | Forms that cover a combination such as year, account and entity, scoped to forms the caller can read. Cell access still depends on data permissions. |
| Semantic Context Intersections | Named combinations of members, such as “Approved FY26 Plan,” that teams can define once and reuse across requests. |
Oracle documents the Application Administrator role for the context, POV resolution and form discovery endpoints. Account for that role when designing a workflow for finance users. Semantic Foundation APIs
MDX form authoring and data export
Planning and FreeForm can now generate a starting MDX query from an existing Classic form layout. The query editor supports data-driven member selection, ranking, filtering and calculations at query time. That gives teams a practical way to start from a form they already know and adapt it using MDX. Oracle’s MDX form design release note
The part I’m most excited about is the Export MDX Query Data REST API. A Service Administrator can send a custom MDX query to a selected cube and receive a JSON grid with the POV, column headings, row headings and values. This is also a way to test a query before deciding whether it belongs in a saved form. Export MDX Query Data API
If you’re new to MDX, start with Oracle EPM MDX Queries Explained: A Beginner’s Guide. It walks through your first query and shows how to compare Actual and Budget in the same grid.
OAuth 2.0 for cross-environment and NetSuite connections
- Cross-environment connections. Planning, FreeForm, Financial Consolidation and Close, and Tax Reporting support OAuth 2.0 for cross-environment connections when the target identity domain is configured to accept it. Cross-environment OAuth 2.0 release note
- NetSuite integrations. Data Exchange supports the OAuth 2.0 authorization-code flow for both NSPB Sync and EPM Connector. NetSuite OAuth 2.0 release note
Multiple consolidation cubes in FCC
New and existing Hybrid Financial Consolidation and Close applications that use Dense/Sparse Optimization (DSO) can now support up to four additional consolidation cubes. The cubes share application dimensions and settings, and users can select a cube for supported processing and reporting activities.
The design question is which data belongs in its own cube. Constant currency analysis, management reporting and disclosure detail are examples where a separate cube can serve a distinct purpose. Ownership-enabled applications require Enhanced Organization by Period before administrators can enable additional cubes. FCC multiple cube release note
Account Reconciliation gets an assistant and new APIs
The Transaction Matching Configuration Assistant uses an uploaded template to create or extend a match type. The template describes data sources, attributes, match processes and rules. For a new match type, the assistant validates the template and creates the configuration after Service Administrator approval. For an existing match type, it adds missing configuration while preserving existing components. Oracle provides it as a downloadable template for Fusion AI Agent Studio. Transaction Matching Configuration Assistant release note
The new Account Reconciliation REST APIs cover formats, reconciliations and transactions. They expose reconciliation details and workflow operations, along with supporting information such as comments, attachments and action plans. These are the next APIs I want to test against real reconciliation workflows. Account Reconciliation REST API release note
What this means for agents in Oracle EPM
The workflow I’m most interested in is taking a question from a finance user, resolving it to the right business concept and POV, then calling a supported Oracle API to retrieve the answer. The model interprets the question. The EPM application supplies the business definitions, resolves selections and handles the request under the caller’s Oracle permissions.
I expect the API surface to keep growing. One addition I’d like to see is attribute dimension details in the Member Details API response. That would simplify a lookup I currently handle separately.
Two product announcements from Newarc
- EPM Relay connects Power BI, Excel and Tableau to live Oracle EPM data. It also supports data retrieval from AI clients such as Claude, ChatGPT and OpenCode, with OAuth 2.0, SSO and Basic Authentication.
- Newarc EPM MCP Server connects AI clients to Oracle EPM Planning using your own Oracle sign-in. The current Windows release runs locally and provides read-only tools for metadata, jobs and data exports. An OCI-hosted option is planned. Explore the Newarc EPM MCP Server