This document discusses whether a company should implement Oracle Fusion applications. It outlines that Fusion was introduced by Oracle to consolidate their various acquired ERP systems onto a unified platform. It describes the various Fusion products and components. It also discusses the challenges of moving to Fusion, including ensuring technical readiness, data quality, staff skills, and properly planning and executing the implementation as a complex project. The presentation aims to help companies understand what is required to transition to Fusion and determine if they are prepared to do so.

1. REMINDER
Check in on the
COLLABORATE mobile app
Should Your Company Implement
Fusion?
Prepared by:
Mike Lynott
Customer Solutions Architect
eprentise
Session ID#: 14525

2. eprentise Can… …So Our Customers Can:
Consolidate Multiple EBS Instances
Change Underlying Structures and
Configurations
 Chart of Accounts, Other
Flexfields
 Inventory Organizations
 Operating Groups, Legal Entities,
Ledgers
 Calendars
 Costing Methods
Resolve Duplicates, Change
Sequences, IDs
Separate Data
: Transformation Software for E-Business Suite
Reduce Operating Costs and Increase
Efficiencies
 Shared Services
 Data Centers
Adapt to Change
 Align with New Business Initiatives
 Mergers, Acquisitions, Divestitures
 Pattern-Based Strategies
• Make ERP an Adaptive
Technology
Avoid a Reimplementation
Reduce Complexity and Control Risk
Improve Business Continuity, Service
Quality and Compliance
Establish Data Quality Standards and a
Single Source of Truth
Company Overview: Incorporated 2007  Helene Abrams, CEO

3. Learning Objectives
Objective 1: Understand the basic concepts of Oracle Fusion’s
strategy and products.
Objective 2: Discuss the impact Fusion will have on your
current ERP environment.
Objective 3: List what options are available if your organization
does not implement Fusion immediately.

4. Agenda
■ Introduction
■ Fusion Products
■ Path to Fusion
■ Data Issues
■ Organization Readiness
■ Project Challenges
■ Roadmap
■ Conclusion
■ Questions

5. Should You Implement Fusion?

6. Where Do You Stand On This Question?

7. Why Did Oracle Introduce Fusion?
■ Oracle offers E- Business Suite (EBS) applications, as
well as the applications offered by companies which it
has acquired
▪ Includes: PeopleSoft, JD Edwards, Hyperion, and Siebel
Systems, among others
■ Due to the company’s numerous acquisitions, customers
feared that their ERP investments were in jeopardy
■ In response to these concerns, Oracle introduced Oracle
Applications Unlimited in 2006
▪ Gesture was a promise to customers that it would continue to
develop and support the applications it had acquired
■ In an effort to consolidate their product-development
efforts over all of their ERP systems and related
applications, Fusion Middleware was born

8. Fusion Middleware Component Groups
Exalogic
(software & hardware)
Oracle Data
Integration
Business Process
Integration (BPM)
Business
Intelligence
Cloud Application
Foundation
(e.g., WebLogic)
Service-Oriented-
Architecture Tools
(SOA)
WebCenterDevelopment Tools

9. Fusion
Middleware
Component
Groups
Image by Oracle®
Enterprise
Manager
Web
Center
Business
Intelligence
Grid
Infrastructure
Identity
Management
SOA
Weblogic Server

10. Fusion Products
Example: Finance
For customers migrating to Oracle Fusion:
■ Oracle Fusion Financials
▪ Oracle Fusion Middleware
— Oracle WebLogic
— Oracle SOA
▪ Oracle Essbase multidimensional database
▪ Oracle Hyperion Reporting

11. Fusion Products
Example: Finance, cont.
For customers staying on standard Oracle Financials:
■ Oracle Fusion Accounting Hub
▪ Input from Oracle General Ledger, PeopleSoft General Ledger
▪ Optional integration with other ledgers
■ Oracle Financial Reports Center
▪ Essbase
▪ Hyperion Reporting

12. Fusion Products
Example: Finance, cont.
For Oracle Fusion Financials customers with specific needs:
■ Fusion Advanced Collections
■ Fusion Automated Invoice Processing
■ Fusion Expenses
■ Fusion Transactional Business Intelligence for Financials

13. Now, What About The Product?
■ Purpose is not to give you “inside” information on product
issues or scare you off
■ Instead, purpose is to get you to consider:
▪ Do I need the features it provides?
▪ Do I understand what it will take…now?
▪ Do I want to take steps now, to make the eventual
implementation more straightforward…later?

14. The Path to Fusion
Licenses
Prerequisites
Technology
Readiness
Org
Readiness
Implement

15. Licenses
■ Like-for-like licenses: Oracle has eased the transition to
Fusion with these license arrangements.
▪ If you only need limited licenses for the Oracle Fusion
Middleware products

16. Prerequisites
■ Each Fusion product may require an environment in which
other Oracle products operate, for example:
▪ OID: Oracle Identity
▪ ODI: Oracle Data Integration
■ These other products come in two kinds of licenses:
▪ Use restricted to the Oracle Application with which they were
purchased
▪ Unlimited Use

17. For Further Details
■ Pick any example from the 19-
page document: Applications
Licensing Table, e.g.:
■ Business Intelligence Foundation
Suite for Oracle Applications is
eligible for use with the following
eight Oracle Business Intelligence
Applications provided Oracle
Fusion Applications is the only
data source:
▪ Financial Analytics, Fusion
Edition (+ 7 more)

18. Other Technology Issues
OS
Hardware
Capabilities
Operating
System
(and Version)
Network
Capabilities
Oracle DB
Version

19. Oracle DB Versions
■ You may need to bring your
existing instances up to a more
recent version
▪ Which may require migrating to a
new OS version
▪ Which may or may not be certified
for your existing server hardware
■ Latest version of Fusion Products are not certified on all prior
versions of Oracle DB
■ For example, Golden Gate 12c release operates only on
specific releases Oracle DB versions 11 and 12

20. Data Issues
“It’s the data, Mike; it’s ALWAYS the data.” Cliff Longman,
Adaptable Data
■ Number of Instances
■ Chart of Accounts
■ Master Data
■ Transaction Data
■ Hierarchies
■ Traceability

21. Multiple Instances
Do you have the optimal number of instances? (One is the
optimal number.)
■ If so, congratulations
■ If not, might it be time to move to the optimal number?

22. Chart of Accounts
■ Does your current Chart of Accounts serve the business well?
■ Or, are there issues with it that are a challenge now, and will
continue to be an issue under Fusion?
■ Do all instances use identical charts of accounts?

23. Master Data
■ The excuses are legion:
▪ Mergers
▪ Acquisitions
▪ Divestiture
■ Is there a single, unique, unchangeable ID number for each
part? Each facility? Each organization?
■ What will it take to get to that condition?

24. Transaction Data
What are the chances of collisions that will prevent transactions
being merged for Data Warehouse or Reporting Database?
■ How are your transactions identified?
▪ Do you need to used the GUID identifier?
■ Do you have a multi-time zone business?
▪ How are your transactions dated?
▪ How are your transactions timed?
▪ How are these values used / interpreted?

25. Hierarchies
■ Do HR’s hierarchy, finance’s hierarchy, and sales’ hierarchy
all match? Oracle Fusion won’t solve that issue!
■ How will you get from this point to a single, agreed hierarchy
for use in Oracle Fusion?

26. Traceability
Where did this data come from?
■ Master data: duplicate or mismatched values
■ Translated master data means the data can only be traced
from source to, for example, data hub; it can’t be traced back
■ Transaction data: what source system(s) provided this data?
How can you confirm?
Can the data be trusted?

27. Is Your Organization Ready?

28. Ready
Staff Skills
Identity and UAM
Cloud
XML
Mobile devices
Project Discipline
System-to-System
Integrations
Developers
Issue Management
Issue Development
Issue Tracking

29. Staff Skills
■ Identity and User Access Management
■ Cloud
■ XML
■ Mobile devices

30. Staff Skills: ID and UAM
■ Large user population:
▪ Can you programmatically assign a role to most of your users
using available system-accessible data?
▪ Do you have a large number of contractors / consultants? Are
they managed well within your system?

31. Project Discipline
■ Are all your system-to-system integrations developed under
official projects?
■ Or…do you have developers (or business users) who
regularly develop what they want in the back room?

32. Data Quality
■ Buying Oracle’s Data Quality tool won’t “fix” your data quality
issues.
■ Do you have a strong data quality program in place? If not,
Oracle Fusion will only make those issues more visible more
quickly.

33. Issue Management
■ Issue development
▪ Oracle Fusion adds layer upon layer to your current software
▪ Hence the issues that arise can be very complex
▪ Do you have the facilities and staff to simplify and replicate
complex issues? (And are they the same staff you need to do
development?)
■ Issue tracking
▪ Once you’ve clarified the issue(s), do you have a support
coordinator who can prioritize and track these complex issues
with your vendor(s)? Or is it a committee of 27?

34. To Recap
To be prepared to adopt Fusion products, an enterprise must:
 Have a compatible software/hardware infrastructure
 Have a high level of data quality
 Have a well-managed IT organization
 Be prepared for the rigors of a complex implementation
 Be prepared for the ongoing operation of a complex
environment

35. Do You Still Think You’re Ready?

36. Project Challenge
“You’ll have to lay a lot of track before you can run a single
train!” (Author unknown)
■ A project that prepares you for Fusion is not a project with
obvious, visible benefits for the business people.
▪ Fit these tasks into ongoing support for operations?
▪ Search for benefits to help satisfy the folks who ask about
Return-On-Investment.

37. Plan for Decommissioning
■ The worst possible outcome for a migration to Oracle Fusion
Financials is to have your legacy environment continue to
operate alongside your Oracle Fusion Financials
environment.
■ Plan your implementation to include a plan for
decommissioning.

38. Staffing
Few people with these skills are readily available at low wages
(or consulting rates):
■ Data Modeling
■ Data Warehousing
■ XML
■ Cloud

39. Roadmap
Migrate to Oracle Fusion
Add Server
Capacity
Review
Data Quality
Issues &
Respond
Upgrade
OS Where
Needed
Upgrade
DB Where
Needed
Prepare
Development,
Test & Production
Environments
Install Oracle
Fusion Apps &
Underlying
Infrastructure

40. Project Implementation Steps
1. Determine which of the Fusion Applications you will want to
utilize
2. May need to purchase other technologies aside from your
desired applications in order to take advantage of Fusion
3. Decide if you want to implement Fusion on-premise or in the
cloud (or some combination of the two)
4. Determine what resources and infrastructure are necessary
5. Begin implementing with a phased approach, one application
at a time

41. Conclusion
■ You can still use non-Fusion applications in your current
environment
■ You can use non-Fusion applications with Fusion components
added on
■ You can migrate to Fusion

42. Questions? Comments?

43. THANK YOU
Mike Lynott
mlynott@eprentise.com
eprentise
www.eprentise.com
Accelerating the time for change in
Oracle E-Business Suite
Visit eprentise at booth 1033!
43

44. Please complete the session
evaluation
We appreciate your feedback and insight
You may complete the session evaluation either
on paper or online via the mobile app