Steps that will help you succeed with your first cloud implementation

1. Lessons Learned for an ERP Cloud Implementation
March 3rd, 2017
Prabal Saha

2. Presentation title
[To edit, click View > Slide Master > Slide Master]
Member firms and DTTL: Insert appropriate copyright
[To edit, click View > Slide Master > Slide Master]
2
DRAFT
Few key considerations
The success levers
Reporting – Financial &
Operational
• Paradigm shift in Financial
Reporting using FRS and
FSG
Security - Roles & data
access
PaaS – Tuning
• Identified roadblocks in custom
development on JCS-SX
• Use accelerators
• Avoid common pitfalls in
programming
Infrastructure & Instance
Enablement
• Configuration of PaaS and
SaaS products in the right
domain
• Plan in advance of two to
four weeks for cloning,
backups and patching
• Identify a good success
manager
Be aware of ERP Upgrade
Cycles
• De-risk the impact of ERP
release upgrades on your
implementation
Data Migration– Master and
Transactional
• Identify the FBDI
templates
• Generate sample data
sets and share with client
for approval
• Always use standard roles
(duties and privileges)
• In case custom roles are
required, it is very important
to develop a matrix of custom
roles with Oracle’s duties and
privileges

3. Presentation title
[To edit, click View > Slide Master > Slide Master]
Member firms and DTTL: Insert appropriate copyright
[To edit, click View > Slide Master > Slide Master]
3
DRAFT
Infrastructure provisioning and management have become more important than ever for a
successful implementation.
Infrastructure and Instance Enablement
Typical
Challenges
faced by client
Infrastructure sizing
and validation
1 Cloning, patching
and backup cycles
2
Correct grouping
of PaaS and
SaaS products3
 Always rely on Oracle’s recommended
sizes (e.g., BOM) for any further
recommendation. Oracle uses volume
maps and integration complexity to
determine the size of PaaS and SaaS
 Oracle expects instance cloning,
patching or upgrades to be planned 4-
6 weeks in advance. It is very
important to factor these timelines for
mock conversions, gold configs and
cutover activities.
 Before the development kicks-off make
sure that the instance is properly
aligned – Oracle ERP, JCS-SX (or
equivalent) and DBCS should be in one
instance

4. Presentation title
[To edit, click View > Slide Master > Slide Master]
Member firms and DTTL: Insert appropriate copyright
[To edit, click View > Slide Master > Slide Master]
4
DRAFT
Managing ERP Upgrades and Release cycles
Oracle releases multiple upgrades throughout the year and major releases once a year. It is
very likely that conflict can happen with the ongoing activities.
Mar,17
ProjectKickoff
Design/Build
TestCycle1
TestCycle2
UserAcceptance
Go-Live
02 03 04 05 06
MajorRelease
01
 Major release upgrades (e.g., R10 to R11) can conflict with implementation timelines and
therefore it is very important to carefully consider Oracle’s release updates schedules.
 In the event of such a conflict, ensure that you have alteast two cycles of testing available to test
conversions, validate upgrades and new features etc.
 If conversions have followed a template prior to upgrade, it is very important to compare the
templates of new version with previous version to access the impact of data structuring and
requirements.

5. Presentation title
[To edit, click View > Slide Master > Slide Master]
Member firms and DTTL: Insert appropriate copyright
[To edit, click View > Slide Master > Slide Master]
5
DRAFT
Data Conversion – Master the templates
Data conversion is a key exercise for any ERP implementation and for cloud, Oracle has
provided various templates to make this activity simpler.
Choosing the
right tool for the
right job
Oracle provides various templates such as FBDI, ADFdi , Rapid Implementation etc.
− Use Rapid Implementation spreadsheets for creating COA, Legal entities and BU
− Oracle File Based Data Import (FBDI) is used when there is a need for high volume data uploads
to Oracle ERP Cloud Service. It can be both legacy data migration as well as daily or regular
import of data.
Supplier
Conversion
Customer
Conversion
Invoice
Conversion
Work with Oracle to increase the sizing of the ERP Cloud DB to improve Supplier Conversion
performance.
- Additionally, perform load testing for entire supplier load well in advance to determine a practical cut
over time.
Customer should be loaded before suppliers and employees to avoid corruption of data.
- Profile option to be updated before customer upload through spreadsheet to prevent auto
numbering/update of account numbers.
- Time zone profile options to be enabled for the geographic locations where users might load
customers to prevent failures when using ADF DI.
FBDI for Auto invoice has certain limitation with respect to Tax.
- If business requires to use FBDI for creating transaction they need to provide calculated tax value in
the template.
- System does not auto calculate tax if tax code is passed in the FBDI template for transaction
creation. This is a bug on which oracle promises to work on their next release
Some conversion callouts

6. Presentation title
[To edit, click View > Slide Master > Slide Master]
Member firms and DTTL: Insert appropriate copyright
[To edit, click View > Slide Master > Slide Master]
6
DRAFT
Reporting
Financial Reporting
Studio provides board
room quality financial
statements and
departmental reports,
which can be viewed
in the user’s preferred
format – HTML, PDF,
or MS Office.
1
OTBI for
Financials
provides the
ability to build
custom queries
on transactional
data, and the
output can be
downloaded to
Microsoft Excel.
2
BI Publisher (BIP)
delivers out-of-the-
box reports, which
can handle high
transaction volumes.
Can be configured to
extract the data in
Rich Text Format,
Adobe PDF, Microsoft
Excel or XML.
4
Smart View is an
Excel plug-in that
allows your financial
users to perform ad
hoc multi-
dimensional
analysis on general
ledger balances.
3
External, management, and local reporting requirements
Decide which reporting tools would be appropriate for varied reporting needs.

7. Presentation title
[To edit, click View > Slide Master > Slide Master]
Member firms and DTTL: Insert appropriate copyright
[To edit, click View > Slide Master > Slide Master]
7
DRAFT
PaaS – A Critical bridge
• Make sure that the
right JCS-SX
configuration is
available for every
SaaS POD
• Raise SR with Oracle
to understand whether
the latest patch sets
are available
1
• Nothing beats
the right coding
standards and
leading practices.
• Avoid heavy
lifting in PaaS, as
much as
possible.
3 Since JCS-SX
works with
HTTPs/SFTP,
make sure the
right security
certificates are
installed.
2
Use Deloitte
Accelerators
for PaaS to
expedite the
development4
The PaaS (JCS-SX) is one of the building blocks of any Oracle Cloud ERP
implementation. This layer provides entry point for additional data validation,
bolt-on solution etc.

8. Presentation title
[To edit, click View > Slide Master > Slide Master]
Member firms and DTTL: Insert appropriate copyright
[To edit, click View > Slide Master > Slide Master]
8
DRAFT
Planning Security – Roles and Data Access
Security plays a pivotal role in ensuring the right access is provided to
enterprise data which is tied to right roles through Oracle Identity Governance
• ERP Cloud create Data specific roles when Operating Unit
(Business Unit in ERP Cloud) is created
• These roles provide segregation of duties
• Not recommended to customize these type of roles
• Create role definition in Oracle Identity Manager
• Plan for duties and privileges (seeded) based on business
need
• Assign those to the custom role through Authorization
Policy Manager * (R11).
Define roles – Key to architecting the right access
• Job Role – e.g., Procurement Manager
• Data Role – e.g., Procurement Manager- Americas or Canada
• Duty Role – e.g., PO Creation
• Abstract Role – e.g., Customer specific roles - Employee
1
Identify
Roles
Custom
Role
Planning
3
2
Plan the
role
structure