Oracle Hyperion 11.2.24 features !

Oracle On-Premises EPM Patch Version - 11.2.24 released Jan 2026 

Release 11.2.24 includes the following new features

Component - Version

Java - Java 8 Update 471

Essbase - 21.7.3 (no changes to Essbase for .24, this is the same version released with Hyperion version 11.2.23.0)

WebLogic - Patch Set Update 12.2.1.4.250910

Application Development Framework (ADF) - Bundle Patch 12.2.1.4.250822

Note: Important UI Changes in Recent ADF Patch Update

To enhance accessibility in EPM applications in alignment with the latest Oracle Accessibility Guidelines (OAG), we recommend applying ADF patch 37836334. This update increases row heights and spacing across various EPM applications, including HFM, FDMEE, Planning, and Reports, to improve usability for users with accessibility needs. 

While these changes align with accessibility standards, they may result in fewer visible rows per page and increased scrolling.

Oracle HTTP Server (OHS) 19c Bundle Patch 12.2.1.4.250609

Oracle Data Integrator (ODI) : No patches in this release

Hypeiron Financial Management Features

• Financial Management Oracle Accessibility Guidelines (OAG) Feature For All UI Screens
The Oracle Accessibility Guidelines (OAG) version 3.2 outline Oracle’s accessibility standards and requirements, which are incorporated into the company’s legal and contractual obligations. 

The HFM UI pages are now compliant with OAG version.

Oracle FCCS Financial Consolidation and Close Database Refresh Failure Error Troubleshooting

Oracle FCCS Financial Consolidation and Close Database Refresh Failure Error Troubleshooting

Occasionally, users will come across Database refresh errors from the FCCS non-hybrid application, displaying the following error:

Cube refresh failed with Essbase Cube: Consol, Error code: 1060200, Message: HSP_TMP_db248fa7-058e-4ddc-9891-46c9346a8b33

Why does it happen?

This error occurs, generally, after you add a shared entity under mid-hierarchy where the entity being added was already shared above and below the hierarchy.

What is the solution?

1. Use one of these performance substitution variables to improve performance. The degree of performance improvement varies widely across different applications as it is driven by the application design and data distribution.
   • OptimizeConcurrency: Use this substitution variable with a value of true (OptimizeConcurrency=true) to improve the concurrency of the consolidation process by executing some of the calculations at the very beginning or at the end. The degree of improvement depends on the entity structure. Deep entity hierarchies will see more performance improvement than shallow entity hierarchies.
   • DeltaDBRefresh: Use this substitution variable with a value of true (DeltaDBRefresh=true) to perform only necessary actions based on metadata change. Not applicable for Legacy Non "Extended Dimensionality" applications.
   • OluRatesLoad: Use this substitution variable with a value of true (OLURatesLoad = True) to improve database refresh performance if the application has a lot of scenarios, currencies,s and rate accounts.
   • OptimizeDBRefresh: Use this substitution variable with a value of true (OptimizeDBRefresh=true) to improve performance by streamlining the way that exchange rates are pushed to the Console cube during the database refresh.
2. Change the newly added shared member to the bottom.
   1. Open the Financial Consolidation and Close application.
   2. Select Navigator, then Dimensions, and then Entity.
   3. Select the hierarchy where you recently added the shared member.
   4. Move the selected hierarchy to the bottom using the Move Down icon.
   5. Refresh the database and verify that the process completes successfully. If database refresh fails, take necessary corrective actions.
   6. After the database refresh is complete, move the shared entity to its original location.
   7. Refresh the database again and verify that the process completes successfully.

Oracle Update Rollout Decision on Essbase 21c

What was the root cause for the 25.11 update being withheld from Production environments?

A few customers reported issues in their 25.11 test environments related to calculation accuracy and system slowness. These problems were specific to customizations within certain customer applications and were only observed sporadically across different customers.

Why did Oracle also decide to skip the 25.12 (December 2025) and 26.01 (January 2026) updates?

The year-end is a critical period for many customers’ business processes. Oracle deferred these updates to avoid any risk of disruption during this time, allowing additional time to fix reported issues and to validate future updates.

Based on issues reported so far, what areas of the applications would Oracle recommend customers test to ensure Essbase 21c works well?

The Oracle Essbase 21c upgrade has no impact on these business processes:

• Narrative Reporting
• Account Reconciliation
• Enterprise Data Management

Oracle recommends customers investigate the following areas of their applications to ensure Oracle Essbase 21c does not have any cause for concern:

• Overall Tests across Financial Consolidation and Close, Planning, Profitability and Cost Management, and Tax Reporting: Run all allocations, data loads, data exports, and reports and confirm that there are no regressions in results and no performance degradations.

• Financial Consolidation and Close:

  Performance Test:

  Run Consolidate and Translate Rules: These rules in Essbase 21c should take a similar amount of time as it used to take in Essbase 11g when the same set of entities were calculated - especially if your insertion points use the Essbase functions @CALCMODE and @EQUAL in Hybrid Mode (SET HYBRIDBSOINCALCSCRIPT FULL).

  1. Run On-Demand Rules: These rules in Essbase 21c should take a similar amount of time as it used to take in Essbase 11g when the same set of entities were calculated. Especially test ODRs using @CALCMODE and @EQUAL Essbase functions in Hybrid Mode (SET HYBRIDBSOINCALCSCRIPT FULL).
  2. Data Retrieval: Test your ad-hoc grids, data forms, and reports in Essbase 21c. Retrievals should take a similar amount of time as it used to take in Essbase 11g.
  3. Data Integration: Test the same data integration exports using All Data mode and Replace Mode.
  4. Restructure Cube: This task in Essbase 21c should take a similar amount of time as it used to take in Essbase 11g when same cube was selected.

  Data Integrity Test:

  1. Ad-hoc Data Comparison: Consolidated data retrievals on ad-hoc grids with Essbase 21c (Sheet A) with Essbase 11g (Sheet B) must tie out. Sheet A - Sheet B = 0.
  2. Data Exports (Dynamic and Stored Sparse Data): Data Integration Export using All Data mode for Essbase 21c must tie with Essbase 11g.
  3. Custom Member Formula Tests: Ratios/Statistical Analysis must match between Essbase 21c and Essbase 11g with the same Solve Orders.

Oracle EPM Automate and REST APIs using OAuth 2.0

Recommendation to Use OAuth 2.0 Instead of Basic Auth with EPM Automate and REST APIs

Oracle recommends using OAuth 2.0 instead of Basic Authentication to ensure enhanced security when using EPM Automate and EPM REST APIs. OAuth 2.0, which utilizes access tokens to establish connections to web services, is the industry-standard protocol for authorization.

Compared to Basic Auth, which uses passwords to establish connections, it provides a more secure method to connect to web resources. 

Applies to: Account Reconciliation, Enterprise Data Management, Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Narrative Reporting, Planning, Profitability and Cost Management, Tax Reporting

Business Benefit: OAuth 2.0 provides a more secure method of connection compared to Basic Auth.

Authentication with OAuth 2

You can use an OAuth 2 access token to issue REST APIs on Oracle Fusion Cloud EPM to satisfy the requirement of avoiding the use of passwords in your environment.

Setting Up Authentication with OAuth 2

In order to access Cloud EPM REST APIs with OAuth 2, a Cloud EPM Service Administrator has to request the Domain Administrator to set up an OAuth 2 client and provide the Identity Domain Cloud Service (IDCS) URL and Client ID.

Overview of the steps:

• Step 1. Register an OAuth client. This is a one-time setup step that requires user interaction with IDCS Administrator privileges.

• Step 2. Obtain and securely store the first refresh token. This step requires user interaction. It is a one-time step for each user who needs to invoke REST APIs with OAuth 2.

• Step 3. Obtain an access token from the refresh token. This step is easily automated. Once automation has been implemented, it can run without user interaction.

About Copying Code Samples

Do not copy code samples from the PDF version of this document. To avoid line breaks and footer information that will render code unusable, Oracle recommends that you copy code samples from the HTML version of the examples in this guide.

Oracle EPM - Mandatory Groovy Update Coming in January 2026

Latest update on Groovy!

A new version of the Groovy engine is planned for the 26.01 update (January 2026). This version introduces stricter validation rules, which means some existing Groovy business rules that work today may fail after the update. 

To avoid issues, you should validate and test all your Groovy scripts prior to the January update.

The Groovy Script Validator, available since the 25.08 update, helps you check whether your rules will pass under the new Groovy version. It will flag any scripts that need changes and generate a report so you can fix them ahead of time.

Recommended Actions

• Run the Groovy Script Validator as soon as possible.
• Review and update any scripts listed in the validator’s report.
• Fully test your Groovy business rules to confirm they work as expected.

If you need extra time to complete these tasks, you can delay the Groovy engine update for up to three months by using the EPM Automate skipUpdate command.

Applies to: Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Tax Reporting

To validate Groovy scripts:

1. From the Home page, select Application, and then Overview.
2. Click Actions, and then select Groovy Script Validator.

After running the validation program, you can download the Groovy validation report from one of the following locations:

• On the Jobs page, under Recent Activity, click the Groovy validation report Job, to view the Download option.
• On the Inbox/Outbox Explorer page, look for the GroovyValidationReport.html file, and download it.

The Groovy validation report shows all the rules and templates that need to be modified. For a list of Groovy validation errors and recommended resolutions, see Resolving Groovy Business Rule Validation Issues in Designing with Calculation Manager.

Oracle Enterprise-Profitability-and-Cost-Management EPCM New Rule Designer

New Version of the Rule Designer

This release introduces a new Rule Designer user interface. You can select which version of the Rule Designer to use in the Profitability and Cost Management Application Settings. Designer 1.0 opens the older version of the Rule Designer. 

Designer 2.0 opens the new Rule Designer UI with enhanced features.

Business Benefit:  Rule Designer 2.0 provides a more modern and updated user interface with more streamlined actions.

About the Rule Designer

Use the Rule Designer to create and manage rules and rule sets.

To access the Rule Designer:

1. From the Home page, select Modeling, and then Designer.

2. Once you are in the Rule Designer, you can:

   • Use the Waterfall Setup tab to create, edit, delete, and copy rule sets and rules. The Waterfall Setup tab shows the full sequence of rule sets and rules for the model. See Using the Waterfall Setup Tab.

   • Use the Mass Edit tab to add and replace members, copy rules to rule sets and models, and enable and disable rules. See Using the Mass Edit Tab.

Oracle EDM - Working with Accelerator Applications !

Working with Accelerator Applications

Accelerator applications are application templates that enable you to create Universal applications in Oracle Fusion Cloud Enterprise Data Management for application types that do not have a dedicated application adapter.

The accelerator application helps expedite the application creation process in Cloud EDM by providing a template that contains the basic dimensions, node types, properties, and validations for an application so that you do not have to create all of those objects manually.

Accelerator application templates are available to create Universal applications for the following application types:

• Oracle Financial Services Accounting Foundation Cloud Service (AFCS) applications
• Oracle Financial Services Data Foundation Cloud Service (DFCS) applications.

Accessing the Accelerator Application Template

You access the accelerator application template by exporting it from the sample application. Follow these steps to create the sample application and access the accelerator application template.

Note

You access the sample application by recreating your service. Therefore, the following procedure details steps to back up your testing environment, recreate the service, create the sample application, export the template, and then restore your original testing environment. If you have another environment from which you can access the sample application then these steps may not be necessary.

1. In your testing environment, back up your service. See Backup Application in Administering Migration .
2. Recreate your service. See Recreating the Service.
3. Create the sample application. See Creating a Sample Application.
4. In the sample application, use the template feature to export one or both of the following accelerator applications.
   • AFCS: Accelerator application for Oracle Financial Services Accounting Foundation Cloud Service.
   • DFCS: Accelerator application for Oracle Financial Services Data Foundation Cloud Service.