Applies to:

Oracle Financials Cloud Service - Version 11.13.17.05.0 (and onwards)

Oracle Project Portfolio Management Cloud Service - Version 11.13.17.5.0 (and onwards)
Oracle Procurement Cloud Service – Version 11.13.17.05.0 (and onwards)
Oracle Revenue Management Cloud Service – Version 11.13.17.05.0 (and onwards)

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

Scope
Oracle ERP Cloud: Upgrade to Release 13
1. R13 Upgrade Overview

This document provides a checklist for you to follow when planning your R13 upgrade.

Please review the entire document to understand all required steps in the R13 upgrade.

The upgrade process includes the following mandatory steps:

• Schedule your upgrade – if you have more than 1 stage environment, you need to develop an instance management plan and schedule the
upgrade of each your stage environments, as well as your production environment. You should consider any production to test refreshes you
require as part of your upgrade schedule and request those at least 3 weeks in advance.
• Uptake mandatory security, configuration and user experience changes – this document identifies all mandatory upgrade impacts. You should
review the list of product changes and define your plan to implement the listed changes, notify users of the changes and test the impacted
areas. Additionally, there are many new features in R13 that are optional and can be reviewed separately and implemented after your upgrade
has completed successfully.
• Test the upgrade – you should perform regression testing for all key flows in your implementation. Use this document to identify mandatory
product changes that may impact your test scripts and may require new tests to be created.

Upgrades are mandatory as described in Oracle Cloud Enterprise Hosting and Delivery Policy
2. 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 13 (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
2.1 Plan for your upgrade
All ERP Release 13 Upgrade scheduling,
Users confirmation, and rescheduling
activities will be performed by your
service administrators using My
Services.
As soon as your service administrator
receives an invitation to schedule
upgrades, dates must be selected
using My Services for each of your
environments. Environments that are
not scheduled within the invitation
period will be scheduled for you by
Oracle, and your service
administrators will be able to see the
scheduled dates in My Services.
Does this apply to you?
All ERP Cloud customers must plan for
their upgrade.
Follow these steps...
Read the Oracle Applications Cloud - Release Upgrade
Planning (Doc ID 2016981.1) to understand the Upgrade
Process and get ready to schedule/confirm/reschedule
upgrade of your environments.
Watch the Customer Connect webcasts Release 13
Progress Update and Scheduling Your R12 to R13
Upgrade (ERP, HCM, SCM, Sales and Engagement Cloud)
(Log in to Customer Connect first, then click links)
• Lay out a plan to upgrade all environments before end
of upgrades
• Include Environment Refresh as part of your plan, and
request in advance (at least 3 weeks in advance, must
be scheduled more than 5 days before or after an
upgrade)
• Review your Service Administrators and Notification
Contacts
• Login and schedule each environment
• Coordinate with other teams implementing or
managing other services
• All services on a Global Single Instance environment
will be upgraded at the same time
• Inform the user community about upgrade plans
• Go/No Go decision for Production environment
 Pre-Upgrade Preparation
2.2. Review and Enable Offerings
All ERP Offerings must be enabled before
Users moving to Release 13.
Does this apply to you?
The business processes your
organization or company performs or
supports determine the offerings and
functional areas you want to
implement.
Beginning with Release 13, the icons
available on the home page for your
users as well as their navigator
selections are controlled by the
offerings you've enabled.
If you haven't enabled offerings prior
to your Release 13 upgrade, the icons
and navigator won't reflect the correct
setup for your users.
There is no other impact on
functionality.
Follow these steps...
upgrade – before rescheduling deadline (at least 1
week before upgrade)
How to Check if Offerings are Enabled:
1. From the Applications home page or Navigation
menu, click Setup and Maintenance
2. On the Setup and Maintenance page, ensure Offerings
is set to All, then select an offering to enable and click
Configure
3. On the Configure page, select Enable for
Implementation
No additional setup is required. You can optionally
choose to enable related functional areas and features for
the offering to optimize the application for your
implementation.
4. To select specific features, click the Features icon for
the functional area, then select the check boxes to
enable the features you need and click Done.
For additional offerings, repeat from step 2.
For more information, see Enable Offerings for Oracle
Applications Cloud Release 13 Upgrade (Doc ID
2317112.1)
 Pre-Upgrade Preparation
2.3. Update existing bookmarks and web services for new URL hostnames
All ERP In earlier releases, each domain (e.g.,
Users HCM, Financials, CRM, Projects,
Procurement, SCM, Common, etc.)
had an external URL hostname.
In Release 13, this is changing to a
single external hostname.
Does this apply to you? Follow these steps...
Upon upgrade to Release 13, all Oracle Product family specific nodes like 'fs', 'crm', 'hcm' etc are
Cloud Applications should be accessed replaced by 'fa'
using the new consolidated URL.
See the naming pattern below:
If you have any integration flows that https://<systemName>.fa.<dcsn>.oraclecloud.com/...
call web services, the code must be
For example, if the system name is 'acme' based in data
updated in order to invoke web
center 6 then the consolidated URL would be:
services using the new endpoints. You https://acme.fa.us6.oraclecloud.com/...
may wish to begin updating your
integrations in advance of the For a few Release 12 customers with an existing URL
upgrade. pattern like:
https://fs-<systemName>.oracleoutsourcing.com/... then
If your users have bookmarked any the new pattern would be
applications pages, these bookmarks https://fa-<systemName>.oracleoutsourcing.com/...
must be updated to reflect the new
Note: After upgrade, your existing URL hostnames will
URL hostname after the upgrade.
continue to work for a short time, as redirect provisions
have been put in place to support your transition to
Release 13, but web services and bookmarked URLs must
be updated at the earliest opportunity to avoid loss of
service when the hostname redirect is desupported in the
future.
Users may notice that there are two parts of the URL that
have changed (1) the hostname - as described previously -
and (2) the context root e.g., https://fin-<systemname>-
oracleoutsourcing.com/ledger/… will become https://fa-
<systemname>-oracleoutsourcing.com/fscmUI/…
 Pre-Upgrade Preparation
Does this apply to you? Follow these steps...
Rewrite rules will map old context roots to the new
context roots, but Oracle recommends updating all
bookmarks to reflect the new context roots. They will
continue to work after your upgrade, but performance
will be less efficient than using the new URLs directly.

2.4. Preserve Organization-Specific and User-Defined Reports

Financials As part of the upgrade, the BI Catalog If you have created your own reports Ensure that any reports or books you have created are
Users may be updated. Any new reports you or modified any out-of-the-box Oracle stored in the folder labeled “Shared Folders > Custom >
only have created that are not stored in BI reports using FR Studio, BI Publisher Financials”.
the Custom folder will get overwritten or OTBI, you should make sure these
as part of this process. are not overwritten during the
upgrade.
o From Release 13 Update 18A, you
will no longer be allowed to edit or
customize out-of-the-box Oracle BI
content directly.
o All company-specific content must
be created as separate new
reports, and stored in the Custom
folder in order to be preserved
during upgrades and updates. You
may clone out-of-the-box reports
as a starting point, but cannot
modify these directly.
o If you directly modified any Oracle
BI content in earlier releases, you
 Pre-Upgrade Preparation
must place it in the Custom folder.
As part of the upgrade, out-of-the-
box Oracle BI reports will be
reinstated.
2.5. SSL Certificates Import for Check Printing on Remote Printer
Payments Starting from Release 13, Oracle will
Users no longer support any manually
Only imported certificates from Release 12
and prior releases. You are expected
to use only those certificates which
are supported by Fusion Truststore by
default.
Does this apply to you?
If you are using the Payments check
printing feature and have been
importing non-standard SSL
certificates for the Print server into the 2. Review the published list of certificates supported by
Fusion Truststore, you will not be able
to print checks on your printer after
your upgrade to Release 13.
You will need to perform a pre-
upgrade step to configure your print
server with a certificate supported by
Fusion Truststore.
Follow these steps...
1. Check if you have imported SSL certificates in Release
12 or prior releases for printing checks on a remote
printer.
Fusion Truststore.
3. Identify the certificate from the published list which
you will be using for printing checks over the internet.
4. Configure your print server with a certificate
supported by Fusion Truststore. Ensure that your
server presents the entire certificate chain during the
SSL handshake process.
More information is available on My Oracle Support: SSL
Certificates Import for Check Printing on Remote Printer
(Doc ID 2406398.1)
3. 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 13 (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 13 Does this apply to you? Follow these steps...

3.1. Supplier Contact Mobile Phone security (Data Security Upgrade)

All As part of this upgrade, a supplier
Procurement contact’s mobile phone information is
and Supplier secured under new data security
Users policy. To view or manage the mobile
phone information, you must have
the View Trading Community Person
Mobile Phone Number or the
Manage Trading Community Person
Mobile Phone Number privilege as
appropriate.
If any user accesses a supplier contact’s 1. Identify the user-defined job roles that give
mobile phone information through a user- you access to the mobile phone information.
defined job role, you need to add the new 2. Add the data security privileges: View Trading
data security privileges to each user- Community Person Mobile Phone Number and
defined job roles to view or edit the mobile Manage Trading Community Person Mobile
phone information. Phone Number depending on your use case.

• The View privilege allows users to

view the mobile phone information
but does not allow them to edit it.
The Manage privilege allows users
to view as well as edit the mobile
phone information.

• The View and Manage data security

privileges have been added to
predefined Oracle roles that give
you access to a supplier contact’s
mobile phone information by
 Changes in Release 13
default as part of the upgrade.
• Users who do not have the new
data security privileges will no
longer be able to access a supplier
contact’s mobile phone
information.
3.2. Procurement Dashboard Replaced by Source to Settle Home Page
Procurement In Release 13, the Source to Settle
Users Home experience page provides
analytics based infolets, and hence
the Procurement Dashboard is
decommissioned. The Procurement
Dashboard link is removed from the
Navigator and Springboard as the
dashboard is no longer available.
3.3. Business Intelligence Content Added to the Purchasing Overview Page
Procurement In Release 13, the Purchasing
Users Overview page is decommissioned. It
is replaced by the Purchase Orders
Work Area Home Page and the
Purchase Agreements Work Area
Home Page.
Does this apply to you?
If you were using the ‘Buyer Productivity
Report’ on the procurement dashboard,
you can no longer access it from this
location. To continue to use this report,
access it from the BI application.
If you added Business Intelligence content
to the Purchasing Overview page in
previous releases and you want to make
this content available to your users in
Release 13, follow the steps to create an
infolet for this content.
Follow these steps...
• In BI application go to Catalog > Shared Folders
> Procurement > Sourcing > Transaction
Analysis Samples.
Find the 'Buyer Productivity Report' under
Dashboard. Add this report to the
Negotiations work area ‘Reports and Analytics’
pane. See the help topic: Reports and
Analytics Pane: Explained
• Grant your users the “View Custom Infolet”
security privilege. This will render a Custom
Infolets page that exists at the same level as
your springboard page.
• Using Page Composer, edit the Custom Infolets
page to create an infolet to render the BI
 Changes in Release 13
Does this apply to you? Follow these steps...
content you want to make available to your
users. Refer to the Creating and Managing
Infolets section of the Configuring And
Extending Applications Guide for more
information.

3.4. Review Data Security Updates for Project Portfolio Management

PPM Users Starting in Release 13, Project Role If you have implemented more than one
and Project Statuses are no longer set Project Unit with separate Project Roles or
enabled. Project Statuses then these should be
revisited as they are no longer set enabled.

Note: Project Roles and Project Status

names have always been unique but you
may need to consider adjusting them to
help users determine which are relevant to
their part of the enterprise.

PPM Users Project Execution –Project Manager You now have the ability to create your
Roles own roles for the Project Manager in
project execution. The following data
security policies have been introduced
which will be automatically added to the
seeded Project Manager role:
• Manage Project Work Plan Data
• Manage Project Work Plan
Baselines Data
• Assign Project Resource to Project
On the Security Console, the IT Security Manager
needs to create a new project manager role with
the appropriate functional and data security
policies. After this project manager role is set up,
the Project Application Administrator can go to the
Manage Project Roles page, create a new project
role, and then map it to the new project manager
role.
 Changes in Release 13 Does this apply to you? Follow these steps...
Data

Although no action is needed as a part of

the upgrade you may want to create new
roles that, for example, allow a secondary
Project Manager to edit but not baseline
the project.

Note: Enabling the Extended Access to

View Project Plans capability allows team
members of the project to access a read-
only version of the Project Plan.

Additionally, the pages for Project Roles -

previously split between Project Financial
and Project Execution - have been unified
to a single page.

3.5. Update Award Performance Data for Grants Management

Grants Grants Management – Update Award After upgrade, the financial amounts for To view this information, run the Update Award
Management Performance Data the award don't display on the Financial Performance Data process for the respective
users Overview page of the award. business unit, with the summarization method set
to Delete and Resummarize.

3.6. Mobile Application for PPM Cloud

PPM Mobile Project Costing – A new iPhone and If you already used the PPM Cloud Mobile 1. If you are using an iPhone or other iOS device:
Users Android app is created for this app with Release 12 or earlier, you must
 Changes in Release 13 Does this apply to you? Follow these steps...
release. install the new Oracle PPM Cloud Mobile a. Uninstall Oracle PPM Cloud R12 Legacy if
application on your iPhone or Android you were using Oracle PPM Cloud Mobile
device. You should install the new app after in earlier releases.
b. Install Oracle PPM Cloud Mobile by
your upgrade to R13.
searching for it in the Apple App Store. Do
not use or install Oracle PPM Cloud R12
Legacy.

If you are using Android:

a. Install Oracle PPM Cloud Mobile by

searching for it in the Google Play Store

2. Open the app and select the gear icon in the

bottom right corner of the app. Do not enter
the URL in the Host field that is first presented
to you after you have installed the app.

In the Host field on the Settings page, enter

the URL for the server instance you will be
using. Do not include https:// or http:// as a
prefix in the Host field. See the example
below for what should be entered in the
Settings page:
Changes in Release 13 Does this apply to you? Follow these steps...

Settings page
 Changes in Release 13
3.7. Update OTBI Reports That Use General Ledger Balances Real Time Subject Area
Financials Changes have been made to optimize
Users the use of chart of accounts
structures in Oracle Transactional
Business Intelligence reports. The
changes affect existing reports that
use the General Ledger Balances –
Real Time subject area.
Does this apply to you?
If you have OTBI reports that use the
General Ledger Balances – Real Time
subject area, your reports will not run
unless you complete a one-time post-
upgrade step.
Follow these steps...
3. If using the mobile time capture functionality
ensure that:
a. Employee and Contingent Worker job
roles have the Project Time Entry Mobile
Duty.
b. User using the mobile time card can enter
and submit time in the web application.
c. Time card layout for the mobile time card
user has at least these three columns:
Project Name, Task Name and Expenditure
Type.
1. Redeploy the chart of accounts structure
a. Navigate to the Manage Chart of Accounts
Structure setup task.
b. Click Deploy Flexfield.
c. Verify the deployment was successful by
checking the results in the Deployment
Status column.
2. Run the following processes from the Scheduled
Processes work area in the order listed:
a. Create Rules XML File for BI Extender
Automation: Run this process for all GL
balances cubes that you need in Oracle
Transactional Business Intelligence.
b. Import Oracle Fusion Data Extensions for
Transactional Business Intelligence
 Changes in Release 13
3.8. Update Custom Reports built on SOA / BPM Tables
All ERP Users In Release 13, the schema that hosts
the Business Process Management
data model has moved from a family
level schema to a single Applications
level schema.
As a result, customers who use BI
Publisher (BIP) to report on related
objects will need to modify their
custom reports in Release 13.
3.9. Validate Reports
All ERP Users Validate the content of any reports
post-upgrade.
Does this apply to you? Follow these steps...
If you You will receive a separate notification via email
from Oracle if you are impacted by this change.
(1) use Approvals and
Review Custom Reports Built on SOA / BPM Tables
(2) previously created custom BIP reports Will No Longer Function Post Fusion Rel13
on various SOA/BPM tables from earlier
Upgrade (Doc ID 2352639.1) for more information
releases, your reports will be referencing and step-by-step instructions to help you update
older schema(s). your reports.
You would have been granted approval
• The modifications cannot be done until after
from Oracle to build BIP reports on the
your upgrade is complete and the new schema
following impacted tables:
is available in your environment
• Allocate time to undertake this work and test
1. WFASSIGNEE
2. WFCOMMENTS the changes in your non-production
3. WFMESSAGEATTRIBUTE environment as soon as this environment is
4. WFTASK upgraded
5. WFTASKHISTORY • Set aside time to either migrate the reports to
production post-upgrade or implement the
Reports built on these tables will no longer same changes in production as a post upgrade
work, and you will need to update your step
reports for Release 13.
If you have created your own reporting or Once the upgrade has been completed you should
analysis in OTBI, BI Publisher or FR Studio conduct a thorough test of your upgraded
 Changes in Release 13
3.10. Compatible Versions of Financial Reporting Studio, Smart View and ADFDi
All ERP users You must use the latest version of
Smart View for this release.
Financials Your Financial Reporting Studio
Users only version must match the server
version for your release.
Does this apply to you?
you should verify these after the upgrade
as there may be new or changed data
affecting these reports.
If you use Smart View for reporting and
analysis, you should download the latest
version.
If you use Financial Reporting Studio to
create financial reports, you should
download the latest version.
Updates for Financial Reporting are
delivered continuously on a monthly basis.
This means that you need to regularly re-
install Financial Reporting Studio to receive
the latest version.
If you are on a standard quarterly update
cycle, you need to re-install financial
reporting on a quarterly basis. If you opt in
to monthly updates, you must re-install
Follow these steps...
environment as soon as possible.
• Give test users access to the upgraded
Test/Non-Production environment.
• Run reports according to your test plan and
record the results.
Uninstall previous versions and download the
latest version from Oracle Technology Network.
Smart View is backward compatible, so you should
always download the latest version from OTN for
the latest updates.
To ensure that these versions are the same,
uninstall previous versions and download the
newest version from Workspace after your
upgrade.
 Changes in Release 13
All ERP users Your ADFDi version must match the
server version for your release.
3.11. Review Optional New Features Available After Upgrade
All ERP Users We continue to add many new
features to Oracle Cloud Applications,
and for some features, you can take
advantage of new functionality at a
pace that suits you by “opting in” to
the feature when you’re ready. You
can opt in to a feature in two ways:
by using the New Features page, or
by using the Setup and Maintenance
work area.
The New Features page in Functional
Setup Manager highlights the new
features that have been introduced in
the latest release version to give
more visibility to what is new in
Oracle Cloud Applications.
Does this apply to you?
financial reporting on a monthly basis.
If you use ADFDi to enter data via
spreadsheet upload, you should download
the latest version.
You will automatically be prompted if
there is a mismatch in versions when
opening an ADFDi spreadsheet.
After your update, you can use the New
Features page to explore and learn about
what has been introduced in the last
update of your applications and decide
whether to opt in.
Oracle recommends that you validate the
successful upgrade of existing features
first, and then manage the introduction
and use of optional new features at a pace
that works for you.
Follow these steps...
Uninstall previous versions and download the
latest version of ADFDi from Navigator > Tools >
Download Desktop Integration Installer.
• Select Navigator > My Enterprise > New
Features to open the New Features page. You
need the ‘Review Applications Offering’
privilege.
• Select your enabled offering from the menu to
review the new functional areas and features
that became available in the latest revision of
the offering.
• For each new functional area or feature:
o Use Learn More to find additional help
topics.
o Check the Enabled column to view opt-in
status. An offering is marked as ‘Not
Enabled’ to indicate that the offering
hasn’t been enabled yet and therefore, its
features cannot be used until the offering
is enabled by opting in.
o Consult the Requires Setup column to
learn whether it requires setup and plan
Changes in Release 13 Does this apply to you? Follow these steps...
accordingly.

• If you decide to opt into any functional area or

feature, click the Opt In button. For a new
functional area, open the Opt In page. For a
new feature, open the Edit Features page.

Note: You need the ‘Configure Oracle Fusion

Applications Offering’ privilege to perform this
step.

• Select the Enable check box, or in case of

features with multiple choices, select the
applicable choices.
• When you are finished, click Done to return to
the New Features page.
4. Additional Resources

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

1. Read the Oracle Applications Cloud - Release Upgrade Planning (Doc ID 2016981.1) to understand the Upgrade Process and get ready to
schedule/confirm/reschedule upgrade of your environments.
2. Read the New Feature Summary and What’s New in Release 13 guide to see the details about what is new and changed in the release.
o Financials Release 13: New Feature Summary and What’s New Guide
o Project Portfolio Management Release 13: New Feature Summary and What’s New Guide
o Procurement Release 13: New Feature Summary and What’s New Guide
o Revenue Management Release 13: New Feature Summary and What’s New Guide

Additionally, be aware of any Common Technology changes for Release 13. These apply to all product families within Oracle Cloud Applications,
including ERP Cloud. There are changes to Functional Setup Manager in Release 13 that change how you opt in (or out) of features and how you
identify newly introduced features, so you must allow sufficient time to read the Oracle Common Technologies and User Experience R13 What’s
New 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. In Release 13, you can use the New Features page in
Functional Setup Manager to get a quick view of the newly introduced features and to decide whether to opt into any of them.
3. Use the sections in this document to help you plan any pre- or post-upgrade tasks for the individual products you are using. Read the Known Issues
and Update Documents (Doc ID 1597086.1) to learn about any known issues that you should be aware of in this release.
4. Watch the Release Training videos to see demos of the new features.
5. If you are implementing services other than ERP Cloud, review the additional resources related with those services:

• Oracle Applications Cloud: Performing Your Upgrade (Doc ID 2106785.1) (Pre/Post Upgrade Steps for customers implementing multiple
services)
• Watch for additional R13 webcasts found in the Customer Connect calendar