The documentation for the May update to Oracle Cloud EPM has been released. As a reminder, these updates are applied in test during the first daily maintenance that occurs after Friday, June 6, 2025 at 22:00 UTC and in production two weeks later during the first daily maintenance that occurs after Friday, June 20, 2025 at 22:00 UTC. This month includes a sizable list of updates and just like last month…new Data Exchange features.
If you’ve been looking for location security in Data Exchange…you’ve been out of luck. But as of the June 2025 update, Data Exchange now supports location security settings. This is yet another step in the process to ensure that Data Exchange has feature parity before finally pulling the plug on Data Management for good.
The EPM implementation of Groovy in Business rules now supports two options: creating a ZIP file and creating an Excel file. As we look to Pipelines to provide fully automated and orchestrated processes, it is important to have the functionality of Groovy in Business Rules to aide in areas where Pipelines have gaps in capability. Creating ZIP for instance could reduce the file size of extracted data from the system to allow for rapid downloading. Creating Excel files can be used in a near countless number of ways with a full set of classes available for adding rows and a whole host of other methods.
With the June 2025 update, Financial Reports is officially not longer supported. While Oracle has chosen to leave the functionality intact for the time being, if you experience any issues with Financial Reports and you contact support…they will kindly ask you to migrate your reports to Platform Reporting or Narrative Reporting. While some people might miss FR, I’m actually pretty happy to see it go!
While some of us (not me) will be mourning the loss of Financial Reports, beginning in October 2025, we’re losing another piece of original functionality in the cloud: Forms 1.0 and Dashboards 1.0. In most cases, this migration is pretty straight forward, but care must be taken to ensure that forms act the way they have been acting. It will also be important to ensure that end users are notified of the upcoming change and provided with basic training as necessary.