Applies to:

Oracle Financials Cloud Service - Version 11.1.12.0.0

Oracle Project Portfolio Management Cloud Service - Version 11.1.12.0.0
Oracle Procurement Cloud Service Version 11.1.12.0.0
Oracle Revenue Management Cloud Service Version 11.1.12.0.0

Purpose
Review these resources to ensure a successful upgrade to Release 12.

Scope
Oracle ERP Cloud: Upgrade to Release 12

Details
Use these resources to prepare for, deploy, and validate the upgrade to Release 12:

1. Read the New Feature Summary and Whats New in Release 12 guide to see the details about what is new and changed in the release.
Additionally, be aware of any Common Technology changes for Release 12. These apply to all product families within Oracle Cloud
Applications, including ERP Cloud. There are both security and functional changes in Release 12, and you must ensure you allow sufficient
time to read the Upgrade Guide for Oracle ERP Cloud Security (Doc ID 2211555.1) and become familiar with these changes before your
upgrade.
o Communicate upcoming user experience changes and any minor changes or enhancements to your user base and schedule end
user training as needed.
o Evaluate which new features you would like to roll out, and make plans to implement new functionality after your upgrade is
complete. Where possible, Oracle allows you to control when the new feature is exposed to your end users. This allows you to
upgrade first, and then manage the introduction and use of new features at a pace that works for you.
 2. Check the pre- and post-upgrade steps listed below to help you plan any pre- or post-upgrade tasks you might need to perform for the
individual products you are using. Read the Known Issues for Release 12 to learn about any known issues that you should be aware of in
this release.
3. Watch the Release Training videos to see demos of the new features.

Pre-Upgrade Steps

You might need to perform some pre-upgrade tasks before your upgrade takes place. This table helps you determine if you need to do that, so
first review the changes described in Release 12 (left column). Then understand why you might want to perform the task (middle column); and if
you do, follow the step-by-step instructions to perform that task (right column).

Pre-Upgrade Preparation Does this apply to you? Follow these steps...

Complete all Scheduled Processes
All ERP ESS processes must not be running in
users your environment during the upgrade.
If you have long-running processes, or are Ensure that all ESS jobs are complete, and
due to schedule any processes, ensure that do not schedule any long-running
these will be completed before your processes prior to the upgrade.
upgrade begins.

Preserve Custom Reports

Financials As part of the upgrade, the BI Catalog
Users may be updated. Any custom reports you
only have created that are not stored in the
Custom folder will get overwritten as part
of this process.
If you have created your own Financial
Reports using FR Studio, you should make
sure these are not overwritten during the
upgrade.
Ensure that any FR Studio reports or
books are stored in the folder labeled
Shared Folders > Custom >
Financials.
Alternatively you may download
content to local storage and reload it
once the upgrade is complete, using
 Pre-Upgrade Preparation
Data Security Upgrade (Data Role Deprecation)
All ERP As part of this upgrade, the use of data
Users roles generated by data role templates to
drive data security will be discontinued.
User-to-role-data assignment records will
be created based on a users assignment
to these data roles, and these assignment
records can be reviewed and managed in
the Manage Data Access for Users
page.
Does this apply to you?
If you started using Oracle ERP Cloud prior
to Release 11, you may be impacted by this
upgrade.
On the other hand, if you started using
Oracle ERP Cloud in Release 11, you are
already using the new data security model,
and this upgrade step does not apply to
failure or error. The upgrade relies on
you.
Follow these steps...
the Archive / Unarchive feature.
You need to run the scheduled process
Retrieve Latest LDAP Changes prior
to the upgrade. This process copies
users and roles from LDAP to HCM
User Management. The process
requests from OIM any changes that
may not have arrived because of a
user and role assignments data in HCM
User Management so it is important to
ensure that data in HCM User
Management is up to date. The
Retrieve Latest LDAP Changes
process is granted to the predefined IT
Security Manager, Human Resource
Specialist and Human Capital
Management Application
Administrator roles.
You should run the User Role
Membership Report to have a record
of user and data role assignments prior
to upgrade.
 Pre-Upgrade Preparation
All ERP After the upgrade, data role templates
Users will no longer be accessible.
Upgrade-Safe Management of Factory Shipped Roles
All ERP In Release 12, predefined Oracle roles are
Users locked and you cannot customize the
Oracle delivered functional and data
security policies associated with these
roles.
Locking down these security artifacts
enables safe upgrades to pre-defined
Does this apply to you?
If you have created custom data role
templates previously, you should make a
note of all the custom data role templates
you may have created.
If you have customized any existing factory-
shipped roles, these will be reset during the
upgrade. To ensure these will be preserved,
you must copy and save them to a new
role.
Predefined Oracle roles will be locked and
cannot be customized from R12 onwards. If
Follow these steps...
You should query any custom data role
templates you may have created in the
Oracle Entitlement Server and
document all the details offline.
If you have already upgraded to Oracle
ERP Cloud Service Release 11, you can
start creating the custom data security
policies that are required in the
manual upgrade as described in Step 2
under the section What if I have
created custom data role templates?
in the Upgrade Guide for Oracle ERP
Cloud Security (Doc ID 2211555.1).
Run the Security Customizations Report to
identify if you have customized the
factory-shipped roles. Oracle predefined
roles will be reset during the upgrade, so
to ensure your changes will be preserved,
you must copy and save these to a new
role.
 Pre-Upgrade Preparation
roles, since the possibility of conflict with
customer introduced changes to these
roles is now eliminated. This in turn
enables customers to safely adopt new
enhancements that may be delivered
with pre-defined roles in future releases.
Does this apply to you?
you wish to create custom roles you can
make copies of pre-defined roles and freely
customize these copies.
Follow these steps...
As part of the pre-upgrade preparation,
Oracle will contact you directly to provide
help with preserving customizations to
existing factory-shipped roles.
If you are affected by this upgrade step
but have not been contacted directly,
please contact Oracle Support for
assistance.
Post-Upgrade Steps

You may need to perform post-upgrade tasks before deploying the release to your user community. This table helps you determine if you have
to do that, so first review the changes described in Release 12 (left column). Then understand why you might want to perform the task (middle
column); and if you do, follow the step-by-step instructions to quickly perform that task (right column).

Changes in Release 12 Does this apply to you? Follow these steps...

Data Security Upgrade (Data Role Deprecation)
All ERP Validate user-role-data assignments If you started using Oracle ERP Cloud
Users record Service prior to Release 11, you may be
impacted by this upgrade.
If you started using Oracle ERP Cloud
Service in Release 11, you are already
using the new data security model, and
this upgrade step does not apply to you.
Validate the user-role-data assignments
that the upgrade has created using the
Manage Data Access for Users task from
Setup and Maintenance.
You can validate the user-role-data
assignments created against the results
from the User Role Membership
Report you ran before your upgrade.

All ERP Plan your migration to the new data You should perform this step if you have Please follow the steps as described in the
Users security model if you have custom data created custom data role templates section What if I have created custom data
role templates. previously. role templates? in the Upgrade Guide for
Oracle ERP Cloud Security (Doc ID
2211555.1).

Validate User Lifecycle Settings

All ERP In Release 12, Oracle Fusion Applications After the upgrade to R12 is completed, Refer to the section Validate User Lifecycle
Users Security enables security administrators security administrators must review the Settings in the Upgrade Guide for Oracle
to manage the entire user lifecycle setup of user lifecycle management in the ERP Cloud Security (Doc ID 2211555.1).
through the Security Console. They can Security Console. The following activities
 Changes in Release 12
customize how notifications are
generated and sent for various user
lifecycle events, including user-account
creation and password
management. Administrators can also
tailor user-name and password
generation by choosing from a list of
shipped policies.
After the upgrade is completed, review
the setup of user lifecycle management
in the Security Console.
Validate Custom Reports
All ERP Restore custom reports.
users
All ERP Validate the content of any custom
users reports post-upgrade.
In particular, the OTBI subject areas for
Assets and General Ledger have been
redesigned in Release 12, so you should
verify these reports are working as
expected.
Compatible Versions of FR Studio, Smart View and ADFDi
Does this apply to you? Follow these steps...
must be undertaken:
1. Verify password expiration duration.
2. Verify password expiration warning
duration.
3. Verify password complexity rules.
4. Verify user-name generation rules.
5. Configure notification templates.
6. Configure forgot-password flow.
All of these activities must be performed in
the Security Console.
If you downloaded your custom content to Use the Archive / Unarchive facility to
a local directory, you should restore it restore any custom OTBI / BI Publisher
after the upgrade. content and FR Studio reports.
If you have created your own reporting or Once the upgrade has been completed you
analysis in OTBI, BI Publisher or FR Studio should conduct a thorough test of your
you should verify these after the upgrade upgraded environment as soon as possible.
as there may be new or changed data
affecting these reports. Give test users access to the upgraded
Test/Stage environment.
Run reports according to your test plan
and record the results.
 Changes in Release 12 Does this apply to you? Follow these steps...
All ERP You must use the latest version of Smart If you use Smart View for reporting and Uninstall previous versions and download
users View for this release. analysis, you should download the latest the latest version from Oracle Technology
version. Network. Smart View is backward
compatible, so you should always download
the latest version from OTN for the latest
updates.

Financials Your FR Studio version must match the If you use FR Studio to build new financial To ensure that these versions are the same,
Users server version for your release. reports, you should download the latest uninstall previous versions and download
only version. the newest version from Workspace after
your upgrade.

All ERP Your ADFDi version must match the If you use ADFDi to enter data via Uninstall previous versions and download
users server version for your release. spreadsheet upload, you should download the latest version of ADFDi from Navigator >
the latest version. Tools > Download Desktop Integration
Installer.
You will automatically be prompted if
there is a mismatch in versions when
opening an ADFDi spreadsheet.