Environment Refresh

Service Entitlement Policy

July 2023
Copyright © 2023, Oracle and/or its affiliates
Confidential – Public
TABLE OF CONTENTS
DISCLAIMER 3
OVERVIEW 4
WHY REFRESH YOUR NONPRODUCTION ENVIRONMENTS 4
BEFORE REQUESTING YOUR ENVIRONMENT REFRESH 5
Requirements 5

WHEN SHOULD YOU SUBMIT YOUR REQUEST FOR AN ENVIRONMENTAL

REFRESH? 5
Picking a Time for your Refresh 5
Blackout Periods 5
Quarterly Update Schedule 6
Product-Specific Considerations 6

HOW TO REQUEST AN ENVIRONMENT REFRESH 6

WHAT HAPPENS AFTER YOU LOG AN ENVIRONMENT REFRESH REQUEST? 7
PREPARING YOUR ENVIRONMENTS FOR THE ENVIRONMENT REFRESH 7
HOW TO VALIDATE SERVICE FULFILLMENT 7
ADJUSTING YOUR ENVIRONMENTS AFTER THE ENVIRONMENT REFRESH 8
FREQUENTLY ASKED QUESTIONS 8
RELATED INFORMATION ON MY ORACLE SUPPORT 8
APPENDIX A: WHAT IS COPIED DURING ENVIRONMENT REFRESH 9
Data Copied 9
Data Not Copied 9

APPENDIX B: UNDERSTANDING BLACKOUT PERIODS 11

Quarterly Updates 11
Monthly Maintenance Packs 11
Data Masking and Different Data Centers 12
Example 12

APPENDIX C: UNDERSTANDING PRODUCT IMPLICATIONS 14

APPENDIX D: PREPARING AND ADJUSTING YOUR ENVIRONMENTS BEFORE
AND AFTER ENVIRONMENT REFRESH 15
Preparing Your Environments Before Refresh 15
Adjusting Your Environments After Refresh 16

Environment Refresh
2 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
DISCLAIMER
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of
Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software
license and service agreement, which has been executed and with which you agree to comply. This document and
information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without
prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in planning for the implementation
and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and
should not be relied upon in making purchasing decisions. The development, release, and timing of any features or
functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this document
without risking significant destabilization of the code.

Environment Refresh
3 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
OVERVIEW
An environment refresh copies data from a source environment, usually production, to a target environment, usually
nonproduction, making a copy of the source environment. Environment refreshes ensure a predictable experience during
testing activities by providing a comparable nonproduction environment for testing and validation, before applying changes
to your production environment.
Two refresh services are available:
 Production-to-Test (P2T): Refresh from a production (source) environment to a nonproduction (target)
environment.
 Test-to-Test (T2T): For those customers with multiple nonproduction environments, refresh from one
nonproduction environment to another.
You should use an Oracle data migration tool to move data from a nonproduction (test) environment to a production
environment. Test-to-Production (T2P) environment refreshes from nonproduction (source) to a production (target) are
generally not supported, because of the permanent loss of production data in the target environment. In very specific
circumstances, you can request a nonproduction to production environment refresh (T2P). To see if a T2P refresh is allowed
for your environments, file a service request (SR). We’ll work with you to determine if this is the best solution for you.
See Appendix A for a list of what is copied during an environment refresh.

WHY REFRESH YOUR NONPRODUCTION ENVIRONMENTS

Environment refreshes address several business objectives during your implementation lifecycle and ongoing use of the
Oracle Cloud Applications Service. They provide a copy of an environment to support the following scenarios:
 Update your nonproduction environment with your production data to support ongoing extension and
configuration changes, testing, and maintenance work.
 Refresh your nonproduction environment to reflect your production environment before applying an update to
your nonproduction environment so you can test before cutting over to the new release in your production
environment.
 Refresh a nonproduction environment whenever you need to reestablish a new baseline for such purposes as
initiating a new project and replacing test data that is no longer useable.
 If you have multiple nonproduction environments, copy content from one nonproduction environment used for
development purposes to another used for testing.

Environment Refresh
4 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
BEFORE REQUESTING YOUR ENVIRONMENT REFRESH
Before you submit your request for an environment refresh, you should know what the requirements are for a successful
environment refresh as well as how much time in advance you need to submit your request. It’s also important to
understand when you can’t schedule a request; those times are known as blackout periods.

Requirements
Before your environment refresh can begin, we check to ensure the following conditions are met:
 Source and Target Environments Must Match Update Levels: This includes Quarterly Updates, Monthly Updates
and Exception Updates.
 Certain Source and Target Environment Service Entitlements Must Match: If you have any of the following
service entitlements, they must be present and at the same update level in both environments.
− Oracle Database Vault, available stand alone and included with Break Glass
− HIPAA

See Oracle HIPAA Service Entitlement (Doc ID 2510080.1) for more information.
Note: Oracle Support checks to make sure all requirements are met. You’ll be contacted if there are any problems with your
environment refresh request.
Important! If you’re approved to receive additional updates or patches, applying them will put your environments out of sync
and may result in cancellation of the scheduled environment refresh. This means your environment refresh request can’t be
fulfilled until both environments are again at the same update level after the blackout period.

WHEN SHOULD YOU SUBMIT YOUR REQUEST FOR AN ENVIRONMENTAL

REFRESH?
It’s important for you to submit your Environment Refresh with enough lead time to fill your request.
Generally, you must submit your request at least 3 weeks before you want the refresh to occur, however there are some
cases that require more time. Environment refreshes are scheduled on a first come first served basis. To reserve your
desired refresh date, enter your refresh request as early as possible.
If you have a coordinated Taleo-Fusion refresh because you use the delivered integration between Oracle Fusion HCM and
Taleo Recruiting Cloud services, you must submit your request at least 6 weeks in advance.

Picking a Time for your Refresh

When you choose a time for your environment refresh, you should think about both blackout periods and product-specific
considerations.

Blackout Periods
There are times when we can’t provide an environment refresh for your environment. These times are known as blackout
periods. You can’t schedule your refresh within a blackout period.
All customers are subject to the blackout period around Quarterly Updates. The following table shows the blackout days
when the source and target environments are on the same update schedule (for example, they’re on concurrent
maintenance) and when the source and target are on different update schedules.
If you don’t know what your update schedule is, contact your service administrator or look it up on One Console. For more
information on concurrent maintenance, see Oracle Cloud Applications Concurrent Maintenance Option, Doc ID 1646394.1.

Environment Refresh
5 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
Quarterly Update Schedule
SAME UPDATE SCHEDULE DIFFERENT UPDATE SCHEDULE
(CONCURRENT MAINTENANCE)

BLACKOUT START Monday immediately before the Friday
DATE Quarterly Update start date
Middle East only: Sunday immediately
before your Quarterly Update start date
Monday immediately before the Friday
nonproduction Quarterly Update start
date
Middle East only: Sunday immediately
before your non production Quarterly
Update start date

BLACKOUT END DATE Monday immediately after the Friday
Quarterly Update start date
Middle East only: Sunday immediately
after your Quarterly Update start date
Monday immediately after the Friday
production Quarterly Update start date
Middle East only: Sunday immediately
after your production Quarterly Update
start date

Important: There are additional Blackout periods that might be applicable based on your specific configuration and
environment. It’s important you review and understand the blackout periods that pertain to your environment. For detailed
information about blackout periods and when they occur, see Appendix B.
Oracle Support checks to make sure your environment refresh doesn’t fall into any blackout periods and adheres to any
product requirements. If you opt into additional exception maintenance, your refresh schedule might be impacted.
You’ll be contacted if there are any problems with your environment refresh request.

Product-Specific Considerations
If you have any of the following products or services, see Appendix C for detailed information about their special
considerations when scheduling your environment refresh.
 Fusion-Taleo Recruiting Integration
 Data Masking
 Oracle Transactional Business Intelligence Enterprise (OTBI-E)
 Data integrations

HOW TO REQUEST AN ENVIRONMENT REFRESH

Before you begin, verify that your environment refresh request is in alignment with your organization’s environment
management and implementation plan, and all interested parties have been notified of the refresh.
To request an environment refresh, you must sign into My Oracle Support (MOS) and create a Service Request (SR). For
detailed steps on how to create a service request (SR), see Instructions on Submitting a Cloud Service Request (SR) in My
Oracle Support (Doc ID 2120276.1). When creating your request, you’ll be prompted to answer the following questions that
are specific to this Cloud service:

SECTION ENTER

Where is the problem? Select the Cloud tab

Service Type Select your service

Environment? Enter your environment

Environment Refresh
6 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
 SECTION ENTER

Select Problem Type: Cloud Hosting Services (Outage,P2T/T2T,Enable

SSO, Resize, Cloud Portal, MyServices,
User/Password, Network, Schedule Maintenance)

Question 1- Select Area of Concern Environment Refresh (Production to Test, Test to

Test or other environment refresh related issues.

Question 2 – Indicate the Area for this issue Standard Production-to-Test (P2T), Test-to-Test
(T2T) copy.

Continue answering the questions presented to you in the SR and then submit your refresh request. As part of your request,
you will need to provide your source and target environment names and links.

WHAT HAPPENS AFTER YOU LOG AN ENVIRONMENT REFRESH REQUEST?

Your environment refresh SR is used to schedule the environment refresh and will remain open until it has been completed.
Your request will take 3-4 business days for review, initial approval, and scheduling. Environment refresh scheduling is done
on a first-come, first-served basis.
Plan for your target environment to be down for up to 48 hours during the refresh. There’s no downtime for the source
environment.
You need a minimum notice of 3 days to cancel a scheduled environment refresh.
We’ll contact you if there are any problems with your environment refresh request. Here are some examples of why we
might contact you:
 Your source and target environments aren’t at the same update levels.
 The date you requested is not feasible.
 You need more lead time because of unique conditions in your environment. See Appendix B: Understanding
Blackout Periods and Appendix C: Understanding Product Implications for more information.

If we don’t have any questions about your request, the next time you’ll hear from us is the Oracle Service Outage Notification
communication email, which will be sent out just before your environment refresh copy starts on your target environment.
You’ll also receive a notification after your environment refresh completes and the target environment is available for use.
Create a new SR if you find issues with your environment after the refresh.

PREPARING YOUR ENVIRONMENTS FOR THE ENVIRONMENT REFRESH

Before your environment refresh starts, you should prepare your environments for the refresh. See Appendix D for more
information.

HOW TO VALIDATE SERVICE FULFILLMENT

Once you receive the notification that your environment refresh is complete, here are the steps to make sure the
environment refresh was successful.
1. Sign in to the target environment and verify that the Oracle data matches the data from the source environment using a
sample data set and setup.
2. Use the Security Console to verify that all functions available to your users in the source environment are the same in
the target environment.
3. You may want to run a report that your team has developed using OTBI or an equivalent business intelligence tool.
4. If you requested data masking, query any person on the database through the user interface and verify that their email
address is sendmail-test-discard@oracle.com.

Environment Refresh
7 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
ADJUSTING YOUR ENVIRONMENTS AFTER THE ENVIRONMENT REFRESH
After your environment refresh completes, you might have to make some adjustments to your environments. For detailed
information, see Appendix D.

FREQUENTLY ASKED QUESTIONS

Will my source environment be available during the environment refresh?
Yes. Environment refreshes require downtime only for the target environment
How much time is needed to cancel the environment refresh?
At least 3 days’ notice is required to cancel an environment refresh.
How far in advance do I need to give Oracle to schedule the environment refresh?
You should schedule at least 3 weeks in advance. You can schedule the environment refresh up to 12 weeks in advance.
How long does an environment refresh take?
The target environment will be down for up to 48 hours.
Can an environment refresh be completed during a blackout period?
No, unless both environments are on the same maintenance schedule. If this is the case, see Appendix B: Understanding
Blackout Periods for when a refresh can be scheduled.
When does Oracle take a backup of the source environment for use in the refresh?
Oracle takes a backup of the source environment at the start time of the environment refresh system outage notification.
Data entered into the source environment before that time will be included in the refresh.
Will email notifications be disabled in the target environment?
For P2T environment refresh, the email notifications will be disabled on the target environment. The source environment
email notifications will remain unchanged. If you need the target environment's email notifications turned on, use the
Applications Console.
What happens to the user security setup during environment refresh?
Environment refresh migrates your user security setup from the source environment to the target environment by removing
all users and roles information from the target environment and copying that information over from the source
environment. If you’ve enabled Single Sign-on on the source environment but not on the target environment, your users
won’t be able to logon to the target because passwords won’t be available. You need to open a service request (SR) to reset
the password for the administrator, who can then reset the password for all other users after the environment refresh
completes.

RELATED INFORMATION ON MY ORACLE SUPPORT

 Oracle Cloud Applications Service Entitlements, Doc ID 2004494.1
 Oracle Cloud Applications Concurrent Maintenance Option, Doc ID 1646394.1
 Oracle Cloud Applications – Fusion Applications Update Policy, Doc ID 1966109.1
 Cloud Service Requests and Fulfillment for Oracle HCM Cloud Service (Taleo Zone Refresh with Fusion HCM
Environment Refresh), Doc ID 2108681.1
 Oracle Cloud Applications - Data Masking Standalone Service Entitlement, Doc ID 2092389.1

Environment Refresh
8 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
APPENDIX A: WHAT IS COPIED DURING ENVIRONMENT REFRESH
During an environment refresh, almost all data is copied.
There are some exceptions to this general rule and some possible implications for you. The following tables list what is and
is not copied.

Data Copied
APPLICATION OBJECT EXAMPLE

All data in the Fusion schema Transactional data and functional setup

Webcenter content File attachments and inbound and outbound Integration

files

Key artifacts managed through Fusion Middleware User interface extensions managed as Application
Metadata Services (MDS) Development Framework (ADF) sandboxes, such as
Flexfields and workflow/approval extensions managed by
the Service-Oriented Architecture (SOA) Suite

Business Intelligence Web catalog and Repository Entire catalog is copied

Definitions (RPDs)

Non-system users groups, roles, and policies Application users, all groups, all roles, and all policies

Pre-compiled FastFormula used by the HCM Cloud Services

Enterprise Scheduler Service (ESS) definition and metadata

Data Not Copied

APPLICATION OBJECT EXAMPLE

Compiled objects Fusion Applications binaries, Fusion Middleware binaries,

and for HCM Cloud Services customers, compiled
FastFormula

Home page notifications Approval requests

Data-maintained in the Functional Setup Manager’s (FSM) Endpoint URLs to other environments
Topology Manager

Enterprise Scheduler Service (ESS) process parameters Instance data is not copied

Some schemas FUSION_IPM

FUSION_BIPLATFORM
FUSION_ORASDPLS
FUSION_ORASDPXDMS
FUSION_ORASDPSDS
FUSION_ORASDPM

Environment Refresh
9 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
 APPLICATION OBJECT EXAMPLE

Files and binaries in file system Java files, scripts, and executables in the file system

Pod-specific data Examples include long-running workflows, SOA transaction

tables, and system audit data

Learning Content Data loaded with Manage Catalog Resources is not copied,
such as SCORM, AICC, PDF, and web links

Environment Refresh
10 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
APPENDIX B: UNDERSTANDING BLACKOUT PERIODS
Blackout periods are the time during which Oracle cannot provide an environment refresh. The following tables describe
blackout period rules.
Important: Your environment might require a longer blackout period than listed below. We’ll contact you if this is ever the
case for you.

Quarterly Updates
The following tables show the blackout days when the source and target environments are on the same update schedule
(for example, they’re on concurrent maintenance) and when the source and target on different update schedules.
If you don’t know what your update schedule is, contact your administrator. For more information on concurrent
maintenance, see Oracle Cloud Applications Concurrent Maintenance Option, Doc ID 1646394.1.

D SAME UPDATE SCHEDULE DIFFERENT UPDATE SCHEDULE

CONCURRENT MAINTENANCE

BLACKOUT START Monday immediately before the Friday Quarterly Monday immediately before the Friday
DATE Update start date nonproduction Quarterly Update start date
Middle East only: Sunday immediately before your Middle East only: Sunday immediately before
Quarterly Update start date your nonproduction Quarterly Update start
date

BLACKOUT END Monday immediately after the Friday Quarterly Monday immediately after the Friday
DATE start date production Quarterly start date
Middle East only: Sunday immediately after your Middle East only: Sunday immediately after
Quarterly Update start date your production Quarterly Update start date.

Monthly Maintenance Packs

The following table show the blackout days when the source and target environments are on the same update schedule (for
example, they’re on concurrent maintenance) and when the source and target on different update schedules.
If you don’t know what your update schedule is, contact your administrator. For more information on concurrent
maintenance, see Oracle Cloud Applications Concurrent Maintenance Option, Doc ID 1646394.1.

D SAME UPDATE SCHEDULE DIFFERENT UPDATE SCHEDULE

CONCURRENT MAINTENANCE

BLACKOUT START Tuesday immediately before your Monthly Update Tuesday immediately before your
DATE start day nonproduction Monthly Update start day
Middle East only: Monday immediately before Middle East only: Monday immediately before
before your Monthly Update start day your non-production Monthly Update start
day.

BLACKOUT END Sunday immediately after your Monthly Update Sunday immediately after your production
DATE start day monthly update start day
Middle East only: Saturday immediately after your Middle East only: Saturday immediately after
monthly update start day your monthly production update start date

Environment Refresh
11 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
Data Masking and Different Data Centers
The blackout period begins 7 days before a Quarterly Update if you have any of the following:
 Data masking
 Environment refresh is hosted in a different data center than the environment

Example
In this example, the target environment is patched on the first Friday of the month and the source environment is patched
on the 3rd Friday of the same month. The example shows the environment refresh blackout periods in two consecutive
months if you take only Quarterly Updates and don’t take any other updates or have other considerations.
The first sample calendar shows the blackout period for a Quarterly Update. The second sample calendar in this example
shows the blackout period for the month following a Quarterly Update month. Notice that this month has no blackout
period.

Quarterly Update Month

Sun Mon Tue Wed Thu Fri Sat

30 31 1 2 3 4 5
Blackout Blackout Blackout Blackout Blackout Blackout Blackout
Period – Period (All Period (All Period (All Period (All Period (All
Period (All
regions) regions) regions) regions) regions)
(Middle East regions)
Only)

6 7 8 9 10 11 12
Blackout Blackout Blackout Blackout Blackout Blackout Blackout
Period (All Period (All Period (All Period (All Period (All Period (All Period (All
regions) regions) regions) regions) regions) regions) regions)

13 14 15 16 17 18 19
Blackout Blackout Blackout Blackout Blackout Blackout Blackout
Period (All Period (All Period (All Period (All Period (All Period (All Period (All
regions) regions) regions) regions) regions) regions) regions)

20 21 22 23 24 25 26
Blackout
Period –
(Except in
Middle East)

27 28 29 30

Environment Refresh
12 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
 Month Following Quarterly Update Month
Sun Mon Tue Wed Thu Fri Sat
1 2 3

4 5 6 7 8 9 10

11 12 13 14 15 16 17

18 19 20 21 22 23 24

25 26 27 28 29 30 31

Environment Refresh
13 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
APPENDIX C: UNDERSTANDING PRODUCT IMPLICATIONS
The following table describes special considerations for your environment refresh based on your products and environment
circumstances.

PRODUCT SPECIAL CONSIDERATIONS

Fusion-Taleo Recruiting Do not request this service if you require a coordinated refresh. See more
Integration details in Oracle HCM Cloud Service Definition: Taleo Zone Refresh with
Fusion HCM Environment Refresh (P2T) (Doc ID 2108681.1).

Data Masking There are 2 data-masking scenarios.

• Scenario 1: You want the environment refresh and data masking
service to occur as a combined activity. In this scenario, complete
a single SR for both. Data migrated to a test environment using an
environment refresh is masked as part of the environment refresh
fulfillment process.
• Scenario 2: You need to add or change data after it is migrated
using an environment refresh, but before data masking is applied.
With this scenario, you must submit two SRs: one to request the
environment refresh service and one to request the data masking
standalone service. If you need only data masking without an
environment refresh, refer to Oracle Cloud Applications - Data
Masking Standalone Service Entitlement on My Oracle Support
(Doc ID 2092389.1).
Always submit an SR to request these environment refreshes.

Data integrations, such as HCM Carefully coordinate the Oracle Cloud Applications Environment Refresh with
Cloud Service data loading tool, the other system’s content migration capability, such as for cloning or another
to move data between your refresh. If you do not synch these processes, data integrity issues may surface
Oracle Cloud Applications in the target environment. To avoid this:
environment and your system
 Pair your integrated production environments together and your
of record
integrated nonproduction environments together. Establish this
pairing early in your implementation and do not change it, if possible.
 Do not run any integration processes between the two systems, once
the first content migration process has started, until the other system’s
similar process has completed.
 Schedule your refresh to coincide with the other system’s content
migration solution. The closer in time they complete, the sooner you
can process integrations between the paired environments.
 Review and change any setup or configuration in the target
nonproduction environment that point to a production environment.
Instead, point to the other paired nonproduction environment.
After both processes have completed, resume your integration processes.

For more information, review the following My Oracle Support articles: Oracle Cloud Applications – Fusion Applications
Update Policy (Doc ID 1966109.1) and Oracle Cloud Applications - Concurrent Maintenance (Doc ID 1646394.1).

Environment Refresh
14 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
APPENDIX D: PREPARING AND ADJUSTING YOUR ENVIRONMENTS BEFORE AND
AFTER ENVIRONMENT REFRESH

Preparing Your Environments Before Refresh

Before your environment refresh starts, you should prepare your environments for the refresh.
Export data from your target environment that you want to save and restore later. Here are some examples of things you
might want to export:

OBJECT NOTES

User interface extensions To retain in-process UI extensions, export them from the target environment
maintained in ADF sandboxes before the environment refresh. After the refresh is complete, you will import
them back.
See Oracle Applications Extensibility Guide for Business Analysts for
instructions.

Functional setup, including To retain some functional setups, export the setups from the target
HCM FastFormula environment before the environment refresh. After the refresh is complete,
you will import the setups back.
See FSM’s Configuration Package capability for instructions.

Business Intelligence To retain custom BI objects, export them from the target environment before
definitions the environment refresh. After the refresh is complete, you will import them
back.
See the BI archive/unarchive facility for instructions.

HCM Extract definitions To retain custom HCM Extract definitions, export them from the target
environment before the environment refresh. After the refresh is complete,
you will import them back.
See the export/import function on the Manage HCM Extracts Definition user
interface for instructions

Oracle Transactional Business Turn off all OTBI-E loads during the period scheduled for the environment
Intelligence Enterprise (OTBI-E) refresh.
Run the OTBI-E full load process after the environment refresh is complete.
Allow the OTBI-E incremental load to handle subsequent changes.

BICC Extract Definitions To retain custom BICC Extract definitions, export them from the target
environment before the environment refresh using the Export Customization
/ Import Customization in the Manage Offerings and Data Stores user
interface.

Environment Refresh
15 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
Adjusting Your Environments After Refresh
After your refresh is complete, you might need to take the following steps before releasing your environment to users.

Change the password for the Admin user account

We recommend that you have different Admin (e.g. FAADMIN) user passwords for Cloud environments.

Disable or Re-route Notifications

Email notifications are disabled on the target environment for P2T refreshes. For T2T, we can only redirect all new hire email
notification to single email address (see Document 1615501.1), or redirect all workflow notification to single email address
(see Document 1473706.1) Use the Applications Console to turn email notifications on.

Change the Global Page Template to reflect nonproduction color and naming scheme
We recommend that you change the Global Test Page template to a nonproduction template, so users know which
environment they’re accessing. This is especially useful if you have multiple nonproduction environments.

Set up any custom ESS Jobs required for this pod’s use
ESS Job Definitions aren’t copied to the target environment. You should set up any custom jobs required for this
environment.

Set up Seeded ESS Jobs (submit for execution and schedule daily)
ESS Job Definitions aren’t copied to the target environment. Here are some jobs that we recommend you run after the
refresh:
 Synchronize Person Records
 Update Person Search Keywords
 Refresh Manager Hierarchy
 Send Pending LDAP Requests
 Retrieve LDAP Request
 Import User and Role Application
 Security Data
ESS process parameters
After the environment refresh, review the process parameters in the target for your key ESS processes. Reestablish
scheduling and reset those default parameters (for example, the number of threads) you want to change.
EssBase cubes
Create EssBase cubes in the target environment after the environment refresh, by submitting standard jobs through the
Scheduler page.
As an example, follow the steps below to create a Ledger EssBase cube:
1. Sign in to the Oracle Cloud Applications Home Page
2. In the Navigator menu, select Tools > Scheduled Processes
3. Select Schedule New Process.
4. Select Search in the search window.
5. Search for "Create General Ledger Balances Cube".
Select the item in the results set, then click OK, and then OK again
6. Enter the details of the Chart of Accounts: Name, Calendar and Starting Period, and then click Close.
7. Repeat this process for all Ledger cubes.
Update links to external applications or services (3rd Party, EPM, OTM, ICS, etc.)
After a P2T, your target environment will have links to production 3rd party applications or services. It’s important that you
link your test environment to the corresponding 3rd party integration test environments.

Environment Refresh
16 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
Disable production-only users
Follow the directions in MOS Note: Doc ID 1494265.1 to clean up user data in an Oracle Cloud application environment.
Use the REST API for managing users (Create, Update, Delete, and View).

Load deployment-only (nonproduction) users

Refer to the User Data Import from Legacy Applications in Application Users Management. Console.
Use the REST API for managing users (Create, Update, Delete, and View).

Grant proper roles to deployment-only users

Refer to the User Data Import from Legacy Applications in Application Users Management Console.

Grant additional roles to users that were in production

Refer to the User Data Import from Legacy Applications in Application Users Management Console.
Use the REST API for managing users (Create, Update, Delete, and View).

Method for exporting and re-importing development work

Use Rapid Implementation Templates to reload configuration data, though there’s not 100% coverage. Unpublished
Sandboxes aren’t overwritten with P2T.
• Configuration Data
• Logos and Home Page
• Customizations

Environment cloning considerations

Payments stores the master encryption key and other security credentials in Oracle Platform Security Services (OPSS). When
an environment is cloned with another environment using methods such as production-to-test (P2T), test-to-production
(T2P), test-to-test (T2T), and so on, the data from the source environment in OPSS isn’t automatically replicated to the target
environment. Following the cloning, system administrator must immediately perform the following actions in the target
environment:
• Wallet Migration: The payments wallet contained in the OPSS repository won’t be migrated during a P2T
environment refresh. The wallet must be migrated from the source to the target environment using the steps
mentioned in the MOS note Payments Wallet Migration Post P2T/T2T Refresh (Doc ID 2407678.1).
• Edit transmission configuration details to ensure they point to the right destination. If the target environment is a
test environment, you must confirm that details such as host/IP, port, username, client private key file, remote
directory, and so on are pointing to the test environment provided by the bank or payment gateway. This step is
optional if you’re using the data masking service.
Note: End-dating the transmission configuration won’t prevent its usage if these transmission configuration details were
already associated with a payment process profile or a fund capture process profile. It’s mandatory to update the
transmission configuration with the correct destination details for the refreshed environment.
Important: Do not run any payment batches in a cloned environment until you have migrated the wallet and updated
transmission configuration details. If you do run payment batches, you may accidentally send payment files to the bank’s
production server.

OTBI
Are you using Oracle Transactional Business Intelligence-Enterprise (OTBI-E)? If yes, Oracle recommends that you:
• Run the OTBI-E full load process after the environment refresh is complete.
• Allow the OTBI-E incremental load to handle subsequent changes.

User interface extensions maintained in ADF sandboxes

If you exported in-process UI extensions before the refresh began, you will need to import them back after the refresh
completes.

Environment Refresh
17 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
See Oracle Applications Extensibility Guide for Business Analysts for instructions.

Functional setup, including HCM FastFormula – Precompiled

If you exported functional setup before the refresh began, you will need to import setups back after the refresh completes,
using FSM’s Configuration Package capability.

HCM FastFormula – Compiled

After the environment refresh, compile all FastFormula using the Compile Formula process that does so.

Environment Refresh
18 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
Business Intelligence definitions
If you exported custom BI objects before the refresh began, you will need to import them back after the refresh completes,
using the BI archive/unarchive facility.

HCM Extract definitions

If you exported custom HCM Extract definitions before the refresh began, you will need to import them back after, using the
export/import function on the Manage HCM Extracts Definition user interface.

BICC Extract definitions

To restore custom BICC Extract definitions back into target environment after the refresh, import the exported file(s) using
the Export Customization / Import Customization in the Manage Offerings and Data Stores user interface.

Learning Content
Some Learning online learning content is not copied during the Environment Refresh. You will need to move this data after
your Environment Refresh is complete.
Risk Management
If you used Risk Management Advanced Controls to analyze the source environment, and will use them to analyze the target
environment:
1. Log into the target environment.
2. Navigate to Risk Management > Setup and Administration > Global User Configuration > Global Users, and select
Actions > Run.
3. Once that job completes, navigate to Risk Management > Setup and Administration > Advanced Controls
Configurations > Transaction and Audit Performance Configuration, and tap on Rebuild Graph.
4. Once that job completes, navigate to Risk Management > Advanced Controls > Controls, select all active controls,
then select Actions > Run.

Environment Refresh
19 Copyright © 2023, Oracle and/or its affiliates | Confidential – Public
CONNECT WITH US
Call +1.800.ORACLE1 or visit oracle.com.
Outside North America, find your local office at oracle.com/contact.

blogs.oracle.com facebook.com/oracle twitter.com/oracle

Copyright © 2023, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without
notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties
and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed
either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without
our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group. 0120

Environment Refresh
July 23