Back to Blogs

Cannot Update the Connections If EPM Versions Are Different

By Lead Innovative Technologies|4 min read|Oracle EPM

If you have an EPBCS application and you are trying to connect it to Narrative Reporting for report development, you cannot update the connection if both applications are on different Oracle EPM Cloud versions. This is one of the most common "why won't this connection save" issues report developers run into, and it has nothing to do with your data source configuration.

The Scenario

You have an EPBCS application that you want to use as a data source in Narrative Reporting, so report developers can build doclets, grids, and report packages against live Planning data. You go to update or validate the data source connection between the two applications, and the update fails or the connection will not save, even though the credentials, URL, and permissions all look correct.

The Root Cause: Version Mismatch

Oracle EPM Cloud services are updated on independent schedules. Test and non-production environments are typically updated first, followed by production a short time later. Because of this, it is very common for two EPM Cloud services, such as EPBCS and Narrative Reporting, to end up running on different monthly or quarterly versions at any given point in the update cycle.

When you try to create or update a data source connection between two EPM Cloud applications, Oracle requires both applications to be on the same version for the connection to validate and update successfully. If the versions do not match, the connection update will fail.

The Rule to Remember

Make sure both applications are on the same version. This means Production connecting to Production, and Non-Production connecting to Non-Production.

  • Production EPBCS can only reliably update its connection to a Production Narrative Reporting instance.
  • Non-Production (Test/Dev) EPBCS can only reliably update its connection to a Non-Production Narrative Reporting instance.
  • You cannot update the connection from Production to Non-Production, or from Non-Production to Production, if the two environments are on different versions.

How to Verify the Version Mismatch

Before troubleshooting security, roles, or URLs, check the release version of both environments first:

  • Open each environment and check the version number on the About page or the application details in the Oracle Cloud EPM console.
  • Compare the EPBCS version against the Narrative Reporting version.
  • If your organization uses EPM Automate, the getVersion command reports the current version of each environment quickly without logging in through the browser.

If the two versions do not match, that mismatch is almost always why the connection update is failing, not a permissions or network issue.

How to Fix It

  • Always pair Production with Production, and Non-Production with Non-Production, when setting up or updating data source connections.
  • If you are working in a Test or Dev environment, confirm both EPBCS and Narrative Reporting have already received the same monthly update before attempting the connection.
  • If production environments update on a delayed schedule, wait until both applications are on the same released version before updating the connection, rather than trying to force it early.
  • Coordinate connection setup or refresh activities with your EPM update calendar so both applications land on the same version window.

Why This Matters for Report Developers

This is easy to overlook because everything else about the connection looks correct, the credentials work, the URL is right, and the user has the correct role. Teams can lose hours troubleshooting security or network settings when the real issue is simply that the source and target applications are on different EPM Cloud versions.

Before you spend time debugging a Narrative Reporting data source connection that will not update, check the version of both environments first. If they do not match, that is your answer.