Welcome to the Webinar!

On the Way to EBS R12.2:

How to Avoid the Pitfalls

Webinar dial-in number: +1 (609) 318-0024

Access Code 723-370-593
Audio PIN will show after joining the webinar

1
We will begin shortly

Todays Speakers

Amir Farhi
Oracle Product Marketing

Panaya
Your Moderator

Rachel Clark

Ayelet Glauberman
Panaya

Project Manager

Webinar dial-in number: +1 (609) 318-0024

Access Code 723-370-593
Audio PIN will show after joining the webinar

Housekeeping

Your line will be muted during the webinar

Submit questions via the Questions Panel

We will use polls during the webinar

We will address them at the end and after the webinar.

Webinar dial-in number: +1 (609) 318-0024

Access Code 723-370-593
Audio PIN will show after joining the webinar

Panaya at a Glance

Leader in Oracle EBS & SAP SaaS-based Testing and Impact Analysis
Automation software

Serving customers in 60+ countries

1,000+ enterprise customers, 2,000+ successful ERP projects

3,000+ ERP systems analyzed

Webinar dial-in number: +1 (609) 318-0024
Access Code 723-370-593
Audio PIN will show after joining the webinar

Panaya on Oracle.com

http://www.oracle.com/us/products/applications/ebusiness/ebs-upgrade/index.html#cost

Webinar dial-in number: +1 (609) 318-0024

Access Code 723-370-593
Audio PIN will show after joining the webinar

Agenda

Whats new in R12.2

Upgrade to 12.1.3 or 12.2.2?
Getting ready to upgrade
Case Study: Synaptics R12 upgrade

Webinar dial-in number: +1 (609) 318-0024

Access Code 723-370-593
Audio PIN will show after joining the webinar

E-Business Suite Support Timelines

We are here
7

Whats New in R12.2

Infrastructure Enhancements
Thousands of Functional Enhancements
Simplified User Flows
Online Patching

Infrastructure Enhancements
12.1 Technology Stack:

12.2 Technology Stack:

Functional Enhancements
ERP

Enhanced Labor Costing with

Projects & Payroll
Project Cost Breakdown Structure
Contract Lifecycle Mgt for Public
Sector (CLM): Electronic Contract
File, Concurrent Modifications, more
Channel Revenue Mgt: Simplified
HTML Flows

SCM

Order Mgt: Selling Subscriptions

Order Mgt / WMS: Advanced Catch Weight
WMS: Mobile Personalizations
MES: Electronic Kanban (E-Kanban)
MES: Express Transact for Serialized Mfg

ALM & Service

Project Accounting for Service Operations

Service: Simplified HTML Flows
EAM: Safety Management: Lockout Tagout

10

EBS R12.1.3+: Functional Highlights

Financials

Mobile Expenses application

Financials: Integration with Fusion Accounting Hub,
Integration with Hyperion DRM, Global Updates
Lease & Finance Mgt: Customer Driven
Enhancements
Property Mgr: New APIs and Extensions

Procurement

Legal Entity Derivation and Intercompany Billing

Improved Usability and Performance of Workplan

Human Capital Management

SCM: Contingent Worker Support

WMS: Mobile Personalizations
VCP: Asset Intensive Planning, Unified Planning and
Analytics, Rapid Simulation

e
l
b
a
l
i
a
v
a
o
!
s
2
l
.
A
2
1
R
in

Customer Driven Enhancements: AME for PO

Approvals
Supplier Lifecycle Mgt (SLM): Parallel Approvals,
Mandatory Internal Reqmts, Enhanced Registration
UI

Projects

Supply Chain Management

Asset Lifecycle Mgt & Service

EAM: Customer Driven Enhancements

Service: Simplified HTML flows
Depot : Supplier Warranty, Waste Mgt, Outsourcing

Master Data Management

Product Hub: APIs, Enhanced Rules, Telco features

Site Hub: Spatial Support; Google Map API update

Applications Technology

OAF Certification for iOS

Simplified SS HR Manager Flows

What-If Paycheck Modeling

11

Example: Fusion Mobile Expenses for

EBS
Now Available for iOS on 12.1.3+

12

Online Patches: From Downtime to Cutover

Critical business operations will not be interrupted

by maintenance operations
Revenue generating activities stay online
Business users stay online
Downtime required by any patch is predictable

Measured in minutes, not days or hours

Global single instances remain operational 24x7

Maintenance window easier to allocate as shorter time

required

13

Dual File System

14

Downtime Limited to Short Cutover

Users are logged off the production Instance

When users reconnect they are directed to the newly patched
system

Production

Patched Production
E-Business Suite
12.2.2

E-Business Suite
12.2.2

Patches
- 12.2.2
- 12.2.3
-

15

Online Patching Cycle

Prepare
Copy the
production
application
code
Create a new
Patch Edition
in the
database

Apply
Apply one or
more patches to
the Patch
Edition

Users
Online

Finalize
Compile invalid
Objects
Wait for a good
downtime
window

Cutover
Restart
application on
Patch Edition

Users
Offline

Cleanup
Remove
obsolete
objects

Users
Online

Application is only offline during the Cutover phase

Online Patching is used to apply all patches in 12.2
ADOP (AD Online Patching) orchestrates the patching cycle

16

Logical view of the Application Data

Model
EBS data model now has a cover layer
-

A logical rather than physical representation is presented

Editioning views provide this cover layer
Editioning views project different views of a table to the Run
and Patch Edition if the data model of a table is patched

All code must access EBS data via this cover layer!

Accessing the data model via the physical layer may result in
obsolete data been returned

17

Logical view of the Data Model

E-Business Code

Apps

APPLSYS

Custom Code

3rd Party Code

WF_ITEMS
(Synonym)

WF_ITEMS#
(Editioning view)

WF_ITEMS
(Table)

All code must access the data model via the APPS synonym!

APPS synonym points to the Editioning View (Logical Model)

Any code accessing the physical model risks accessing obsolete columns

18

Database Editioning Views

Patch & Run Editions see a different projection of the table
Run Edition View
Desc FND_TABLE
Name
Type

Desc FND_TABLE (Editioning View)

Name

Type

ID

NUMBER

ID

NUMBER

NAME

VARCHAR2(30)

NAME

VARCHAR2(30)

DESCRIPTION

VARCHAR2(30)

DESCRIPTION

VARCHAR2(30)

DESCRIPTION#1

VARCHAR2(80)

Patch Edition View

Code in the Run edition will treat
description as 30 characters
Code in the Patch edition will use the
new expanded 80 characters

Desc FND_TABLE (Editioning View)

Name

Type

ID

NUMBER

NAME

VARCHAR2(30)

DESCRIPTION

VARCHAR2(80)

19

EBS 12.1 and 12.2 Roadmap

20

Which version should you to upgrade

to?
Choose 12.2.2 if you:
-

Need the high availability provided by Online Patching

Want the functional enhancements that are in 12.2
Prefer to invest in a single project to upgrade directly to 12.2

Choose 12.1.3 if you:

Prefer to target a release with thousands of live customers

Upgrading from a release prior to 11.5.10.2

Would like to stay on 12.1 for 3-5 years before upgrading to

12.2

21

Getting Ready to Upgrade

For R12.2: Review Oracles On-Line Patching Readiness reports

Summary Readiness Report (ADZDPSUM.sql)

Manual Readiness Report (ADZDPMAN.sql)
Database check report (ADZDDBCC.sql)
File System check report (gscc.pl)

For R12.x: Subscribe to Panayas Upgrade Automation

Impact Analysis
Custom Code Corrections
Tailored Test Plan

22

Upgrade Automation
Panayas Software-as-a-Service simulation technology:
Maps customizations & system usage
Identifies what will break
Shows how to fix the code
Lists what needs to be tested

23

Cutting Upgrade Time, Cost & Risk

Traditional
Mapping
Customizations

More Cycles
Initial
Testing

Fix

Unit
Testing - CRP1

Integration
Testing - CRP2

User Acceptance
Testing - UAT

Go-Live

Panaya
Initial
Testing
Mapping
Customizations
& Usage

Go-Live
Fix

Unit
Testing

Integration
Testing

User
Acceptance
Testing

Savings of up to 70%

24

Case Study: EBS R12 Upgrade at Synaptics

Rachel Clark

25

About

Leading developer of human interface solutions

Over one billion devices contain Synaptics technology
Close to 400 patents issued or pending
750+ employees located in a global network of sales
offices and design centers
Headquartered in San Jose, California

26

Synaptics Oracle EBS 11i Environment

One global EBS production instance

Modules:

Financials
Human Resources
Business Intelligence
Procurement
Supply Chain
Sales and Demand Planning

27

The Challenge

Upgrade from EBS 11.5.10 to R12.1.3 on time and

within project budget

Identify impacted customizations before requesting

bids from system integrators in order to retain full
control over project costs and scope

28

The Solution

Signed up for a trial with Panaya

Within 48 hours we received:

A listing of all customizations and usage

Person-Hour estimates for each code correction task
Detailed steps, code snippets and even Oracle Support
references to complete each task

Purchased a Panaya subscription

Partnered with a System Integrator (SI)

29

Oracle EBS R12 Upgrade Project

Step 1: Identify Project Scope and Select System Integrator

Identified in-scope code corrections based on object usage and priority

Included Panaya analysis in the RFP document sent out to system
integrators
System Integrators submitted accurate quotes and timelines based on
project scope (# of customizations and enhancements) and estimate of
hours required
Screenshots from RFP document

30

Oracle EBS R12 Upgrade

Step 2: Pre-Upgrade Code Corrections

Panaya identified code corrections that could be made in 11i before the project began.
Gave these code corrections to support team to fix in record time
This exercise gave our IT team time to become familiar with the Panaya tool before the
project started

Example of a code correction task in Panaya

31

Oracle EBS R12 Upgrade

Step 3: Code Corrections

Panaya took care of the Discovery, Analysis and Design phases of impacted objects,
significantly reducing the time & effort that would normally be allocated to this
portion of the project

Synaptics team was able to focus on the business valuable activities

Enhancements

Discovery

Analysis

Design

Code
Corrections

Discovery

Analysis

Design

Development

Development

Project Phases for Enhancements and Code Corrections

32

Code corrections

33

Unit Testing
492 tasks covering 572 transactions

34

Oracle EBS R12 Upgrade

Step 4: Testing

Panaya analysis on test instances demonstrated that all code was corrected

Panayas analysis on test instances demonstrated that all code was corrected,
therefore test plan focused on key enhancements and end-to-end functional
processes with much less emphasis on testing corrected programs and reports.

Unit testing progress was tracked in Panaya

IT Functional Testing took place before each round of user testing
Users participated in three rounds of functional testing before the project went
live (CRP1, CRP2, UAT)

Test Phases for Enhancements and Code Corrections

35

Oracle EBS R12 Upgrade

Step 5: Reporting and Monitoring

Panaya provided full visibility over the project throughout the duration which let us
manage time and resources efficiently

36

Reporting & Monitoring

Panaya showing all custom objects & their usage

37

Reporting & Monitoring

(contd)

Automated project tracking

38

Reporting & Monitoring

(contd)

Summary of tasks by type

39

Reporting & Monitoring

(contd)

Detailed reports can be exported to Excel

40

The Result

Project went live on time and under budget using a fixed bid
contract
42% cost savings compared to similar projects
Team was able to focus resources on delivering valuable
enhancements and business process improvements instead of on a
routine technical upgrade

99% of customizations worked as expected upon going live

41

Advice

Analyze your system using Panaya before beginning the

project

Run a Panaya analysis early and often to get an accurate

estimate of the number of customizations and their usage

(best to start a month or two before project begins)

Continue running Panaya analyses throughout development
and testing phases to help auto-close development tasks
and to report and assign new tasks based on usage changes
Shorten the code freeze period by allowing project scope
flexibility with your partner SI

42

Thank You!
View the full webcast here:
http://panaya.com/webinars-category.html

43