Oracle Cloud Applications

Fusion

Environment Refresh
Enterprise Operational Policy

April 2020
 Contents

Overview ...................................................................................................................... 4

Why Refresh Your Nonproduction Environments?....................................................... 4

Before Requesting Your Environment Refresh ............................................................ 5

Requirements .................................................................................................... 5

When Should You Submit Your Request for an Environment Refresh? ...................... 5

Picking a Time for your Refresh ........................................................................ 6

How to Request an Environment Refresh .................................................................... 7

What Happens After You Log an Environment Refresh Request?............................... 9

Preparing Your Environments for the Environment Refresh ........................................ 9

How to Validate Service Fulfillment .............................................................................. 9

Adjusting your Environments after the Environment Refresh ..................................... 10

Frequently Asked Questions ...................................................................................... 10

Related Information on My Oracle Support ................................................................ 11

Appendix A: What Is Copied During Environment Refresh ........................................ 12

Appendix B: Understanding Blackout Periods............................................................ 14

Quarterly Updates ........................................................................................... 14

Monthly Maintenance Packs: .......................................................................... 15

Data Masking, Break Glass, and Different Data Centers ................................ 15

Example .......................................................................................................... 16

Appendix C: Understanding Product Implications ...................................................... 18

Appendix D: Preparing and Adjusting Your Environments Before and After
Environment Refresh ................................................................................................. 20

Preparing your Environments before Refresh ................................................. 20

Adjusting your Environments after Refresh ..................................................... 21

Overview
This paper applies to Enterprise operational policy holders. Find your Cloud Service operational policy
on the Overview tab on the Service Details page in the Applications Console.
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.

4
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 Monthly Updates
if you’ve opted in.
 Certain Source and Target Environment Service Entitlements Must Match: The following
service entitlements must be present and at the same update level in both environments if you’re
subscribed to them
 Oracle Database Vault
 Break Glass for Fusion Cloud Service
 Data Masking
 HIPAA
See the following documents for more information:
 Oracle Break Glass (Doc ID 2119149.1)
 Oracle Data Masking documents (Doc ID 2092389.1)
 Oracle HIPAA Service Entitlement (Doc ID 2510080.1)
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 Environment 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.
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.

5
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 administrator. For more information on
concurrent maintenance, see Oracle Cloud Applications Concurrent Maintenance Option, Doc ID
1646394.1.

Quarterly Update Schedule

Same Update Schedule Different Update Schedule

(Concurrent Maintenance)

Blackout Start Day Monday, 5 days before your Monday, 5 days before your
Quarterly Update start day Quarterly Update start day

Middle East only: Sunday, 5 days Middle East only: Sunday, 5 days
before your Quarterly Update before your Quarterly Update
start date start date

Blackout End Day Sunday, 3 days after your Sunday, 3 weeks after your
Quarterly Update start date Quarterly Update start date

Middle East only: Saturday, 3 Middle East only: Saturday, 3

days after your Quarterly Update weeks after your Quarterly
start date 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.

6
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

There are two ways to request an environment refresh: the online self-service Scheduling Tool and
logging an SR. The Scheduling Tool provides an automated way of logging an SR. It includes a
Schedule Maintenance calendar that shows you the dates the environment refresh can occur.
If you can’t or don’t want to use the Scheduling Tool, you can always log an SR.
Can you use the Scheduling Tool?
 The Service Administrator who submits the environment refresh request must have a My
Oracle Support (MOS) account for the Customer Support Identifier (CSI).
 You don’t have the following special considerations:
 data masking
 coordinated Fusion-Taleo refresh
To request an environment refresh using the Scheduling Tool:

1. Sign in to the Applications Console for the environment from which data will be refreshed. This is
referred to as the source environment.
2. Select Maintenance and Service Request, and then Create Request.
3. Follow the online instructions.
4. If you need further assistance, click Help about this page.
Once your request is submitted, an SR is created with Support. Work with Support using the SR as a
reference.
Here are some other considerations:
 After submitting a self-service environment refresh request, you can’t change or delete it via
the Applications Console. Instead, you must update the SR previously generated in MOS.
 The link displayed in the Applications Console for the environment refresh SR created by this
process will direct you to the standard MOS SR viewer. From the SR page, you can click
Switch to Cloud Support in the upper right-hand corner if you prefer that view.
 SRs generated by the self-service environment refresh process will appear in the Applications
Console Request.

7
  The target environment receives up to 48 hours of downtime during the refresh. There’s no
downtime for the source environment.
 There might be some blackout periods that aren’t included in the calendar due to conditions
unique to your environment. In any case, we’ll work with you to make sure your environment
refresh is scheduled properly.
To request an environment refresh using a Service Request (SR):
For detailed steps on how to file a service request (SR), see Instructions on Submitting a Cloud Service
Request (SR) in My Oracle Support Doc ID 2120276.1. When filing your request, you’ll be prompted to
answer the following questions that are specific to this Cloud service:

Section Enter

Confirm that you have read this document on Yes/No

My Oracle Support (Doc ID 1632261.1) and
that you understand the documented policies
and procedures contained in it.

Do you want data in the target environment to Yes/No

be masked as part of the environment refresh?
This option is available if you have subscribed
to the data masking service.
Confirm that you have read and understand,
HCM Cloud Service Definition – Data Masking
Standalone available on My Oracle Support
document, Doc ID 2092389.1.

Source and target Oracle applications [Your environment names]

environment identifiers

Desired Refresh Start Date
The date you’d like to have content refreshed
to the target/nonproduction environment. The
target environment will be down for up to 48
hours (without data masking) or up to 96 hours
(with data masking).

Have you reviewed scheduled ESS jobs to be Yes/No/Uncertain

terminated during the Refresh process?

a. Name Technical contact information for the person

Oracle Support should contact if there are any
b. E-mail questions or issues.
c. Cell phone number
d. Office phone number

Additional Information Any additional information that will help clarify

the timing and special considerations for this
request.

8
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 of 3 days’ notice to cancel a scheduled environment refresh.
Important! If you make any changes to the source or target environments or to the environment refresh
desired date, you must submit a new request, which will restart the 3-week lead-time.
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 e-mail, 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.
If any questions or issues need to be addressed after the environment refresh has completed, you must
create a new SR.

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

Here are the steps to make sure the environment refresh has successfully completed.
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.

9
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.
Can an environment refresh be completed during a blackout period?
No, unless you are on concurrent maintenance or requesting a T2T. If this is the case, it can be
scheduled any time except on the weekends, Thursday through Sunday, when updates occur. See
Appendix B: Understanding Blackout Periods.
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 e-mail notifications be disabled in the target environment?
For P2T environment refresh, the e-mail notifications will be disabled on the target environment. The
source environment e-mail notifications will remain unchanged. If you need the target environment's e-
mail 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.

10
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

11
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

Database 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 User interface extensions managed as

Middleware Metadata Services (MDS) Application Development Framework (ADF)
sandboxes, such as flexfields and
workflow/approval extensions managed by the
Service-Oriented Architecture (SOA) Suite

Business Intelligence Web Catalog and Entire catalog is copied.

Repository Definitions (RPDs)

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

Pre-compiled FastFormula used by the HCM

Cloud Service

Enterprise Scheduler Service (ESS) definition

and meta data

12
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 Endpoint URLs to other environments

Manager’s (FSM) Topology Manager

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

parameters

Some schemas FUSION_IPM

FUSION_BIPLATFORM
FUSION_ORASDPLS
FUSION_ORASDPXDMS
FUSION_ORASDPSDS
FUSION_ORASDPM

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 weblinks

13
Appendix B: Understanding Blackout Periods
Blackout periods are the time during which Oracle cannot provide the 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.

Same Update Schedule Different Update Schedule

(Concurrent Maintenance)

Blackout Start Day Monday, 5 days before your Monday, 5 days before your
Quarterly Update start day Quarterly Update start date

Middle East only: Sunday, 5 days Middle East only: Sunday, 5 days
before your Quarterly Update before your Quarterly Update
start date start date

Blackout End Day Sunday, 3 days after your Sunday, 3 weeks after your
Quarterly Update start date Quarterly Update start date

Middle East only: Saturday, 3 Middle East only: Saturday, 3

days after your Quarterly Update weeks after your Quarterly
start date Update start date

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

Same Update Schedule Different Update Schedule

(Concurrent Maintenance)

Blackout Start Day Thursday, 1 day before the first Thursday, 1 day before the first
Friday of the month that you Friday of the month that you
opted in for monthly updates opted in for monthly updates

Middle East only: Wednesday, 1 Middle East only: Wednesday, 1

day before the first Thursday of day before the first Thursday of
the month that you opted in for the month that you opted in for
monthly updates monthly updates

Blackout End Day Sunday, 3 days after the first
Friday of the month that you
opted in for monthly update.
Middle East only: Saturday, 3
days after your monthly update
start day
Sunday, 3 weeks after your
monthly update start date
Middle East only: Saturday, 3
weeks after your monthly update
start date

Data Masking, Break Glass, and Different Data Centers

The blackout period begins 7 days before a Quarterly Update if you have any of the following:
 Data masking
 Break glass is enabled
 Environment refresh is hosted in a different data center than the environment

15
Example
The following sample calendars show 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 month when
your source and target are on different update schedules. For 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
month.
The second sample calendar 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
(Middle East regions) regions) regions) regions) regions) 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

Month Following Quarterly Update Month

Sun Mon Tue Wed Thu Fri Sat
1 2 3

4 5 6 7 8 9 10

16
 Month Following Quarterly Update Month
Sun Mon Tue Wed Thu Fri Sat
11 12 13 14 15 16 17

18 19 20 21 22 23 24

25 26 27 28 29 30 31

17
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
Integration more 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.

18
 Product
Data integrations, such as
HCM Cloud Service data
loading tool, to move data
between your Oracle Cloud
Applications environment and
your system of record
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).
Special Considerations
Carefully coordinate the Oracle Cloud Applications Environment
Refresh with the other system’s content migration capability, such as
for cloning or another refresh. If you do not synch these processes,
data integrity issues may surface in the target environment. To avoid
this:
 Pair your integrated production environments together and your
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.
19
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
User interface extensions maintained in ADF
sandboxes
Functional setup, including HCM FastFormula
Business Intelligence definitions
HCM Extract definitions
Oracle Transactional Business Intelligence
Enterprise (OTBI-E)
Notes
To retain in-process UI extensions, export
them from the target environment before the
environment refresh. After the refresh is
complete, you will import them back.
See Oracle Applications Extensibility Guide for
Business Analysts for instructions.
To retain some functional setups, export the
setups from the target environment before the
environment refresh. After the refresh is
complete, you will import the setups back.
See FSM’s Configuration Package capability
for instructions.
To retain custom BI objects, export them from
the target environment before the environment
refresh. After the refresh is complete, you will
import them back.
See the BI archive/unarchive facility for
instructions.
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
Turn off all OTBI-E loads during the period
scheduled for the environment refresh.
Run the OTBI-E full load process after the
environment refresh is complete.
Allow the OTBI-E incremental load to handle
subsequent changes.
20
 Object Notes

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.

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
E-mail 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 e-mail 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.
Setup any custom ESS Jobs required for this pod’s use
ESS Job Definitions aren’t copied to the target environment. You should setup any custom jobs required
for this environment.
Setup 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.
21
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.
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, View).
Load deployment-only (nonproduction) users
Refer to the Import Worker Users Process (FSM) and User-Account Creation via auto provisioning rules
in Security Console.
Use the REST API for managing users (Create, Update, Delete, View).
Grant proper roles to deployment-only users
Refer to the Import Worker Users Process (FSM) and User-Account Creation via auto provisioning rules
in Security Console.

22
Grant additional roles to users that were in production
Refer to the Import Worker Users Process (FSM) and User-Account Creation via auto provisioning rules
in Security Console.
Use the REST API for managing users (Create, Update, Delete, 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
Address Wallet Migration
During a P2T environment refresh, the address wallet stored in OPSS is not migrated.
Important! Do not run any payment batches in nonproduction until you’ve migrated the address wallet. If
you do run payment batches, you’ll accidently send payment files to the bank’s production server.
To migrate the address wallet:
 Update payments transmission configuration to point to bank's nonproduction server, or
 Use "Payments Wallet Migration Post P2T / T2T Refresh (Doc ID 2407678.1)" migrate the wallet
from production to nonproduction.
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.
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.
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.

23
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.
To move Learning content from the source to the target environment after your Environment Refresh,
follow the instructions in MOS Note 2290763.1 (Fusion Learning Management: Content Unavailable
after P2T OR T2T).

24
Follow us at:

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

Copyright © 2020, 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.
0319

Oracle Cloud Applications Oracle Corporation, World Worldwide Inquiries

April 2020 Headquarters Phone:
500 Oracle Parkway +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200