How-toOracle Fusion Cloud ApplicationsEnvironment Management / Quarterly Updates

Oracle Fusion production to test (P2T) refresh and release dates

Question
oracle fusion production to test

Also searched as

  • oracle fusion release dates
  • oracle fusion p2t request
  • oracle fusion quarterly update schedule
  • oracle fusion test environment refresh

Short answer

A production-to-test (P2T) refresh copies your production Fusion data and configuration over a test environment so you can test with realistic data. You request it through Oracle's cloud service request process for a chosen window, then reset users, integrations and schedules in test afterwards. Quarterly updates reach test environments first and production a few weeks later, according to a calendar Oracle publishes.

Applies to: Oracle Fusion Cloud Applications on Oracle-managed environments. Request mechanics, lead times and the exact release dates are set by Oracle and change, so check the current Oracle Cloud documentation and your service request portal.

How to plan and run a P2T refresh

  1. 1Decide why you need the refresh: regression test before a quarterly update, a data fix rehearsal, training or a new integration build.
  2. 2Confirm which test environment will be overwritten and tell everyone using it. Anything in it that is not in production will be lost.
  3. 3Submit the P2T request through Oracle's cloud service request channel for your tenancy, with the source, target, and a preferred date and time.
  4. 4Before the window, export any test-only setup, scripts, reports or personalisation you want to keep, because they are replaced.
  5. 5After the refresh, confirm the target is back and sign in with a security administrator.
  6. 6Fix environment-specific settings: integration endpoints, email and notification settings, scheduled processes, certificates, SSO and bank or payment connections that must not point at live partners.
  7. 7Mask or protect sensitive data if your policy requires it, and confirm users cannot send live communications from test.
  8. 8Run a smoke test of key flows (order to cash, procure to pay, work orders) before declaring the environment ready.

What P2T copies and what it changes

A refresh brings production data and setup into the target. That includes transactional data, configuration and users, which is why post-refresh clean-up matters. The target then looks like production, with the risk that it also acts like production if integrations are left active.

Treat the first hour after a refresh as a safety task: disable or repoint outbound integrations, stop scheduled jobs that send mail or files, and review who has access.

Post-refresh checklist

Reset passwords or SSO mapping as needed, reapply any test-only roles, re-create scheduled processes you want in test, and reconnect OIC or middleware to test endpoints.

Confirm profile options and email settings. Some organisations add a banner or naming convention so users never confuse test with production.

Quarterly update calendar

Fusion applications update on a quarterly cadence. Oracle applies the update to non-production environments first, then to production a few weeks later, on dates listed in the Oracle release schedule for your environment type. That gap is your regression testing window.

Use the published calendar for your own plan, and add your internal freeze dates and test cycles around it. Always take dates from Oracle's current schedule rather than a blog or a past year.

Timing the refresh around updates

A common pattern is to request a P2T shortly before the update lands in test, so you regress on fresh production data, or immediately after, if you need to prove the new release against current data.

Avoid refreshing during a project test cycle unless you have exported what you need to keep. Coordinate with implementation partners.

Try it here, free

Oracle Fusion Quarterly Update Test Checklist

Open full tool

A step-by-step regression checklist for each Oracle Fusion Cloud quarterly update, from release notes review to production sign-off.

Common pitfalls

  • !Overwriting a test environment that holds unsaved project work.
  • !Leaving integrations pointed at live partners after a refresh.
  • !Scheduled processes sending real email or files from test.
  • !Relying on release dates from an old year instead of the current schedule.
  • !Skipping a smoke test and discovering broken flows during user testing.

How an ERP-grounded AI assistant handles this

An assistant can turn the post-refresh checklist into a repeatable check: it compares integration endpoints, scheduled processes, email settings and roles between test and the intended baseline and lists the differences for a person to approve. Release notes can be summarised against your own customisations. The language model can run privately so configuration and user data stay inside your network.

Frequently asked questions

What is P2T in Oracle Fusion?

P2T stands for production to test. It copies production data and setup into a non-production environment so you can test with realistic data.

How do I request a production to test refresh?

Submit a request to Oracle through your cloud service request channel, naming the source and target environments and a preferred window. Lead time and rules come from Oracle, so check the current guidance.

When do Oracle Fusion quarterly updates reach production?

Oracle updates test environments first and production a few weeks later on published dates. Use Oracle's current release schedule for your environment, not a past year.

What should I do right after a P2T?

Disable or repoint integrations, review scheduled processes and email settings, reset users and roles, and smoke test key flows before anyone uses the environment.

Related

How-to

Extend Oracle Fusion Safely With Sandboxes And Visual Builder Studio

Fusion customizations - a new field, a validation rule, a redesigned page layout, or a standalone custom app - are built inside a sandbox, an isolated workspace that lets you make and test changes without affecting other users until you explicitly publish. Application Composer handles fields, objects, and business rules; Visual Builder Studio builds new standalone pages and full custom applications that can embed inside or sit alongside Fusion.

How-to

Connect Oracle Integration Cloud (OIC) To Fusion ERP

OIC connects to Fusion ERP primarily through the prebuilt ERP Cloud Adapter, which wraps Fusion's REST and SOAP web services with OAuth-based authentication and pick-list discovery of available business objects and operations, instead of you hand-building every REST call. Use the adapter for standard integrations; drop to a generic REST or SOAP adapter only when the ERP Cloud Adapter does not yet expose the specific service you need.

Error fix

Clear An Oracle Fusion ESS Job Stuck In Blocked Status

A Blocked status on an Oracle Fusion Enterprise Scheduler (ESS) job almost always means an earlier instance of the exact same job is still running or stuck, and the job definition does not allow simultaneous requests. Find and finish, or cancel, the earlier request first; only then does the Blocked request move to Running.

Error fix

Fix The Oracle Fusion "You Don't Have Access To This Data" Error

This generic Oracle Fusion security message means the function privilege and the data security scope did not both line up for that user on that record - most often the job role is assigned but the matching data role, security profile, or business unit and ledger context in Manage Data Access for Users is missing. Fix it by checking data access setup for the user's role, not by re-granting the same job role again.

Error fix

Fix FBDI Import Failures From Interface Table Validation Errors

When a Fusion FBDI import job errors out, the cause is almost always bad data in the interface tables (an invalid value set, a wrong date format, or a missing required column), not the ESS job itself. Open the process's Interface Errors Report or the Correct Import Errors spreadsheet to see the exact rejected rows and reason codes, fix the source data, and resubmit from the interface tables instead of re-running the whole FBDI load.

How-to

OTBI vs BI Publisher: Which One Should You Use

Use OTBI when a business user needs ad hoc, self-service, real-time analysis with no fixed layout. Use BI Publisher when you need a pixel-perfect, scheduled, high-volume, or externally distributed document such as an invoice, check, or statutory report. Most Fusion implementations end up using both, not one instead of the other.

AI for ERP

Fusion Cloud ERP AI: OCI Generative AI Service vs. a Private LLM

How Fusion Cloud ERP AI supports GenAI implementation: OCI Generative AI Service for Fusion-only use cases, a private LLM for sensitive or cross-system data.

AI for ERP

Oracle ERP AI Consulting: What a Partner Should Deliver

Choosing an Oracle JDE partner for AI: what to demand across JD Edwards (Orchestrator, AIS), EBS, NetSuite and Fusion Cloud, plus the buyer questions to ask.

Stuck on Oracle Fusion Cloud Applications?

Talk to engineers who work inside Oracle Fusion Cloud Applications every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

AI on your ERP

Integrations

Comparisons

Software