Learn how and why to upgrade to R12.2.5

1. CUSTOMER
FOCUS
COMMITMENT
QUALITY
Click to edit Master title style
CUSTOMER
FOCUS
COMMITMENT
QUALITY
Oracle EBS Upgrade to 12.2.5

2. Why upgrade to 12.2.5
2
Protects Investment
in e-Business suite
Enables Modern
User experience
Extends the value
of e-Business Suite
Dramatic downtime
reduction
with online patching
Keeps Technology
up-to date
Automated Testing
Centralized Monitoring
Enables Hybrid
Cloud Strategy
In-memory enables
145 x Faster
performance

3. R12.2.x Upgrade Value Proposition
4
Business Value
 New features and
functionality
 New Modules
 New Requirements
 Smart Phone Applications
 Operational Efficiency
 Opportunity to re-engineer
business processes
 High System Availability
IT Reasons
 Supportability
 Improved Performance
 Reduce Maintenance cost
 Retire Customization
 New Features
 Better Technology
Techstack
 Reduce maintenance
downtime - adop

4. 12.2.5 Modern User Experience
5
Smartphone
Applications
Modern user experience
Tablet friendly UI
Reduced need of custom
reporting

5. Improved Operational Efficiency
6
Centralized System
monitoring
145 x faster
performance with
commodity hardware
Dramatic
maintenance
reduction
(Online Patching)

6. Support Schedule
7
EBS 12.1.X will be de-
supported in 2016, this
means in order to keep the
support active, a large
number of organizations
have to upgrade the EBS to
12.2.X in a short amount of
time

7. Cloud vs upgrade what’s right path ?
8

8. EBS 12.2.x Financials enhancements
9
ORACLE E-
BUSINESS TAX
ORACLE
PAYMENTS
ORACLE
PAYABLES
SUBLEDGER
ACCOUNTING
ORACLE ASSETS
 Customer Tax
Information Import
 New Condition
Set Operator for
Tax Rules
 Payment
Acknowledgem
ent Import
 No
enhancements
 Enhanced Multi-
Reporting
Currency
Functionality
 Improved
Reporting and
Analysis with
Supporting
References
 Enh. Mass Additions
I/F for Legacy
Conversions
 Automated Depr.
Rollback for Selected
Assets

9. 10
EBS 12.2.x Order Management enhancements
 OM integration with Oracle Approvals Management (AME)
 Tax Calculation on Freight Charges
 Credit Tolerance for Honoring Manually Released Credit
Checks Holds
 Support for Service as Promotional Goods
 Scheduling Enhancements
 Credit Card Authorization Reversal
 Support for Assemble-To-Order (ATO) Items in Pick-To-
Order (PTO)
 Models and Kits
 Order Information Portal (OIP) Enhancements
 Support for Credit Hold Based on Bill To Customer
 Selling Services Enhancements
 User Defined Attributes (UDA)
 Support for Advanced Catch Weight
 Additional Business Events
 Order Management Productivity Enhancements

10. EBS 12.2.x Sales Contracts new enhancements
11
ORACLE SALES CONTRACTS
• Repository Contracts Enhancements
• UDA support for Deliverables
• MS Word 2010 Certification
ORACLE ADVANCED PRICING
• Service Item Support in Promotional Modifiers
• Support of Non-Continuous Price Breaks
ORACLE SHIPPING
• Integration to 3PLs or 3rd Party Distributed Warehouse
Management System

11. More12.2.x new functional features
12
There are hundreds of new features in 12.2 that organizations can leverage to further automate their business
processes. If any of these features is important to your business, then strongly consider a 12.2 release target. See the
12.1 and 12.2 Release Content Documents (RCDs) for details of the new 12.2 features, which are as :
ERP SCM ALM & Services
Enhanced Labor Costing with
Projects and Payroll
Project Cost Breakdown Structure
Contract Lifecycle Management
(CLM) for Public Sector: Electronic
Contract File, Concurrent
Modifications, and more
Channel Revenue Management:
Simplified HTML Flows
Order Management: Selling Subscriptions
Order Management / Warehouse Management:
Advanced Catch Weight
Warehouse Management: Mobile Personalization
Manufacturing Execution System: Electronic
Kanban (E-Kanban)
Manufacturing Execution System: Express
Transact for Serialized Manufacturing
Supply Chain Management: Contingent Worker
Support
Project Accounting for Service
Operations
Service: Simplified HTML Flows
Enterprise Access Management:
Safety Management: Lockout –
Tagout Oracle

12. Premier support ended in January in 2012
Extended support ended in January 2015
Longer EBS 12.1 Premier Support and Extended support timelines
Premier Support will end on December 31, 2016
Extended Support will end on December 31, 2019
Premier Support ended in September 2018
Extended Support ended in September 2021
Business Suite Support Timelines for All Versions
13
12.0
12.1
12.2

13. EBS 12.1 vs 12.2
14
EBS 12.2 EBS 12.2.X
Release 12.1 includes major architectural improvements to
the Financials products to support global and shared
service operations. It also includes significant
enhancements to other product areas, including
 Procurement,
 Supply Chain Management,
 Asset Lifecycle and Service,
 Human Capital Management,
providing increased opportunity for process improvement
and automation than was available in 11i.
The upgrade from 11i to 12.2 includes the Financials
architecture changes, and adds some 12.2-specific
technical changes. These include the move to Online
Patching, the uptake of Web Logic Server, the required
move to Oracle Database 11gR2, and the required switch
from Oracle Single Sign-On to Oracle Access Manager.

14. When should you choose release 12.2:
• Wish to invest time and resources in a single project to
upgrade directly to 12.2
• Need high availability provided by a new feature in
release 12.2 called “Online Patching”
• Need to implement new Functional features and
enhancements available in release 12.2
EBS 12.1 vs 12.2 Upgrade
15

15. • 12.2 comes with Web logic application server
• New versions of Java components. Forms and report s are re-engineered
• Significant changes in the middle tier stack, new skills needed
• List of co-existence opportunities > SOS suite and Web services, IDM, Web
center, OEM, OBIEE, Hyperion EPM, Endeca, HCM Cloud etc.
• Online patching reduces downtime dramatically
• Many Out of the box ADF Mobile Apps available ( iExpense, Time Entry and
Field Service etc. )
• However, online patching requires 2 stacks of the applications servers and it
adds complexity in the database
• You will need significant more horsepower on your ( temp) storage and
servers (memory) compared to 11i and 12.x
• CEMLI list should be up to date
• 12.2 comes with Web Logic and SOA suite. You can build your own Mobile
Apps and web services
• Simplified user Interface
• SSO Integration is simplified in 12.2
12.2 Pros & Cons
16

16. • There is a direct upgrade patch from EBS release 11.5.10.2
to EBS release 12.2.
 Customers on EBS release 11.5.10.2 must apply minimum baseline
patch requirements for Extended Support as per Metalink Note:
883202.1 before upgrading to EBS release 12.2
• There is no direct upgrade path to EBS release 12.2 from
earlier EBS 11i releases.
 Customers must first upgrade to 11.5.10.2 and apply baseline patch
requirements for Extended Support before they can upgrade to 12.2.
• There is a direct upgrade path from EBS release 12.0.4 and 12.0.6 to
EBS release 12.2
• Customers on earlier releases of EBS 12.0 will need to upgrade to
EBS 12.0.4 or 12.0.6 level before starting EBS release 12.2 upgrade
• There is a direct upgrade path from EBS 12.1 (12.1.1, 12.1.2 and
12.1.3) to EBS release 12.2
Release 12.2 upgrade paths
17

17. • On the database tier , the technology stack includes:
Oracle Database 11g Release 2 (11.2.0.3)
EBS utilizes Edition -Based Redefinition (EBR) feature to enable EBS
online patching
• On the application tier, the technology stack includes:
 Oracle Fusion Middleware 11g PS3 (11.1.1.6.0)
 Oracle WebLogic Server 11g PS3
 Oracle WebLogic JSP compiler
 Oracle FMW 11g Java Required Files (JRF) libraries (except the use of
ADF and MDS 11g )
 Oracle WebLogic Portlet 11g PS3 Container
 JRockitor JDK 6.0
 Apache version 2.2
 Oracle 10g (10.1.2) Applications Server for Oracle EBS Forms
based Applications
EBS Release 12.2 Architecture
18

18. • Proven approach
• Usage of our knowledge base and
tools for accurate upgrade
assessment
• Couple of trial upgrades to ensure
detailed activity capture
• MOCK to ensure right estimates on
the production downtime & planning
Proven Upgrade Approach
19

19. Upgrade Strategy
20
Preparation
(Lay down 12c
and R12.2) –
no downtime
Apply Latest
CUP + other
performance
patches – no
downtime
Online Clone
database +
Upgrade to
12c
Upgrade
R12.2
Apply TXK +
AD and
Upgrade to
12.2.5
Apply Post
Upgrade
Patch
(conditionally
required)
Deploy
Customization
and external
Integration
Configure
system to
production
capacity
• Clone latest production to test instance
• Two trials to ensure progress & detailed activity tracking
• Mock iterations before prod upgrade

20. • Alignment of clients project roadmaps and align it
with Upgrade timelines
• Agreement on the test scripts for both SIT & UAT
before start of the project
• Segregation of issues on auxiliary systems impact
with upgrade
• We work closely with client team to ensure
upgrade is in alignment with other auxiliary
systems
Alignment with Client Global Roadmap
21

21. Current Env
• EBS – 11i.10.2 ( 11.5.10.2 ) - Single node and 6 apps nodes
• RDBMS – 11.2.0.3
• OS – OEL 5.1
• Localization – Brazil, Israel and Latin America
• Storage – Single Node RAC on 3-PAR SSD
• Auxiliary systems – Hyperion, AppsWorx, BPEL and SOA
Target Env
• EBS – 12.2.4 ( Single DB node and 6 apps nodes )
• RDBMS – 11.2.0.3
• OS – OEL 6.7
• Localization – Brazil, Israel and Latin America
• Storage – Single Node RAC Kamanario-K2
• Auxiliary systems – Hyperion, AppsWorx, BPEL and SOA
• Duration – 9 months
Our recent EBS 12.2.x Upgrades
22

22. Current Env
• EBS – 12.1.3 ( Single Node DB and Single Apps Node )
• RDBMS – 11.2.0.3
• OS – SunSolaris 10
• Storage – Single Node Instance
• Auxiliary systems – Agile, OTM and Discoverer
Target Env
• EBS – 12.2.5 ( Single Node DB and 3 Apps Node )
• RDBMS – 12.1.0.2
• OS – OEL 6.7
• Storage – Single Node RAC Kamanario-K2
• Auxiliary systems – Agile, GTM and OBIEE
• Duration – 1 year
12.2.5 Re-implementation
23

23.  Cloning issues with third party tools after 12c upgrade
 Online patching – adop issues
 Run and patch filesystem issue
 OAF/Java custom code issues
 Custom schema and PL/SQL code issues
 Auxiliary system issues due to EBR
 SSO integration issues
 Cloning issues and challenges
 Forms personalization issues
 Shared APPL top issues
 Custom top and custom code related challenges
 Issues with custom triggers due to EBR
Learning experience
24

24.  Agreement on SLAs for downtime of various environments
 Role matrix on approvals and issue resolution
 OS compatibility verification
 Backup & restore activities. Need to have dedicated support during planned
 activities and quick SLAs for any unplanned activities
 Need to start with PROD equivalent instance
 Agree on the number of environments
 Bound to get issues
 Need to involve critical account management and get buy-in
 Regular calls for SR issue resolution & support
Learning from past experience
25

25. Trinamix At a Glance
Development
Partner
US UAE
India
Japan
Ex-Oracle
Development
Industry
Experts
Cloud User
One of 3 certified SCM Cloud delivery partner globally
Australia

26. CUSTOMER
FOCUS
COMMITMENT
QUALITY
Click to edit Master title style 27
Spy
Glasses
Select Customers

27. CUSTOMER
FOCUS
COMMITMENT
QUALITY
Click to edit Master title style
Noticeable Case Studies
End to end management of merger of Synaptics USA +
RSP Japan (EBS Financials, Supply Chain, PLM, VCP)
End to end system management for Merger of
Panasonic Fabless Operations with Fujitsu
Semiconductors (Under the brand – Socionext)
End to end management of merger of Lattice
Semiconductors with Silicon Image Inc.
End to end Implementation of Oracle Applications –
Financials & Supply Chain

28. Why Trinamix
29
 We perform thorough analysis on client customization – CEMLI before upgrade
 We study customer master data volume and other technical information to accurately
estimate the migration efforts for 12.2.x upgrade
 Help clients identifying things they can plan ahead of 12.2.x upgrade to reduce
downtime
 We follow unique approach to reduce downtime in minimum iterations
 Help customers in identifying in-place upgrade Vs re-implementation
 Design client architecture for new 12.2.x tech stack
 Help client in moving traditional custom code based on de supported technology to new
technology e.g. mod pl sql is de supported in 12.x
 Help client with 11.5.10.x and earlier release to latest 12.2.5 upgrade best approach
 Perform db and apps upgrade in same downtime
 Help with OS, storage and network in same EBS upgrade window
 Implement best practices to avoid performance issues e.g. JVM tuning and proper
distribution of Web, CCM and other Apps components
 Help client with post go-live stabilization and cloning