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

> Source: https://netray.co/erp-help/oracle-fusion-production-to-test-refresh-and-quarterly-release-dates
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## 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.

## Kind

how-to

## System

oracle-fusion

## Erp

Oracle Fusion Cloud Applications

## Module

Environment Management / Quarterly Updates

## Query

oracle fusion production to test

## Alternate Queries

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

## 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.

## Steps

### How to plan and run a P2T refresh

**Items:**

- Decide why you need the refresh: regression test before a quarterly update, a data fix rehearsal, training or a new integration build.
- Confirm which test environment will be overwritten and tell everyone using it. Anything in it that is not in production will be lost.
- Submit the P2T request through Oracle's cloud service request channel for your tenancy, with the source, target, and a preferred date and time.
- Before the window, export any test-only setup, scripts, reports or personalisation you want to keep, because they are replaced.
- After the refresh, confirm the target is back and sign in with a security administrator.
- Fix 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.
- Mask or protect sensitive data if your policy requires it, and confirm users cannot send live communications from test.
- Run a smoke test of key flows (order to cash, procure to pay, work orders) before declaring the environment ready.

## Sections

### What P2T copies and what it changes

**Body:**

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

**Body:**

- 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

**Body:**

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

**Body:**

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.

## 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.

## Ai Angle

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.

## Faq

### What is P2T in Oracle Fusion?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

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

## Search terms

oracle fusion production to test, oracle fusion p2t, oracle fusion release dates, oracle fusion quarterly update, oracle fusion test environment refresh, fusion cloud environment refresh, oracle fusion release schedule

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json