Oracle Applications Cloud Environment Refresh

8/17/2019 Oracle Applications Cloud Environment Refresh

1/16

MARCH 2016

Oracle Applications Cloud

Environment RefreshService Entitlement Definition

Oracle Fusion Applications


2/16

Contents

Contents

Overview ...................................................................................................................... 3

Why Refresh Your Nonproduction Environments? ....................................................... 3

About the Environment Refresh Service ...................................................................... 4

Fulfillment Considerations ............................................................................................ 5

How to Request an Environment Refresh .................................................................... 9

How to Validate Service Fulfillment ............................................................................ 12

Frequently Asked Questions ...................................................................................... 13

Related Information on My Oracle Support ................................................................ 13

Appendix A: What Gets Copied During Environment Refresh ................................... 14


3/16

3

Overview

An environment refresh migrates data from a source environment, usually production, to a target

environment, usually nonproduction, making a copy of the source environment. Environment refreshesensure a predictable experience during testing activities by providing a comparable nonproduction

environment for testing and validation, before applying changes to your production environment.

There are two refresh services 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 fromone nonproduction environment to another.

Environment refreshes don’t support migrating data from a nonproduction environment to a designatedproduction environment.

This document describes how to prepare for and request your environment refresh.

Appendix A lists what does and does not get copied during an environment refresh.Important! Do not request this service if you are using the delivered integration between Fusion andTaleo Recruiting. Instead, request an environment refresh using the Taleo Zone Refresh with FusionHCM Environment Refresh service.

See more details in the Cloud Service Requests and Fulfillment for Oracle HCM Cloud Service article,available on My Oracle Support (Doc ID 2004494.1)

Why Refresh Your Nonproduction Environments?

Environment refreshes address several business objectives during your implementation lifecycle andongoing use of the Oracle Applications Cloud Service. They provide a one-to-one, or a copy of an

environment, to support the following scenarios:

Update your nonproduction environment with your real production data to support ongoingextension and configuration changes, testing, and maintenance work.

Refresh your nonproduction environment to reflect your production environment before applyingan upgrade to your nonproduction environment so you can test before cutting over to the newrelease in your production environment.

Refresh a nonproduction environment whenever you need to reestablish a new baseline for suchpurposes as initiating a new project and replacing test data that is no longer useable.

If you have multiple nonproduction environments, copy content from one nonproductionenvironment used for development purposes to another used for testing.

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2004494.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2004494.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2004494.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2004494.1


4/16

4

About the Environment Refresh Service

Request an environment refresh using either the online self-service scheduling feature or the ServiceRequest (SR) user interface in My Oracle Support (MOS). If you need to request a coordinated Fusion-Taleo refresh, or require data masking as part of your refresh request, log a Service Request (SR).

Without Data Masking Service (Release 9 and Above)

Cloud Service Type ERP, SCM, HCM, and Sales

Typical Frequency Based on business need

Fulfillment Method Self-service Scheduling Tool or the MOS SR User Interface

When to Submit SRSubmit your SR 3-12 weeks before the date you need changes applied.Submitting an SR before or after this submittal window will result in yourenvironment refresh request being canceled and rescheduled.

Maximum Downtime

for TargetNonproductionEnvironment

48 hours

With Data Masking Service (Release 10 and Above)

Be sure you understand limitations with using masked data before you request the data maskingservice. Do not request the data masking service if:

You have not subscribed to the data masking service.

You want to replicate the same results as when using real, unmasked data.

Your test purpose is to verify interfaces to downstream systems that require real data that is notmodified.

Cloud Service Type HCM Only

Typical Frequency Based on business need

Fulfillment Method Scenario 1: You want the environment refresh and data maskingservice to occur as a combined activity. In this scenario, complete asingle SR for both. Data migrated to a test environment using anenvironment 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 thisscenario, you must submit two SRs: one to request the environmentrefresh service and one to request the data masking standaloneservice. If you need only data masking without an environment refresh,refer to Oracle Applications Cloud - Data Masking Standalone ServiceEntitlement on My Oracle Support(Doc ID 2092389.1.)

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=462161526435838&id=2092389.1&_adf.ctrl-state=qax3263uw_57https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=462161526435838&id=2092389.1&_adf.ctrl-state=qax3263uw_57https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=462161526435838&id=2092389.1&_adf.ctrl-state=qax3263uw_57https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=462161526435838&id=2092389.1&_adf.ctrl-state=qax3263uw_57


5/16

5

When to Submit SRSubmit your SR 3-12 weeks before the date you need your environmentrefresh. Submitting an SR before or after this submittal window will result inyour environment refresh request being canceled and rescheduled.

Maximum Downtimefor TargetNonproduction

Environment

72 hours

For more information about data masking, refer to Oracle Applications Cloud - Data MaskingStandalone Service Entitlement on My Oracle Support (Doc ID 2092389.1).

Fulfillment Considerations

Plan Ahead

Provide at least three weeks advance notice, (Six weeks if related with a release upgrade), oryou will be asked for a new date. This date must be 3 or more weeks from the date you filed youSR. 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.

Review the Schedule Maintenance calendar in MyServices

Choose an available date for your environment refresh

An environment refresh can’t be scheduled on the weekends when monthly updates occur.

For P2T, there is a blackout period between the 1st Thursday to the Sunday after the 3 rd

Friday of the month. If the 1st of a month falls on a Friday, the environment refresh can’tbe scheduled on the Thursday before the 1st Friday of the month.

If you are on concurrent maintenance, there is no blackout period.

For T2T, there is no blackout period.

Additional Considerations

Concurrent Maintenance

P2T when production is on nonproduction update cadence, there is no blackoutperiod, since both environments are updated at the same time.

P2T when nonproduction is on production update cadence, there is no blackoutperiod, since both environments are updated at the same time.

T2T when nonproduction environments are on different update cadence. Forexample, nonproduction 1 is on nonproduction cadence, and nonproduction 2 is onproduction cadence. The normal blackout period between the 1st Thursday to theSunday after the 3rd Friday of the month does apply, except when the 1st Friday ofthe month is the 1st of the month. If the 1st of the month falls on a Friday, theenvironment refresh can’t be scheduled on the Thursday before the 1st Friday of themonth.

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2092389.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2092389.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2092389.1https://cloud.oracle.com/sign-inhttps://cloud.oracle.com/sign-inhttps://cloud.oracle.com/sign-inhttps://cloud.oracle.com/sign-inhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2092389.1


6/16

6

For more information about concurrent maintenance, refer to Oracle Fusion ApplicationsCloud Concurrent Updates Option on My Oracle Support (Doc ID 1646394.1).

No Monthly Updates on Current Release: If you are no longer receiving monthly

updates for your current release, there is no blackout period.

Release Upgrade: Environment refresh is not available between different releaseversions.

Examples: The following examples show regular environment refresh blackout periods in twoconsecutive months. This calendar does not apply to any of the additional considerationspreviously mentioned:

September

Sun Mon Tue Wed Thu Fri Sat1 2 3

Blackout

Period

Monthly Update – nonproductionMiddle East only

4 Blackout

Period

Monthly update –nonproductionRest of World

5Blackout

Period

6 BlackoutPeriod

7 BlackoutPeriod

8 BlackoutPeriod

9 BlackoutPeriod

10 BlackoutPeriod

11BlackoutPeriod

12 BlackoutPeriod

13 BlackoutPeriod

14 BlackoutPeriod

15 BlackoutPeriod

16 BlackoutPeriod

17 BlackoutPeriod

Monthly update –

productionMiddle East only

18BlackoutPeriod

Monthly update –

productionRest of World

19 BlackoutPeriod

20 BlackoutPeriod

21 22 23 24 25 26

27 28 29 30

October

Sun Mon Tue Wed Thu Fri Sat1

BlackoutPeriod

Monthly Update – non production

Middle East only

2BlackoutPeriod

Monthly updatenonproductionRest of World

3BlackoutPeriod

4 BlackoutPeriod

5BlackoutPeriod

6BlackoutPeriod

7BlackoutPeriod

8BlackoutPeriod

9BlackoutPeriod

10BlackoutPeriod

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1


7/16

7

October

Sun Mon Tue Wed Thu Fri Sat11

BlackoutPeriod

12BlackoutPeriod

13BlackoutPeriod

14 BlackoutPeriod

15BlackoutPeriod

Monthly update – production

Middle East only

16BlackoutPeriod

Monthly update – productionRest of world

17BlackoutPeriod

18BlackoutPeriod

19 20 21 22 23 24

25 26 27 28 29 30 31

The two-week blackout period exists because your production and nonproductionenvironments won’t be at the same update level due to the mandatory monthly updates. For

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

Match Update Levels Between Source and Target Environments: The environment refreshprocess requires that your source and target environments must be at the same release, patch,and language packs.

If you purchased the Database Vault and Transparent Data Encryption (TDE) services, theymust be present and at the same update level in both environments or the environment refreshwill be canceled.

Even if your request is initially accepted, if the environments are not at the same update levelbefore the scheduled environment refresh, your request may be canceled.

If your environments are not at the same level, you have the option of one or more of thefollowing actions:

o Customer cancellation: You will need 1 week lead time for a cancellation.

o Customer rescheduling the environment refresh: You will need lead time to rescheduleThis will cause the 3 week lead time to restart, you will need to log a new SR.

o Wait until after the monthly update to schedule the environment refresh so that yourenvironments are back at the same update level.

Understand Exception Updates May Impact the Timing of Your Environment Refresh:Environment Refresh is not available if you requested an Exception Update on any one of yourenvironments. Oracle Support will explain the type of update you’ll receive and the timing forapplying it. If you are approved to receive exception updates during a month, applying them willput your environments out of sync and result in cancellation of the previously scheduledenvironment refresh. This means your environment refresh request cannot be fulfilled until bothenvironments are again at the same update level after the blackout period.

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1966109.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1966109.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1966109.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1966109.1


8/16

8

Obtain Required Preapproval: Submitting an environment refresh SR does not guarantee thatthe request can be fulfilled on the date requested. Comparison of update levels for source andtarget environments, as well as advance notice requirements, play a significant role indetermining whether the request can be fulfilled. Your request will be evaluated consideringthese factors and you’ll see the acceptance or rejection of your request within your SR.

Even if your request is initially accepted, if the environments are not at the same update levelbefore the scheduled environment refresh, your request may be canceled. Consider OtherFactors

Are you expecting an upgrade soon?

o If you require an environment refresh before your upgrade, schedule it to start 5 daysbefore your scheduled upgrade date. You must still avoid the blackout period.

o If you require an environment refresh after your upgrade, schedule iti to start 3 daysafter your scheduled upgrade date. You must still avoid the blackout period.

Have you subscribed to the data masking service, and are you requesting anenvironment refresh with data masking? If so, the environment refresh should start 6days before your scheduled upgrade date. You must still avoid the blackout period.

We recommend you submit an environment refresh request related to upgrades at least 6weeks in advance to consider all additional restrictions.

Are you on a release that is no longer updated and near the end of an upgradewindow? If the answer is yes, normal environment refresh blackout periods do not apply.Since previous release environments will not be updated during this time frame, they willremain in sync and can be refreshed outside of the blackout period. However, any exceptionupdates approved and applied will still put your environment refresh requests at risk.

Do you use data integrations, such as HCM Cloud Service data loading tool, to movedata between your Oracle Applications Cloud environment and your system ofrecord? If so, carefully coordinate the Oracle Applications Cloud environment refresh with

the other system’s content migration capability, such as for cloning or other refresh. If you donot synch these processes, data integrity issues may surface in the target environment. Toavoid this:

o Pair your integrated production environments together and your integratednonproduction environments together. Establish this pairing early in yourimplementation and do not change it, if possible.

o Do NOT run any integration processes between the two systems, once the firstcontent migration process has started, until the other system’s similar process hascompleted.

o Schedule your P2T 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.

o Review and change any setup or configuration in the target nonproductionenvironment that points to a production environment. Instead, point to the otherpaired nonproduction environment.

After both processes have completed, resume your integration processes.


9/16

9

How to Request an Environment Refresh

You can request environment refreshes using the online self-service scheduling feature. If you need torequest a coordinated Fusion-Taleo refresh, or require data masking as part of your refresh request, loga Service Request (SR).


10/16

10

To request an environment refresh using the Scheduling Tool:

The online self service scheduling feature is available for the environment refresh process. Follow thesesteps:

1. Sign in to My Services for the environment from which data will be refreshed. This is referred to asthe source environment.

2. Select Schedule Maintenance.

3. Follow the online instructions.

4. If you need further assistance, click Help about this page.

Once your request is submitted, a SR is created with Support. Work with Support using the SR as areference. You can track the status of the environment refresh approval through My Services.

Note: The self-service environment refresh feature in My Services simplifies the scheduling effort bypresenting you with a calendar that displays capacity for dates on which you can schedule both P2Tsand T2Ts. If any of the considerations listed below prevent you from scheduling your environmentrefresh via this self-service feature, you can always request it using the SR process described belowas Option 2.

The Service Administrator who submits the environment refresh request must have a MOSaccount for the Customer Support Identifier (CSI) assigned to the customer. If they do not,another Service Administrator should enter the request.

The self-service feature does not currently support the data masking option or the version ofan environment refresh which coordinates with Taleo Recruiting.

After submitting a self-service environment refresh request, you cannot change or delete it viaMyServices. Instead, you must update the SR previously generated in MOS.

The link displayed in MyServices for the environment refresh SR created by this process willdirect you to the standard MOS SR viewer. From the SR page you can click Switch to CloudSupport in the upper right hand corner, if you prefer that view. Note that this is a temporary

restriction.

SRs generated by the self-service environment refresh process will appear in My Company'sService Requests instead of My Service Requests. To view your environment refresh SR,search for it under My Company's Service Requests. Note that this is a temporary restriction.

To request an environment refresh using a Service Request (SR)

1. Sign in to My Oracle Support.

2. Select Create SR from the Services Requests section or tab.

3. Enter the following information:

Section Enter

What is the Problem? Copy from to

Where is the Problem? On the Cloud tab:

Service Type: the Oracle Applications Cloud Servicefor which you are requesting a P2T.

Environment: the target environment for your P2T

https://cloud.oracle.com/sign-inhttps://cloud.oracle.com/sign-inhttps://cloud.oracle.com/sign-inhttps://cloud.oracle.com/sign-in


11/16

11

Section Enter

request.

Problem Type: Hosting Services

Support Identifier: Your CSI number.

Click Next in the upper right hand corner to proceed

Guided Problem Definition The system will prompt you to answer a series ofquestions. Each question may be followed by a questionmark (?) that lets you view help text and a list ofassociated service entitlements from which to choose.

· Select the question that most closely reflects theissue you need addressed.

· Select the specific service entitlement you needfulfilled (e.g., Federated Single Sign On, LanguagePack).

· Answer subsequent questions to provide details

needed to fulfill the request.· Click Next to provide your contact details.

· Click Submit to complete your request.

4. Click Next and provide the following additional information.

Note: You must submit a new SR if you make any change to the source, target, or environmentrefresh desired date, as the request fulfillment process is based exclusively on theseparameters. This will cause the 3 week lead time to restart.

Section Enter

Confirm that you have read this document on My OracleSupport (Doc ID 1632261.1) and that you understand thedocumented policies and procedures contained in it.

Yes/No

Do you want data in the target environment to bemasked as part of the environment refresh?

NOTE: This option is available only to HCM Cloudcustomers on Release 10 or above with a paidsubscription to the data masking service.

Confirm that you have read and understand, HCM Cloud

Service Definition – Data Masking Standalone availableon My Oracle Support document, Doc ID 2092389.1.

Yes/No

Source and target Oracle applications environmentidentifiers

[Your environment names]

Desired P2T Completion Date The date you’d like to have content refreshed to thetarget/nonproduction environment. The targetenvironment will be down for up to 48 hours (without datamasking) or up to 72 hours (with data masking).

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1632261.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1632261.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1632261.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1632261.1


12/16

12

Section Enter

Have you reviewed scheduled ESS jobs to be terminatedduring the P2T process?

Yes/No/Uncertain

a. Name

b. b. E-mail,

c. Cell phone number

d. Office phone number

Technical contact information for the person OracleSupport should contact if there are any questions or

issues.

Additional Information Any additional information that will help clarify the timingand special considerations for this request.

Is this P2T Release Upgrade related? If so, provide the environment names and Oracle-proposed upgrade dates for your nonproduction andproduction environments. Your response to this questionis for additional information only. The upgrade schedulingprocess is handled separately and must be handled byfiling separate SRs. You should carefully plan andschedule these activities.

Note: If you have not heard from Oracle on the upgradedates, then do not file this as a Release Upgrade-relatedP2T.

What happens after you log an Environment Refresh SR?

Your environment refresh SR is used to schedule the environment refresh and will remain openuntil it has been completed. If you want to cancel a scheduled environment refresh, Oraclerequires a minimum of 7 days notice.

If any questions or issues need to be addressed after the environment refresh has completed,you must create a new SR.

We’ll also reach out to you to discuss options if environments are not in synch.

If we don’t have any questions about your request, the next communication step will be theOracle Service Outage Notification communication e-mail, which will be sent out just before yourenvironment refresh copy starts on your target environment. You’ll receive a notification fromOracle after your environment refresh completes and the target environment is available for use

How to Validate Service Fulfillment

1. Sign in to the target environment and verify that the Oracle data matches the data from thesource environment using a sample data set and setup.

2. If you have administrative access to Oracle Identity Management (OIM), sign in as that user and

verify that all OIM functions available to that user in the source environment are identical in thetarget environment.

3. You may want to run a report that your team has developed using OTBI or an equivalentbusiness intelligence tool.

4. If you requested data masking, query any person on the database through the user interface andverify that their email address is [email protected].


13/16

13

Frequently Asked Questions

How much time is needed to cancel the environment refresh?

At least 1 week advance notice is required to cancel an environment refresh.

How much advance notice do I need to give Oracle to schedule the environment refresh?

A minimum of 21 days advance notice is required. You can schedule the environment refresh upto 12 weeks in advance.

How long does an environment refresh take?

The target environment will be down for up to 48 hours (without data masking) or up to 72 hours(with data masking).

When is the blackout period?

For most months of the year, The blackout period starts on the 1st Thursday of the month andends on the Sunday following the 3rd Friday of the month. However, if the 1 st of the month fallson a Friday, the environment refresh can’t be scheduled on the Thursday before the 1st Friday

of the month.

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 bescheduled any time except on the weekends when monthly updates occur.

How do I schedule an environment refresh?

You can request environment refreshes using the online self-service scheduling feature. If youneed to request a coordinated Fusion-Taleo refresh, or require data masking as part of yourrefresh request, log an SR.

Related Information on My Oracle Support

Oracle Applications Cloud Concurrent Maintenance Option, Doc ID 1646394.1

Oracle Applications Cloud – Fusion Applications Update Policy, Doc ID 1966109.1

Cloud Service Requests and Fulfillment for Oracle HCM Cloud Service (Taleo Zone Refresh witFusion HCM Environment Refresh), Doc ID 2108681.1

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1966109.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1966109.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1966109.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2108681.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2108681.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2108681.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2108681.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1966109.1https://support.oracle.com/epmos/faces/DocumentDisplay?id=1646394.1


14/16

14

Appendix A: What Gets Copied During Environment Refresh?

The most important thing to understand is that almost all data is refreshed, but compiled binary objectsare not. There are some exceptions to this general rule and some possible implications for you.

What is copied?

All data in the Fusion schema, such as all transactional data and functional setup.

Webcenter content, such as file attachments and inbound and outbound integration files.

Key artifacts managed through Fusion Middleware Metadata Services (MDS), such as user

interface extensions managed as 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 Repository Definitions (RPDs).

Pre-compiled Fast Formula used by the HCM Cloud Service.

What is not copied?

Compiled objects, such as Fusion Applications binaries, Fusion Middleware binaries, and for

HCM Cloud Services customers, compiled Fast Formula.

Home page notifications, such as approval requests.

Data maintained in the Functional Setup Manager’s (FSM) Topology Manager , such as endpoint

URLs to other environments.

Enterprise Scheduler Service (ESS) process parameters.

Special cases

You may need to take steps before or after an environment refresh as a result of what is and what is notcopied.

Application Object Copied or Not? Possible Action

User interface extensionsmaintained in ADF sandboxes

Copied To retain in-process UI extensions, export them from thetarget environment before environment refresh andimport them back after. See Oracle Applications CloudExtensibility Guide for Functional Administrators.

Functional setup, includingHCM Fast Formula

Copied To retain some functional setup in the target, export itfrom the target environment before the environment

refresh and import it back after, using FSM’sConfiguration Package capability. See Oracle Applications Cloud Using Functional Setup Manager

Business Intelligencedefinitions

Copied To retain custom BI objects, export them from the targetenvironment before the environment refresh and importthem back after, using the BI archive/unarchive facility.

http://docs.oracle.com/cd/E51367_01/common_op/OAEXT/toc.htmhttp://docs.oracle.com/cd/E51367_01/common_op/OAEXT/toc.htmhttp://docs.oracle.com/cd/E51367_01/common_op/OAEXT/toc.htmhttp://docs.oracle.com/cd/E51367_01/common_op/OAEXT/toc.htmhttp://docs.oracle.com/cloud/latest/common/OAFSM/toc.htmhttp://docs.oracle.com/cloud/latest/common/OAFSM/toc.htmhttp://docs.oracle.com/cloud/latest/common/OAFSM/toc.htmhttp://docs.oracle.com/cloud/latest/common/OAFSM/toc.htmhttp://docs.oracle.com/cloud/latest/common/OAFSM/toc.htmhttp://docs.oracle.com/cloud/latest/common/OAFSM/toc.htmhttp://docs.oracle.com/cd/E51367_01/common_op/OAEXT/toc.htmhttp://docs.oracle.com/cd/E51367_01/common_op/OAEXT/toc.htm


15/16

15

Application Object Copied or Not? Possible Action

HCM Extract definitions Copied To retain custom HCM Extract definitions, export themfrom the target environment before the environmentrefresh and import them back after, using theexport/import function on the Manage HCM ExtractsDefinition user interface.

ESS process parameters Not Copied After the environment refresh, review the processparameters in the target for your key ESS processes.Reestablish scheduling and reset those defaultparameters (for example, the number of threads) youwant to change.

EssBase cubes Not Copied Create EssBase cubes in the target environment afterthe environment refresh, by submitting standard jobsthrough the Scheduler page.

For example, to create a Ledger EssBase cube:

1. Sign in to the Oracle Applications Cloud HomePage.

2. In the Navigator menu, select Tools >Scheduled Processes.

3. Select Schedule New Process.

4. In the Search window, scroll to the bottom of thelist and select Search.

5. Search for Create General Ledger BalancesCube. Select the item in the results set, thenclick OK, and then OK again

6. Enter the details of the Chart of Accounts:Name, Calendar and Starting Period, and thenclick Close.

Repeat this process for all Ledger cubes.


16/16

Follow us at:

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

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposesonly, 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 impliedwarranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liabilitywith 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 anypurpose, without our prior written permission.

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

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used underlicense 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. 0115

Oracle Applications Cloud Oracle Corporation, World Headquarters

500 Oracle ParkwayRedwood Shores, CA 94065, USA

Worldwide Inquiries

Phone: +1.650.506.7000Fax: +1.650.506.7200
http://blogs.oracle.com/oraclehttp://blogs.oracle.com/oraclehttps://www.facebook.com/Oraclehttps://www.facebook.com/Oraclehttps://twitter.com/oraclehttp://www.oracle.com/index.htmlhttp://www.oracle.com/index.htmlhttps://twitter.com/oraclehttps://www.facebook.com/Oraclehttp://blogs.oracle.com/oracle

Documents

Oracle Applications Cloud Environment Refresh