A webcast presented by IT Convergence November 20 th, 2014

(1)

Answering the Million Dollar Question for Oracle E-Business Suite R12.2 Customization

A webcast presented by IT Convergence

(2)

(3)

Global Reach, Local Expertise

● San Francisco - Bay Area

● Chicago ● New York ● Dallas ● Incline Village ● Mexico DF ● San José ● Rio de Janeiro ● São Paulo ● Buenos Aires BRAZIL ARGENTINA COSTA RICA MEXICO UNITED STATES ●Shanghai ●Hyderabad INDIA CHINA

(4)

And we host our systems running Oracle VM

Used the

E-Business

Suite since 2004

Upgraded

to R12

in January 2009

Implemented

OBIEE

in January 2010

Oracle Fusion

Applications

in 2012

R12.2 Beta

Program

in January 2012

(5)

On the Phone



Host

Belen Diaz Colodrero

Marketing Campaigns Assistant,

IT Convergence



Presenters

Gustavo González

Chief Technology Officer,

IT Convergence / Oracle ACE Director

Stephen Bonica

Manager of Financial and HR Applications,

Harvard Pilgrim Health Care

Chuck Scheller

Director Business Systems,

Harvard Pilgrim Health Care

Marcelo Albajari

Development Services Strategic Consulting Director,

IT Convergence

Pablo Andres Stahlhamer

(6)

Free 60 minutes 12.2 assessment



Training



Online patching cycle, problems and

standards



Analysis and Recommendations



Analyzing customer system and

formulating remediation strategy

Email

(7)

Oracle E-Business Suite Support Timeline

New Technical Architecture and

Development Standards

Harvard Pilgrim preparation for Release 12.2

(8)

Oracle E-Business Suite Support Timelines

Updated Support Polices for 11.5, 12.0, 12.1& 12.2

2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022

12.0

Jan '12 Jan '15 Jan ‘07

PREMIER

EXTENDED

SUSTAINING

12.1

May ‘09 Dec‘16

PREMIER

EXTENDED

Dec’19

Extend 12.1 Premier Support thru Dec ‘16

12.2 11.5.10 Nov '10

EXTENDED

SUSTAINING

Nov '13 Dec ’15 EXEPTION

Offer Exception to Sustaining Support

PREMIER

Sep‘18 Sep‘13

EXTENDED

Sep’21 Today

(9)

Oracle E-Business Suite Support Timeline

New Technical Architecture and

Development Standards

Harvard Pilgrim preparation for Release 12.2

(10)

R12 Technology Stack

CLIENT

APPLICATION

DATABASE

HTT P/S

Weblogic Server

Weblogic JSP

BC4J

UIX 11g

BI Publisher

Forms

W

eb

List

er

ne

r

Global Single

Data model

RAC & ASM

Edition-based

redefinition

JDB C/SQL Ne t

(11)

SOA Suite Uptake



Technology Stack Upgrade: SOA Suite 11g and WLS 11g

E-Business Suite 12.2

E-Business Suite 12.1.3

Integrated SOA Gateway

WS

Framework

Adapter

Framework & EBS

Adapter Lib

WSIF

Oracle AS & 10g for E-Business Suite

Integrated SOA Gateway

SOA Suite

(12)

Technical Upgrade Process

Resource: CON7700_Bastidas-CON7700-Migrating-and-Managing-Customizations-For-Oracle-E-Business-Suite-R122

5. Enable Online

Patching

6. Upgrade to

12.2.x RUP

7. Deploy

Customizations

and External

Integrations

8. Configure

System to

Production

Capacity

1. Upgrade

Database

2. CEMLI

Remediation

3. Lay down R12.2

File System

4. Upgrade to

12.2.0

(13)

E-Business Suite R12.2 Online Patching

E-Business Suite

will remain

available to users

during patching

operations

Downtime

window will

be predictable and

in minutes

Patches are applied

while the

production

application remains

online

(14)

The Basics of Online Patching



Online Patching Cycle include 5 phases



Application is only offline during the “Cutover” phase



Online Patching is used to apply all patches in 12.2

Resource: Oracle E-Business Suite: Mobile Strategy and Roadmap [CON7492] Jeanne Lowell - VP, EBS Product Strategy, Oracle , OpenWorld 2014

Prepare

Copy the

production

application code

Apply

Apply one or

more patches to

the copy

Finalize

Ready the

system for

cutover

Cutover

Restart

application on

patched copy

Cleanup

Remove

obsolete objects

Users Online

Users Offline

Users Online

(15)

Online Patching Cycle - Abort



The Online Patching Cycle can be aborted at any time prior to cutover

Resource: http://www.oracle.com/technetwork/tutorials/onlinepatching-1686406.pdf

Prepare

Apply

Finalize

Cutover

Cleanup

(16)

E-Business Suite R12.2 Patching Cycle

Database Edition Patching Cycle



One or more database editions are always present



Run Edition



Used by the running application



Always exists



Patch Edition



Used by the patching tools



Only exists during a patching cycle



Old Editions



These editions are only used to store code

objects that have not been patched in a later

edition



Remove by cleanup when no longer needed

(17)

Customization Preparation Project

Analysis and Implementation



Based on the Catalog



Utilities available for the analysis



Online Patching Readiness Reports



Database



Online Patching Standards Compliance Report



Database



Application tiers



Available as standalone patches for 11i, 12.0, 12.1

and 12.2

Reference Note: 1531121.1

(18)

Online Patching Readiness Reports

Database



Very few violations require manual intervention if schema is registered with the application



Materialized View with a dependency on a PLSQL package or function



Constraints with a dependency on PLSQL code



Triggers defined on LONG columns



Readiness Report will tell you how to address them



Register your Custom schemas with the application

(19)

Online Patching Standards Compliance Report

Database



Custom code should comply with Online Patching Development Standards



Standards include



Data model access pattern



Code naming standards



Special Object definition requirements (VPDs, MVs)



Failure to address these violations could result in



Future Code invalidation



Inability to patch Custom Code online (Downtime required to maintain Custom Code)

(20)

Online Patching Standards Compliance Report

Database, Data Model Access Pattern



All code must access the data model via

the Logical View (APPS synonyms

(21)

Customizations in Oracle E-Business Suite R12.2

(22)

Editionable Objects



Views (ordinary, not materialized)



PL/SQL code



Synonyms



User Types



Virtual Private Database Policies

Non-Editionable Objects

E-Business Suite R12.2 Online Patching

New Development Standards



Tables



Temporary Tables



Indexes



Materialized Views



Sequences



Database links

(23)

Online Patching Readiness Reports

Database



Main purpose is to identify the Editioned Based Redefinition golden rule:

“

Non-Editioned objects cannot depend on Editioned Objects

”



Non-Editioned Objects



Tables



Indexes



Materialized Views



Sequences



Constrains

DATA STORAGE OBJETS



Editioned Objects



PLSQL



Specs



Body



Function



Procedure



Views



Editioning Views



Triggers



Types



Synonyms

CODE OBJETS

(24)

Online Patching Standards Compliance Report

Database, Code Naming Standards



Table Names cannot exceed 29 characters



Column Names cannot exceed 28 characters



Table Names cannot use the

“

#

”

character



Object Names must end in alphanumeric character



Index names must contain at least one

“

_

”

character



Constraint Names must contain at least one

“

_

”

character



Materialized Views Name cannot exceed 29 characters

(25)

Ways of customizing or extending your EBS

environment



New business rules or data transformations



New or custom screens



Integrations with external systems



Use of third-party utilities or extensions



Creation of new reports



Creation of new workflows



Integrations with standalone APEX applications

(26)

E-Business Suite 12.1 Instance Ready for 12.2 Upgrade

(27)

Managing Customizations in R12.2



Maintain customizations with Online Patching



New R12.2 Development and Deployment Process



New R12.2 Development Standards



Tools to help manage customizations

(28)

Maintain Customizations with Online Patching in R12.2



Customizations are deployed during the APPLY phase

(29)

Oracle E-Business Suite Support Timeline

New Technical Architecture and

Development Standards

Harvard Pilgrim preparation for Release 12.2

(30)

Harvard Pilgrim’s Challenges



Harvard Pilgrim was concerned about the changes in development standards

necessary due to the new 12.2.2 Online Patching feature



Harvard Pilgrim needed to train their developers and then modify their software

promotion process so all new code was compliant with Oracle’s “coding”

standards before they promoted it to their production system



Harvard Pilgrim required help to understand the violations reported by Oracle’s

tools (Readiness Reports) and to define a strategy for solving those issues

(31)

ITC’s Solution



A training plan that addressed approximately 85 developers within Harvard Pilgrim’s IT teams



Onsite and remote trainings, covering coding concepts including exercises



A devoted consultant that worked with Harvard Pilgrim for 3 months



Assisted their development teams incorporate the new concepts and apply them to new

code developed



Evaluated the violations in their current code to the standards as reported by Oracle

Readiness Reports



Planned the mitigation activities with them to remediate offending code



Facilitated the introduction of a "gate" into their software promotion process in order to