Oracle Update June 2026 - Issue

Oracle Update June 2026 –Issue: 5-minute estimated reading time

Data Integration EPBCS EPM Cloud

Here, we compile the latest developments, knowledge, and insights regarding the June 2026 Oracle Update.

Oracle EPM Cloud 26.06: Please Note Regarding Data Integration Between FCC and Planning

An issue has been reported in the Oracle EPM Cloud 26.06 update regarding data integration between FCC and Planning / EPBCS.

The problem may become apparent when an integration retrieves data from FCC and loads it into Planning. The integration then fails with a message such as:

ERROR_INVALID_PERIOD

The tricky part here is that the cause doesn't seem immediately obvious. Period mappings may be set up correctly, the integration may have worked fine before, and the same setup may still function in a different environment. As a result, it initially appears to be a configuration problem, whereas in this case it may actually be a product issue in the 26.06 update.

How can you tell?

You'll notice this especially in:

  • Data Exchange / Data Integration jobs that suddenly fail after the June 26 update
  • Integrations from FCC to Planning or EPBCS
  • Error messages related to an invalid period, even though the period mapping appears to be correct
  • Situations in which the test environment is already running on June 26 but the production environment is not, or in which behavior differs between environments

What can you do?

First, check the basics: period mapping, POV, import/export mode, start period, end period, and the integration log files.

If all of this seems correct, don’t treat it as a local configuration error for too long. Create a Service Request with Oracle and refer to the behavior observed after the June 26 update. Explicitly ask Oracle to assess whether the specific one-off patch for June 26 is necessary in the affected environments.

After applying the patch, it is important to rerun the same integration and verify that the load is running through completely again.

The most important lesson: not every error message related to period mapping automatically means that the period mapping is incorrect. Sometimes the message is technically correct, but the cause lies in the underlying release.

For EPM administrators, this is exactly why logging, version control, and a clear monthly update process remain important.

Smart | Simple | Solid

Related insights