Preparing forr12-140703020001-phpapp02

10 Things You Can Do Today
to Prepare for Oracle
E-Business Suite 12.2
Nadia Bendjedou
Senior Director, Product Strategy, Oracle

Program Agenda
 Overview
 12.2 Overall E-Business Suite Readiness
 12.2 Online Patching Readiness
 Key Takeaways

Supported Upgrade Paths
[1]: Patch Requirements for Extended Support of Oracle E-Business Suite Release 11.5.10 [ID 883202.1]
11.5.10
11.5.9
12.2
12.0 &
12.1
11.5.10
CU2 [1]

12.2 Overall
EBS Readiness
1. Review the Functional Changes
2. Understand the Technical Architecture
Changes
3. Learn about WebLogic Server
4. Consider Upgrading your Technical
Architecture

#1 Review The Functional
Changes

Oracle E-Business Suite R12
Global Financial Architecture
Bank
Model
Tax
Engine
Inter
Company
Subledger Accounting (SLA)
Dr Cr
Ledger & Ledger Sets
ProjectsReceivablesInventory
Work in Process Purchasing Payables
Multi-Org
Access
Control
Major Initiatives:
1. Ledger and Ledger Sets
2. Multi-Org Access Control
3. Subledger Accounting
4. Tax Engine
5. Intercompany
6. Bank Model

#1 Review The Functional Changes
Functional Changes – Upgrading to Oracle E-Business Suite 12.2 11i 12.0 & 12.1
Understand the Release12 new accounting model 
Understand the upgrade impact on 11i setups and data
• R12 Upgrade Considerations by Product (Doc 889733.1)
• Accounting Setup Manager Pre-Update Diagnosis Report (Doc 961742.1)

Understand the Datamodel changes from 11i. Doc 1290886.1 
Evaluate the impact on your 11i customizations and consider native functionality
wherever possible.
• Upgrading your Customizations to Oracle E-Business Suite Release 12.1 (Doc
1435894.1)
• EBS File System Comparison Report (Doc 1446430.1)

Evaluate new 12.2 functionalities: Yard Mgt, Outsourced Mfg, In-Memory Costing,
Supply Chain Event Mgt, more. Doc 1302189.1
 
Review the functionalities and modules that have been replaced:
• DBI (Daily Business Intelligence), Oracle Balanced Scorecard, Oracle Financials and
Sales Analyzers etc…(Doc 1302189.1)  
NB: A migration plan exists for customers who have purchased these products in earlier releases. Contact your Account Manager for more information.

E-Business Suite Functional Highlights
Customer-Driven Features – New in 12.2
 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
 HCM
– Recruitment Candidate Profile
– Oracle Webcenter Content Integration
– Paycheck Modeling
 SCM
– Order Mgt: Selling Subscriptions
– Order Mgt / WMS: Advanced Catch Weight
– WMS: Mobile Personalization
– MES: Electronic Kanban (E-Kanban)
– MES: Express Transact for Serialized Mfg
– SCM: Contingent Worker Support
 ALM & Service
– Project Accounting for Service Operations
– Service: Simplified HTML Flows
– EAM: Safety Management: Lockout – Tagout

Oracle E-Business Suite Info Center
 Release Content Documents (RCDs)
 Release Value Propositions (RVPs)
 Online Training (TOI)
 Online Documentation
 MOS Doc:
– 12.1 806593.1
– 12.2 1581299.1
Available to Customers on oracle.com and My Oracle Support (MOS)

#2 Understand The
Technical Architecture
Changes

10gR2 | 11g
Oracle E-Business Suite 11i Architecture
Client
JDBC/SQLNet
HTTP/S
Application Database
RAC & ASM
Global Single
Data Model
Forms
BI Publisher
BC4J
WebListener
JSP
UIX
JServ
iAS 1.0.2.2.2
#2

10gR2 | 11g
Oracle E-Business Suite 12.0/12.1 Architecture
Client
JDBC/SQLNet
HTTP/S
RAC & ASM
Global Single
Data Model
Forms
BI Publisher
BC4J
WebListener
10g
JSP
UIX
OC4J
#2

Oracle E-Business Suite 12.2 Architecture
Client
JDBC/SQLNet
HTTP/S
R2
Edition-Based
Redefinition
WebLogic JSP
Forms
BI Publisher
BC4J
WebListener
UIX 11g
WebLogic Server
RAC & ASM
Global Single
Data Model
#2

Oracle E-Business Suite Architecture
Developer 10.1.2
COMMON_TOP
APPL_TOP
INST_TOP
Oracle HTTP Server (OHS)
WebLogic Server (WLS)
Fusion
Middleware 11g
Applications Tier – 12.2
Developer 10.1.2
COMMON_TOP
APPL_TOP
INST_TOP
AS 10.1.3.1
Applications Tier – 12.1
#2

Applications Tier
 Forms & Reports Services
– OracleAS 10.1.2.1 ORACLE_HOME
– Coming from 11i: Replaces the 8.0.6-based Oracle_Home provided by iAS 1.0.2.2
 HTML-based Apps
– FMW 11g ORACLE_HOME
– Coming from 11i: Replaces the 8.1.7-based Oracle_Home provided by iAS 1.0.2.2
– Coming from 12: Replaces the OracleAS 10.1.3-based ORACLE_HOME (OC4J)
used in Oracle E-Business Suite 12.0 and 12.1
 Oracle JDeveloper 10.1.2
Oracle E-Business Suite Architecture in 12.2
#2

#2 Understand the Technical Architecture Changes
 Oracle E-Business Suite 12.2 Technical Planning Guide,
First Edition: 1585857.1
 EBS 12.2 Product Information Center , 1581299.1
 12.2 Documentation Library
Resources

#3 Learn about WebLogic
Server

#3 Learn about WebLogic Server
Oracle E-Business Suite 12.1 Configuration
Context Files
Oracle Application
Manager
Autoconfig
Configuration Changes
Oracle Application Manager &
Autoconfig
Database Home SID name, Listener, dbPorts, etc
Oracle Application Server
Virtual Hosts, performance directives, log configuration, ports,
mod_perl, mod_wl_ohs, oacore, oafm, forms services, etc.
E-Business Suite
Concurrent Processing, Profile Options, Developer 10g, Product
Specific Settings



 SID name, Listener, dbPorts, etc
 Virtual Hosts, performance directives, log configuration, ports,
mod_perl, mod_wl_ohs, oacore, oafm, forms services, etc.
 Concurrent Processing, Profile Options, Developer 10g, Product
Specific Settings

Oracle E-Business Suite 12.2 Configuration
Configuration
Changes
Fusion
Middleware Control
WLS Administration
Console
Oracle Application
Manager
& Autoconfig
Database Home
 SID name, Listener,
dbPorts, etc
Oracle HTTP Server
 Performance directives, log
configuration, ports, mod_perl,
mod_wl_ohs, etc.
WebLogic Server
 oacore, oafm, forms and
forms-c4ws services
E-Business Suite
 Concurrent Processing,
Profile Options,
Developer 10g, Product
Specific Settings




 SID name, Listener,
dbPorts, etc
 Performance directives, log
configuration, ports, mod_perl,
mod_wl_ohs, etc.
 oacore, oafm, forms and
forms-c4ws services
 Concurrent Processing,
Profile Options,
Developer 10g, Product
Specific Settings

12.2 Configuration: Fusion Middleware Control
Administer
Oracle HTTP
Server

12.2 Configuration: Fusion Middleware Control -> Access to OAManager
Access to Oracle
Application Manager

12.2 Configuration: Fusion Middleware Control
Access to WLS
Admin Console

12.2 Configuration: Fusion Middleware Control -> WLS Admin Console
Administer
WLS
Domain
System Monitoring
Configure Deployments

#3 Learn about WebLogic Server 11gR2
You Are Already Familiar with WebLogic Server IF Using These
Technology Release 11i Release 12
Oracle Access Manager 10.1.4.3, 11.1.2 11.1.1.5, 11.1.2
Oracle Internet Directory 11.1.1.6 11.1.1.6
WebCenter 11.1.1.6
Portal 11.1.1.6 11.1.1.6
Discoverer 11.1.1.6 11.1.1.6
Business Intelligence (EE+) 11.1.1.5 11.1.1.6
Business Intelligence Applications 7.9.6.3 7.9.6.3
Oracle SOA Suite 11.1.1.6 11.1.1.6
Enterprise Manager
11gR1 (11.1.0.1.0),
12cR2(12.1.0.2.0)
11gR1 (11.1.0.1.0),
12cR2 (12.1.0.2.0)

#4 Consider Upgrading
your Technology
Infrastructure

#4 Consider Upgrading your Tech. Architecture
 Switch from Oracle SSO to Oracle Access Manager 11gR2
– Premier Support for Oracle SSO ended in December 2011
– 12.2 is certified only with Oracle Access Manager 11g
– OAM 11gR2 (11.1.2) is certified for 11i and 12.0/12.1.3
 Switch from Oracle Portal to Oracle WebCenter Portal
– 12.2 is certified only with Oracle WebCenter Portal
– Oracle WebCenter Portal 11gR2 (11.1.1.6) is certified for 12.0/12.1.3
External Services

#4 Consider Upgrading to Latest Technologies
 Upgrade to Oracle RDBMS 11gR2 (11.2.0.3)
– 12.2 has a prerequisite of Oracle Database 11gR2 11.2.0.3
– Database 11gR2 11.2.0.3 is certified for 11i and 12.0/12.1.3
 EBS 11i, 12.0 & 12.1 References
– Interoperability Notes EBS 11i with Database 11gR2 (11.2.0). Doc 881505.1
– Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2. Doc 1058763.1
– Database Preparation Guidelines for EBS Release 12.1.1 Upgrade. Doc 761570.1
Database tier

12.2 Online
Patching
Readiness
5. Understand the 12.2 Patching Cycle
6. Understand Edition Based Redefinition
7. Understand the Enablement Process for
Online Patching (OP)
8. Review Online Patching Standards
9. Plan for 12.2 Dual File System
10. Consider New Operational
Characteristics

#5 Understand the 12.2
Patching Cycle

#5 Understand the 12.2 Patching Cycle
 Online Patching cycle includes 5 phases
 Online Patching is used to apply all patches in 12.2
 New patching tool “adop” orchestrates the patching cycle

Online Patching
Online Patching Cycle - Overview
 Online Patching cycle includes 5 phases
 Application is only offline during the “Cutover” phase
 Online Patching is used to apply all patches in 12.2
• Remove
obsolete
objects
• Restart
application on
Patch Edition
• Compile invalid
objects
• Wait for a good
downtime window
• Apply one or
more patches to
the Patch Edition
• Copy the
production app
code
• Create a new
Patch Edition in
the DB
CutoverFinalizeApplyPrepare Cleanup
Users
Online
Users
Offline
Users
Online

#6 Understand Edition
Based Redefinition

#6 Understand Edition Based Redefinition
 Edition Based Redefinition
– New features of the 11gR2 database
– Enables multiple copies of the same code object to co-exist
 Editioned Objects (Code Objects)
– Database automatically manages versioning
– e.g pl/sql, views, synonyms etc.
 Non-Editioned Objects (Storage Objects)
– Application layer makes these objects effectively editioned
– e.g tables, indexes, materialized views etc.

#7 Understanding the
Enablement Process

#7 Understanding the Enablement Process
 Performed as part of the R12.2 upgrade process
 Schemas in the database are converted to be editions enabled
– Turns on object versioning in the database
– Once a schema is editions enabled it cannot be reverted
 Introduces a new view of the EBS data model
– A logical rather than physical representation of the data model is
presented
– Changes the way many objects are defined and patched
 New standards must be followed
 Customers should fully review the new standards

Logical view of the data model
• 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
Apps APPLSYS• E-Business Code
• Custom Code
• 3rd Party Code
WF_ITEMS
(Synonym)
WF_ITEMS#
(Editioning view)
WF_ITEMS
(Table)
#7 Understanding the Enablement Process

#7 Database Editioning Views
 Patch & Run Edition see a
different projection of the table
– Code in the Run edition will treat
description as 30 characters
– Code in the Patch edition will use the
new expanded 80 characters
Data Model Upgrades Run Edition View
Patch Edition View
Name Type
ID NUMBER
NAME VARCHAR2(30)
DESCRIPTION VARCHAR2(30)
DESCRIPTION#1 VARCHAR2(80)
Desc FND_TABLE
Name Type
ID NUMBER
NAME VARCHAR2(30)
Desc FND_TABLE (Editioning View)
Name Type
ID NUMBER
NAME VARCHAR2(30)
Desc FND_TABLE (Editioning View)

#7 Transparent Data Model Changes
Cross Edition Triggers
ID NAME DESCRIPTION DESCRIPTION#2
FND_TABLE
1 Table A thing with 4 legs
2 Window Something to see thru
3 Door Keeps the cold out
A THING WITH 4 LEGS
SOMETHING TO SEE THRU
KEEPS THE COLD OUT
ID NAME DESCRIPTION
1 Table A thing with 4 legs
2 Window Something to see thru
3 Door Keeps the cold out
ID NAME DESCRIPTION
1 Table A THING WITH 4 LEGS
2 Window SOMETHING TO SEE THRU
3 Door KEEPS THE COLD OUT
Run Edition view of the data
Patch Edition view of the data
Cross Edition Trigger

#8 Review Online Patching
Standards

 Helps prepare customization and extensions for Online Patching
– Custom schemas that require registration for Online Patching enablement
– Custom objects that require manual intervention in order to avoid
invalidation post enablement
 All Customers should
– Execute the Readiness Reports before enabling Online Patching
– Understand and fix any exceptions reported before enabling Online
Patching
 Standalone patches available for Readiness Reports
– 11i, 12.0 & 12.1
a) Readiness Reports
#8 Review Online Patching Standards

 Non-Editioned Objects can’t reference Editioned Objects
 12.2 upgrade removes all such dependencies
• PLSQL
Spec
Body
Function
Procedure
• Tables
• Indexes
• Materialized Views
• Sequences
Editioned ObjectsNon-Editioned Objects • Views
• Editioning Views
•Triggers
• Types
• Synonyms
Relationship between Editioned and Non Editioned Objects

 Summary Readiness Report (ADZDPSUM.sql)
– Reports schemas that will be automatically editioned
 All schemas owned by EBS are automatically registered for editioning
– Reports custom schemas with objects that will become invalid if schema is
not registered for editioining
 Recommended to register all schemas listed
 Manual Readiness Report ( ADZDPMAN.sql)
– Reports custom objects that must be manually fixed before Online
Patching is enabled
– Any exception not fixed will cause object invalidation post enablement

1. Execute Summary
Readiness Report
(ADZDPSUM.sql)
2.Register Custom
Schemas for
Enablement
Unregistered
Custom
Schemas?
Yes
3.Execute Manual Fix
Readiness Report
(ADZDPMAN.sql)
Exceptions
Reported?
4.Fix Exceptions
No
No
Yes
Ready for
enablement

 Database Objects and code must follow a new set of standards
– Standards must be followed to successfully patch objects Online
 Review your customizations for violations of Online Patching standards
– Database check report ( ADZDDBCC.sql)
 Scans the data dictionary for objects and code that violate the Online Patching
standards
(i.e. Table with LONG columns cannot be patched online)
– File System check report (gscc.pl)
 Scans the file system for source files that violate the Online Patching standards
(i.e. DML statements must access tables via APPS synonyms)
b) Development Standards

b) Development Standards
1. Execute Database
Standards Checker
( ADZDDBCC.sql)
Exceptions
Reported
3. Execute File System
Standards Checker
(gscc.pl)
2. Fix Exceptions
Yes
No
4. Fix ExceptionsExceptions
Reported
Yes
Code
Standards
Compliant
No

 The standalone Readiness Reports are documented in the MOS
Note:1531121.1
 Development Standards are documented in Chapter 7 of the
Oracle E-Business Suite Developer's Guide Release 12.2.
– This book is currently available as part of the R12.2 Documentation
Library. The library can be downloaded from the Software Delivery Cloud,
Under E-Business Suite 12.2 Media Pack
References for Readiness Reports and Development Standards

#9 Plan for 12.2 Dual File
System

#9 Plan for 12.2 Dual File System
 Two complete file systems are always present
– Run Edition - Used by the running Application
– Patch Edition – Either:
 Currently being patched
or
 Waiting for the next patching cycle
– The two files systems are rotated between Run
and Patch during every patch cycle
Cutover
Prepare
Prepare
Cutover
1
2
1
2

WebLogic Server
Oracle HTTP Server
Developer 10.1.2
COMMON_TOP
APPL_TOP
INST_TOP
File System 2
WebLogic Server
Oracle HTTP Server
Developer 10.1.2
COMMON_TOP
APPL_TOP
INST_TOP
File System 1
Synchronization managed
by patching tools
Edition-Based
Redefinition
File System Non Editioned
APPL_TOP_NE
PATCH_TOP
LOGS

 File System 1 (FS1)
– Stores a complete copy of all Applications and Middle Tier code
 File System 2 (FS2)
– Stores a complete copy of all Applications and Middle Tier code
 File System Non-Editioned (FS_ NE)
– Stores data that is written or read from the file system
– Report Outputs
– Log Files etc.
 FS1 and FS2 switch roles at cutover
– Patch file system becomes the Run file system
– Run file system becomes the Patch file system
Dual File System + Non-Editioned File System

Online Patching – Resource Considerations
 Database
– SYSTEM tablespace requires double its current space allocation
 25GB increase to 50GB
– SEED tablespace requires double its current space allocation
 5GB increases to 10GB
 File System
– 2 file systems require double the space of 1 file system 
Dual File System + Non-Editioned File System

#10 Consider New
Operational Characteristics

#10 Consider New Operational Characteristics
 Downtime windows are now measured in minutes
– What operations other than applying patches do you perform?
– Can these operations be performed while the E-Business Suite is online?
– Example: Taking backups (pre-patching, during-patching or post-patching)
 Testing
– Patch Edition is not a testing environment
– Patches still need to be tested on a test system
– Consider new test scenarios
 Users can be online during patch application

#10 Consider New Operational Characteristics
 Train the development team
– Review the new coding standards, for example:
 Cross Edition Triggers replace data upgrade scripts
 Table names must be unique at 29th character
– Review the new deployment standards, for example:
 Custom files must be applied to the Patch file system
 Custom files must be registered with the custom driver
Handling Customizations

Key Takeaways

Summary: Preparing for the 12.2 Upgrade
1. Review the Functional Changes
2. Understand the Technical
Architecture Changes
3. Learn about WebLogic Server
4. Consider Upgrading your Technical
Architecture
1. Understand the 12.2 Patching Cycle
2. Understand Edition Based Redefinition
(EBR, 11gR2 DB)
3. Understanding the Enablement Process
for Online Patching (OP)
4. Review Online Patching Standards
5. Plan for 12.2 Dual File System
6. Consider New Operational
Characteristics
12.2 Overall EBS Readiness 12.2 Online Patching Readiness

2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023
E-Business Suite Support Timelines
Reinforce Customer Choice to Use 12.1 or 12.2
11.5.10
GA Nov 2004
Premier Sustaining
Premier Sustaining
Nov 2013
Jan 2012 Jan 2015
Nov 2010
Extended
Dec 2015
12.0
GA Jan 2007
12.1
GA May 2009
12.2
GA Sep 2013
Sustaining
Dec 2016 Dec 2019May 2009
Extended
Premier Sustaining
Sep 2018 Sep 2021Sep 2013
Extended
3
Support updates as of Sep 2013
1. 11.5.10 Sustaining Support Exception through Dec 2015 (from Dec 2014; additional 12 months)
2. 12.1 Premier Support through Dec 2016 (from May 2014; additional 31 months)
3. 12.1 Extended Support through Dec 2019 (from Dec 2018; additional 12 months)
1
2
3
Premier 2
Extended
1
Exception
For more info, see Oracle Lifetime Support Policy: Oracle Applications

Which Release Should You Target?
 Choose 12.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 if you:
– Prefer to target a release with thousands of live customers
– Would like to stay on 12.1 for 3-5 years before upgrading to 12.2
– Need to move from a release below 11.5.10 with no direct upgrade to 12.2
Will Depend on Your Circumstances

Key Takeaways
 Don’t wait, keep moving forward with your upgrade
 Direct upgrade path from EBS 11.5.10.2, 12.0.4 and 12.0.6 to 12.2
 11gR2 (11.2.0.3) is Pre-requisite for 12.2
 Get familiar with Web Logic Server
 Understand the 12.2 Patching Cycle
 Review Online Patching Standards
 Plan for 12.2 Dual File System
 Consider New Operational Characteristics

Q&A

Preparing forr12-140703020001-phpapp02

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie Preparing forr12-140703020001-phpapp02

Ähnlich wie Preparing forr12-140703020001-phpapp02 (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Preparing forr12-140703020001-phpapp02