From EPRCS to Oracle Narrative Reporting
The product most of us learned as EPRCS (Oracle Enterprise Performance Reporting Cloud Service) is now officially Oracle Fusion Cloud Narrative Reporting. The rename is the easy part. The change worth paying attention to is happening one layer down: Oracle has spent the last two years consolidating grid-and-chart reporting across the whole Cloud EPM platform into a single module called Reports, and retiring classic Hyperion-era Financial Reporting (FR/FRS) in the process.
If you're looking for a full walkthrough of what Narrative Reporting does today (data sources, doclets, review workflows), our overview of Narrative Reporting in Oracle Cloud EPM and our report packages deep dive already cover that ground. This post is about the part those don't: what changed when EPRCS became Narrative Reporting, what happened to Financial Reporting, and how to decide between Reports and full report packages now that the old FRS comparison no longer applies.
Why the Old EPRCS-vs-FRS Comparison Doesn't Hold Up
When EPRCS first launched, the natural comparison point was Oracle's older Hyperion Financial Reporting Studio (FRS): similar grid-and-chart reporting, different price tag, different feature set. That comparison has aged. Oracle has since folded grid-and-chart authoring into a single module called Reports, used both inside individual Cloud EPM business processes (Planning, FCCS, Tax Reporting, and so on) and inside Narrative Reporting for multi-source work. Reports supports:
- Grids and charts sourced from Cloud EPM applications, Essbase, and ERP Cloud Financials
- Conditional formatting and suppression applied at the cell, row, or column level
- Member selectors, substitution variables, and dynamic text/formula functions
- Drill-through to source data and zoom on parent members
- Centralized point-of-view (POV) control across a deployment
- Books, which bundle multiple reports and documents into a single PDF or Excel output
- Bursting, which runs a single report or book across every member of a dimension and publishes one output per member
The Retirement of Classic Financial Reporting
Classic Financial Reporting (FR/FRS) is being phased out in favor of Reports. As of the June 2025 (25.06) monthly update, Oracle stopped shipping bug fixes and enhancements for classic FR across Cloud EPM Platform business processes (Tax Reporting and NetSuite Planning and Budgeting are the current exceptions), which is the clearest signal yet of where Oracle wants everyone to land.
Existing FR content isn't stranded: Oracle supports migrating reports through in-place migration (migrate all reports at once, or one at a time, with an option to carry over the folder structure) or by importing report files that were previously exported from the FR Explore Repository. If your organization still has legacy FR-based reports in production, that migration should already be on your roadmap, check Oracle's current readiness documentation for your pod's timeline, since Oracle has revised this schedule more than once and continues to update guidance as the transition progresses.
Report Packages Still Belong to Narrative Reporting, Not Reports
Reports alone is scoped to a single EPM Cloud instance or business process. Report packages, the collaborative, multi-source, narrative-driven documents built inside Narrative Reporting, are a different thing entirely, and they're still the reason to reach for Narrative Reporting instead of, or in addition to, Reports. We cover how report packages are structured (doclets, sections, sign-off) in detail in our report packages overview; the short version is that report packages retain capabilities Reports doesn't have on its own: Notes, Disclosure Management, in-line annotations, and full change tracking. That's why multi-entity, audited, narrative-heavy reporting (10-Ks, board books, statutory filings) still belongs in Narrative Reporting rather than a standalone Reports instance.
Choosing Between Reports and Narrative Reporting
The decision today isn't "EPRCS versus FRS" the way it was a few years ago; FRS is on its way out. The more useful framing is: use Reports when you need grids and charts sourced from a single Cloud EPM application, and reach for Narrative Reporting's report packages when you need multi-source or multi-instance data, structured review workflows, commentary, or audit-ready narrative content. Many organizations end up using both: Reports for day-to-day operational reporting inside each application, and Narrative Reporting for the collaborative, board-level packages that pull it all together.
Licensing and packaging for Narrative Reporting have also evolved since its early days as a separately subscribed service; current bundling depends on your Cloud EPM edition and agreement, so confirm the specifics with your Oracle account team rather than relying on older pricing figures.
If you're planning a migration off classic Financial Reporting, or want help deciding where Reports ends and a full report package begins, CloudADDIE can walk through your specific environment with you.