What is changing
Oracle announced in November 2022 that Reports would replace Financial Reporting across Cloud EPM. Update 27.02 completes that change. On Oracle’s usual schedule it reaches Test environments on February 5, 2027 and Production on February 19, 2027. It applies to every business process that uses Financial Reporting, including Planning, Financial Consolidation and Close, and Tax Reporting.
For most finance users, the visible change is small: reports open from a different place and look much the same. For the people who build and look after reports, it is larger. Reports are designed in the browser, charts are built in, books are assembled differently, and batches are replaced by bursting.
What Oracle’s migration does, and doesn’t
Oracle provides a migration that converts Financial Reporting report grids, text boxes, and images into Reports, for the whole repository or one report at a time. Most report designs come across. Some formatting and features need adjusting afterwards.
It does not move:
- Books, which are created again as Reports books.
- Batches and scheduled batches, which become bursting definitions in the Job Scheduler.
- Snapshot reports, which can’t be migrated and should be saved as PDF.
- Charts, which are rebuilt as Reports charts.
Excel workbooks holding fully formatted Financial Reporting reports also can’t be refreshed from Reports, so those are brought into Excel again once the report has moved.
Source: Oracle, Migrating Reports from Financial Reporting, and Oracle Support Document KB62016.
The order to do the work in
- Count what you have. List every report, book, batch, scheduled batch, and snapshot report in the repository, with the folder it sits in and when it last ran. This is the size of the job, and the number most teams underestimate.
- Decide what to keep. Ask each report owner which reports went to someone last quarter. Repositories built up over years carry drafts, one-off analyses, and copies of copies. Every report retired here is one fewer to migrate, check, and support.
- Save what can't move. Snapshot reports can't be migrated. Save the ones kept for audit or reference as PDF, in a place the finance team controls.
- Set standards before rebuilding. Agree on styles, folder structure, and security in Reports first. Without them, each person rebuilding a book makes their own choices, and the new repository is as hard to maintain as the old one.
- Migrate in Test and compare the numbers. Run Oracle's migration in Test. Open each migrated report beside the Financial Reporting original for the same period and point of view, and fix formatting and formulas until they match.
- Rebuild books and bursting. Create the books again in Reports, and replace batches with bursting definitions scheduled through the Job Scheduler, sending to the same people as before.
- Switch users over once. Pick a cutover date away from close and budget deadlines, move users to Reports together, and lock the Financial Reporting folders so nobody keeps editing the old versions.
The first two steps decide how big the rest is. A repository of 150 reports with 45 still in use is a 45-report project, once someone has confirmed which 45.
The mistakes that cost the most time
- Migrating everything. Moving the whole repository feels safe, and it multiplies the checking. Retire first, then migrate.
- Trusting a migrated report because it opened. A report can migrate without errors and still show different numbers, because of a formula, a suppression setting, or a point-of-view default. Compare every kept report against the original.
- Forgetting the people at the end of a batch. Scheduled batches often email managers and board members who never log in to EPM. If the distribution list isn't rebuilt in bursting, the first sign is a missing board pack.
- Forgetting Excel. Workbooks that hold fully formatted Financial Reporting reports can't be refreshed from Reports. Find them early, migrate the report, and bring it into Excel again from Reports through Smart View.
- Leaving it for January. 27.02 reaches Test on February 5, 2027. For most finance teams, January and February are year-end close, audit preparation, or budget season. Work done before the holidays is done in the quietest window left.
Where to start this week
List what is in the repository and count the reports, books, batches, and snapshot reports. Send the list to report owners and ask which ones they used last quarter. Those two steps take little time, need no new software, and turn an open-ended deadline into a known amount of work.
If you’d like help
We can review a snapshot of your environment at no cost and come back with a plan and a fixed price, whether we move the reports for you or your own team does the work with a roadmap.
Questions
- What replaces Financial Reporting in Oracle EPM Cloud?
- Reports, Oracle's reporting solution built into Cloud EPM. Reports are designed in the browser and include grids, charts, text, and images, with books for packaging reports together and bursting for running a report or book for many members and sending the results to recipients.
- When exactly is Financial Reporting removed?
- In the February 2027 update, 27.02. On Oracle's usual schedule, updates reach Test environments on the first Friday of the month and Production on the third Friday: February 5, 2027 in Test and February 19, 2027 in Production.
- What happens to a report that hasn't been moved by then?
- Once 27.02 reaches an environment, Financial Reporting is no longer there to run it. Anything still needed has to be in Reports, or saved as PDF, before that date.
- Does Oracle's migration move books and batches?
- No. Oracle's migration converts report grids, text boxes, and images. Books, batches, scheduled batches, snapshot reports, and charts are rebuilt in Reports or saved separately.
- Do finance users need training on Reports?
- Report viewers mostly need to know where reports now live and how to run them. The people who build and maintain reports need more, because the designer and the way books and bursting are set up are different from Financial Reporting.