Migrating and Managing Customizations for Oracle E-Business … · 2021. 3. 23. · •...
Transcript of Migrating and Managing Customizations for Oracle E-Business … · 2021. 3. 23. · •...
Migrating and ManagingCustomizations for Oracle E-Business Suite R12.2
Santiago BastidasProduct Management DirectorE-Business Suite DevelopmentOracle
Copyright © 2020, Oracle and/or its affiliates3
Agenda
• Customizations in EBS 12.1 vs 12.2• 12.2 Architecture changes to Support Online Patching• Preparing Customizations for the EBS 12.2 Upgrade• 12.2 Upgrade impact to Customizations• Managing Customizations in 12.2• Key Takeaways
Copyright © 2020, Oracle and/or its affiliates4
Agenda
• Customizations in EBS 12.1 vs 12.2• 12.2 Architecture changes to Support Online Patching• Preparing Customizations for the EBS 12.2 Upgrade• 12.2 Upgrade impact to Customizations• Managing Customizations in 12.2• Key Takeaways
• Implemented in several technologies• Installed in the middle tier and in the database• Database customizations• Deployed in custom schemas and EBS schemas• Could have dependencies on EBS code
Customizations in E-Business Suite
Copyright © 2020, Oracle and/or its affiliates5
Customizations Release 12.1
Copyright © 2020, Oracle and/or its affiliates6
COMMON_TOP
Custom Schemas
Application Tier Database
Application Code
Custom Code
Web Listener
OC4J
Oracle Developer 10g
Application Schemas
Application Code
Custom Code
Custom Code
Application Data Model
Custom Data Model
APPL_TOPApplication
CodeCustom
Code
FormsReportsScripts
OAFJava
PLSQL
TablesIndexes
Quick High-level RecapOracle E-Business Suite 12.2 and Online Patching
Copyright © 2020, Oracle and/or its affiliates7
• Copy the production code, including customizations• Apply patches to the copy
Patches- 12.2.10-
Customization- …
E-Business Suite12.2.9
Production Copy of Production
E-Business Suite12.2.9
Dual File SystemOracle E-Business Suite 12.2 and Online Patching
Copyright © 2020, Oracle and/or its affiliates8
Application Tier
Oracle OHS Web Listener
WebLogic Server
Oracle Developer 10g
Oracle OHS Web Listener
WebLogic Server
Oracle Developer 10g
INST_TOP
COMMON_TOP
APPL_TOP
INST_TOP
COMMON_TOP
APPL_TOP
File System 1 File System 2
Two Complete Copies of the File System
Edition-Based Redefinition
• Efficiently stores multiple copies of Application
definitions in the same database
• Provides an isolation mechanism (“Edition”) that
allows pre-upgrade and post-upgrade schemas to
co-exist
• Client code chooses the particular “Edition” that it
wants to connect to
Oracle E-Business Suite 12.2 and Online Patching
Copyright © 2020, Oracle and/or its affiliates9
Edition-Based Redefinition
• To be patched Online they have to comply with Online Patching: • Development Standards• Patching Procedures
• Exist in both file systems (dual file systems)• Custom Schemas with dependencies on EBS objects must be editions-
enabled
Customizations in Oracle E-Business Suite R12.2
Copyright © 2020, Oracle and/or its affiliates10
Customizations in Oracle E-Business Suite R12.2
Copyright © 2020, Oracle and/or its affiliates11
Custom Schemas
Database
Application Schemas
Application CodeCustom Code
Custom Code
Application Data Model
Custom Data Model
COMMON_TOP
Application Tier
Application Code
Custom Code
Oracle OHS Web Listener
WebLogic Server
Oracle Developer 10g
APPL_TOPApplication
CodeCustom
Code
COMMON_TOPApplication
CodeCustom
Code
Oracle OHS Web Listener
WebLogic Server
Oracle Developer 10g
APPL_TOPApplication
CodeCustom
Code
Data Model Logical View
Data Model Logical View
Editioned DB Schemas
Sync
Sync
Dual File System
Copyright © 2020, Oracle and/or its affiliates12
Agenda
• Customizations in EBS 12.1 vs 12.2• 12.2 Architecture changes to Support Online Patching• Preparing Customizations for the EBS 12.2 Upgrade• 12.2 Upgrade impact to Customizations• Managing Customizations in 12.2• Key Takeaways
• 11gR2/12R1/19c Database! Edition Based Redefinition! Understand which objects are editioned (versioned)! Understand which objects are NOT editioned (non-versioned)
• File System! Dual File System! Non editioned file system
• New Patching tool! ADOP
• New Customization Deployment Procedure! 1577661.1 Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2
Prepare for the New 12.2 Architecture
Copyright © 2020, Oracle and/or its affiliates13
• All code type objects support editioning• The Database automatically manages multiple copies of these objects during patching
Editioned Database Objects
Copyright © 2020, Oracle and/or its affiliates14
• PLSQL
Package Spec
Package Body
Function
Procedure
Editioned Objects
• Views
• Editioning views
• Triggers
• Types
• Synonyms
• Storage objects do not support editioning• Online Patching uses advanced EBR features to manage these objects during patching
Non-Editioned Database Objects
Copyright © 2020, Oracle and/or its affiliates15
• Tables
• Indexes
• Materialized Views
• Sequences
Non-Editioned Objects
What about the data?
• Logical view of the data model! Isolates the running Application from changes to the data model ! Editioning Views
• In place upgrade of transactional data! New transactions entered into the system are upgraded in place! Cross Edition Triggers
• Seed data! Data in seed data tables is replicated and the patch operates on a private copy! Editioned Data Storage
Managing Non-Editioned Objects
Copyright © 2020, Oracle and/or its affiliates16
Handling Non Editioned Objects in Online Patching
Copyright © 2020, Oracle and/or its affiliates17
• Existing columns are never changed in a patch
• Data model changes are implemented as new columns
• Running application does not see the new column
Patch DriverCode Changes
Data Model Changes
• 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
Logical view of the Application Data Model
Copyright © 2020, Oracle and/or its affiliates18
• 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
Logical view of the Application Data Model
Copyright © 2020, Oracle and/or its affiliates19
Apps APPLSYS• E-Business Code
• Custom Code
• 3rd Party CodeWF_ITEMS(Synonym)
WF_ITEMS#(Editioning view)
WF_ITEMS(Table)
Online Patching Copies the Code, but not the Transactional Data
• There’s a single copy of transactional data stored in your database• Editioning views project the correct logical view of physical tables to Run and
Patch Editions• During patching, data updates are propagated from the Run Edition to the
Patch Edition using Cross-Edition Triggers
Database Editioning and Transactional Data
Copyright © 2020, Oracle and/or its affiliates20
Data Model Changes Database Editioning Views
Copyright © 2020, Oracle and/or its affiliates21
Name TypeID NUMBER
FILED_BY VARCHAR2(30)
STATUS NUMBER
Run & Patch Edition see a different projection of the tableCode in the Run edition will treat STATUS column as a Number
Values = 11, 30, 90
Code in the Patch edition will use the new 30-character STATUS columnValues = ‘OPEN’, ‘INFO_REQUESTED’, ‘FIXED’
Run Edition View Patch Edition View
Service Request Table Definition
Name TypeID NUMBER
FILED_BY VARCHAR2(30)
STATUS NUMBER
Service Request Editioning View
Name TypeID NUMBER
FILED_BY VARCHAR2(30)
STATUS VARCHAR2(30)
Service Request Editioning View
STATUS NUMBER
STATUS#1 VARCHAR2(30)
• Cross Edition Triggers replace traditional upgrade scripts• Allows the running Application to signal that a data upgrade is required
• Pre and Post upgrade schema and data coexist• Two versions of the application operate in tandem
Transparent Data Model Changes
Copyright © 2020, Oracle and/or its affiliates22
Cross-Edition Triggers Fire for Existing RowsTransparent Data Model Changes
Copyright © 2020, Oracle and/or its affiliates23
ID FILED_BY STATUS STATUS#1
Service Request Table
1 JSMITH 11
2 RGUPTA 30
3 SDUBOIS 90
OPEN
INFO_REQUESTED
FIXED
ID FILED_BY STATUS
1 JSMITH 11
2 RGUPTA 30
3 SDUBOIS 90
Run Edition view of the data Patch Edition view of the data
Cross Edition Trigger
ID FILED_BY STATUS
1 JSMITH OPEN
2 RGUPTA INFO_REQUESTED
3 SDUBOIS FIXED
Cross-Edition Triggers Fire for New RowsTransparent Data Model Changes
Copyright © 2020, Oracle and/or its affiliates24
ID FILED_BY STATUS STATUS#1
Service Request Table
1 JSMITH 11
2 RGUPTA 30
3 SDUBOIS 90
OPEN
INFO_REQUESTED
FIXED
ID FILED_BY STATUS
1 JSMITH 11
2 RGUPTA 30
3 SDUBOIS 90
Run Edition view of the data Patch Edition view of the data
ID FILED_BY STATUS
1 JSMITH OPEN
2 RGUPTA INFO_REQUESTED
3 SDUBOIS FIXED
Cross Edition Trigger
4 ACHANG 11
4 ACHANG 11 4 ACHANG OPEN
OPEN
• Seed data is data stored in database tables that affects the behavior of the application and is patched by EBS development
• Patches cannot be allowed to modify the seed data seen by the running application
• Editioned Data Storage• Allows an Online Patch to modifying seed data • A copy is made of seed data and stored within the same table• Patches only interact with the copy• Old copy is kept in sync by Online Patching
Handling Seed Data
Copyright © 2020, Oracle and/or its affiliates25
Editioned Data Storage
Copyright © 2020, Oracle and/or its affiliates26
FND_LOOKUPS
Patch Edition
• Seed data Loader
• Prepares table for patching
• All rows are copied
• Loads seed data changes into the copy
DatabaseRun Edition
• Always operates on a private copy of the seed data
• Never affected by patching
AD+TXK.Delta.8: 2 Sets of Rows permanent. Sync only the changes
Copyright © 2020, Oracle and/or its affiliates27
Agenda
• Customizations in EBS 12.1 vs 12.2• 12.2 Architecture changes to Support Online Patching• Preparing Customizations for the EBS 12.2 Upgrade• 12.2 Upgrade impact to Customizations• Managing Customizations in 12.2• Key Takeaways
Copyright © 2020, Oracle and/or its affiliates28
Preparing Customizations for the 12.2 Upgrade• Customizations Upgrade Project• Create a customizations catalog• Analyze and Implement code remediation• Deploy revised customizations
Customizations Upgrade Project
Make sure the catalog identifies all the artifacts• Database• Middle Tier• Technologies Used
• OAF, Forms, Reports, Java, PLSQL, etc
Customizations Catalog
Copyright © 2020, Oracle and/or its affiliates29
Customizations Catalog
• Discovery & reporting of EBS customizations
• Ability to validate, package and deploy customizations across EBS instances
• Over 200 customization file types supported
• Interface with external Source Code Version Control systems
• Validation of the custom objects using: • Oracle Defined Standards
• Optionally, User Defined Standards
• Validates and reports readiness of customizations for Online Patching
Application Management Suite - Customization Management
Copyright © 2020, Oracle and/or its affiliates30
Decide Which Standards Compliance Level to Target
MinimalRequired, minimal set of standards must be met for custom code to operate correctly on 12.2
FullOptional, additional standards must be met for custom code to be Online Patchable
12.2 Development Standards for Custom Code
Copyright © 2020, Oracle and/or its affiliates31
• Decision is based on importance of minimizing downtime• In either case, EBS Patches are always applied online
• Online Patching Readiness Reports• All sections on this report refer to Minimal compliance
• Online Patching Standards Compliance Report• Section headers indicate the type of compliance: Minimal or Full
• Reports are available as standalone patches for 11i, 12.0, 12.1 and 12.2• Note:1531121.1 Using the Online Patching Readiness Reports in Oracle E-Business Suite Release
12.2
Utilities available for the Analysis
Copyright © 2020, Oracle and/or its affiliates32
• Validate Edition Based Redefinition compliance• All Sections in the report refer to Minimal compliance• 12.2 Upgrade will automatically address most custom code standards violations contained in
schemas registered with the application• Failure to address standards violations will result in Invalid Custom Code after the R12.2
Upgrade
Online Patching Readiness Reports
Copyright © 2020, Oracle and/or its affiliates33
Reports
• ADZDPSUM.sql
! Identifies Custom Schemas with objects that have dependencies on EBS Code
! Generates statements to register identified schemas with the application
• ADZDPMAN.sql
! Identifies Objects that violate the Minimal Compliance standards which require manual intervention
! Each section header provides a description of standards violation and how to fix them
• ADZDPAUT.sql
! Identifies Objects that violate the Minimal Compliance standards and are automatically fixed by the Online Patching Enablement process. There is no action required on the output of this report
Online Patching Readiness Reports
Copyright © 2020, Oracle and/or its affiliates34
Online Patching Readiness Report
Copyright © 2020, Oracle and/or its affiliates35
Section Headers indicate how to fix the standards violations
Sample Report: ADZDPMAN.sql
DOC> **********************************************************************DOC> SECTION-1DOC> **********************************************************************DOC>DOC> MANUAL FIX: Objects in Non-EBS schemas that depend on EditionedDOC> Objects of EBS.DOC>DOC> To fix these violations, do one of the following:DOC> - Register object schema (owner) as a Custom EBS Schema, please refer toDOC> report ADZDPSUM.sqlDOC> - Drop object, if not requiredDOC> - Redefine object to remove dependencyDOC> - Move the object to a registered Custom EBS Schema
Summary
• Very few violations require manual intervention if the schema is registered with the application, e.g.!Materialized View with a dependency on a PLSQL package or function!Use of LONG and LONG RAW columns
• Report output will direct you on how to address these violations• Reports applicable during the preparation to the 12.2 upgrade
Online Patching Readiness Reports
Copyright © 2020, Oracle and/or its affiliates36
Overview
• Validates standards applicable to Minimal and Full Compliance! Section headers indicate the type of compliance: Minimal or Full
• Standards include! Data Model Access Pattern! Code naming standards! Special Object definition requirements (VPDs, MVs)
• Failure to address these standards violations could result in! Future Code invalidation! Inability to patch Custom Code online (Downtime required to maintain Custom Code,
Full Compliance)
Online Patching Standards Compliance Report
Copyright © 2020, Oracle and/or its affiliates37
Data Model Access PatternOnline Patching Standards Compliance Report
Copyright © 2020, Oracle and/or its affiliates38
Pre-12.2 Database
All code must access the data model via the Logical View (APPS synonyms)
APPS EBS SchemaSynonym
EBS Table
EBS Code
Custom Code
CUSTOM Schema
Custom Code
Custom Table
Code Naming Standards
These standards allow Online Patching to automatically manage derived objects
• Table Names must be unique within the first 29 characters• Column Names must be unique within the first 28 characters • Table Names cannot end with 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
Online Patching Standards Compliance Report
Copyright © 2020, Oracle and/or its affiliates39
Code Naming StandardsOnline Patching Standards Compliance Report
Copyright © 2020, Oracle and/or its affiliates40
Table name cannot end with a “#” character• Reason: Editioning View name matches the name of the table + “#”
Column name may only use “#” as last character• Reason: “#” character reserved for identifying patched columns
ID FILED_BY STATUS
FND_CONCURRENT_REQUESTS#Editioning View
ID FILED_BY STATUS STATUS#1
FND_CONCURRENT_REQUESTSTable
Application Tier Data Model Access Pattern
• Included as part of the Readiness Reports (gscc.pl)• Validates Data Model Access Pattern in middle tier source code! Java! XML! SQL! PLSQL! Oracle Forms! Oracle Reports
Online Patching Standards Compliance Report
Copyright © 2020, Oracle and/or its affiliates41
Application Tier Data Model Access Pattern
All code must access the data model via the Logical View (APPS synonyms)
Online Patching Standards Compliance Report
Copyright © 2020, Oracle and/or its affiliates42
APPS EBS Schema
E-Business Code
Custom Code
Synonym
EBS Table
Custom Schema
Custom Table Pre-12.2 DatabaseApplication Tier
• Section headers indicate the type of compliance: Minimal or Full
• Report: ADZDDBCC.sql
Online Patching Standards Compliance Report
Copyright © 2020, Oracle and/or its affiliates43
DOC> **********************************************************************DOC> SECTION-10 [full]DOC> **********************************************************************DOC> "APPS object names must end with alphanumeric character."DOC>DOC> - P2: May cause object name conflicts during online patching.DOC> Use of special characters as the last character of anDOC> object name is reserved for the Online Patching tool.DOC> - Fix: Change the object name to use an ordinary identifier characterDOC> as the last character: A-Z a-z 0-9 _ # $DOC> - Unused objects can be ignored or dropped.DOC>#
Summary
• Violations to the standards can be very easily fixed, do not require advanced development skills
• Reports applicable during the preparation to the 12.2 Upgrade and to validate future customization development
Online Patching Standards Compliance Report
Copyright © 2020, Oracle and/or its affiliates44
Customizations Upgrade Project
• Compatible with any pre-12.2 releases• Remediated Code could be! Deployed to the current production environment (Preferred)! Deployment can be deferred to the upgrade downtime
Deploy Revised Customizations
Copyright © 2020, Oracle and/or its affiliates45
E-Business Suite 12.1 Instance Ready for 12.2 Upgrade
Copyright © 2020, Oracle and/or its affiliates46
COMMON_TOP
Application Tier
Application Code
Custom Code
Web Listener
OC4J
Oracle Developer 10g
APPL_TOPApplication
CodeCustom
Code
Custom Code
Custom Code
Minimal/Full Online Patching Compliant
Custom Schemas
Database
Application Schemas
Application Code
Custom Code
Custom Code
Application Data Model
Custom Data Model
Copyright © 2020, Oracle and/or its affiliates47
Agenda
• Customizations in EBS 12.1 vs 12.2• 12.2 Architecture changes to Support Online Patching• Preparing Customizations for the EBS 12.2 Upgrade• 12.2 Upgrade impact to Customizations• Managing Customizations in 12.2• Key Takeaways
R12.2 Technical Upgrade Process
Copyright © 2020, Oracle and/or its affiliates48
Upgrade Database
Lay down R12.2 File System
21
Enable Online Patching
4
Upgrade To 12.2.0
3
Deploy Customizations and External Integrations
6
Upgrade to 12.2.x RUP
5
Configure System to ProductionCapacity
7
Key Stages for Customization MigrationR12.2 Technical Upgrade Process
Copyright © 2020, Oracle and/or its affiliates49
Lay down R12.2 File System
21
Enable Online Patching
4
Upgrade To 12.2.0
3
Deploy Customizations and External Integrations
6
Upgrade to 12.2.x RUP
5
Configure System to ProductionCapacity
7
Upgrade Database
Lay Down R12.2 File System
• Completely New Dual File System• Does not carry over any code from pre-12.2 file system
R12.2 Technical Upgrade Process
Copyright © 2020, Oracle and/or its affiliates50
APPL_TOP
Oracle E-Business Suite R12.2Application Tier
Application Code
OHS Web Listener
Oracle WebLogic Server
Oracle Developer 10g
COMMON_TOPApplication Code
APPL_TOPApplication Code
OHS Web Listener
Oracle WebLogic Server
Oracle Developer 10g
COMMON_TOPApplication Code
Rapid Wizard
1 2 3 4 5 6 7
Enable Online Patching
• This process is Database centric• Before running this process:! Deploy any remediated database code not deployed in the preparation project! Register any custom schemas identified by the preparation project ! Re-run Readiness and Database Compliance Reports to verify customization compliance
prior to Enablement
R12.2 Technical Upgrade Process
Copyright © 2020, Oracle and/or its affiliates51
1 3 4 5 6 72
Enable Online Patching
• High level steps in the process! Prepares all the database code for editioning,
• E-Business Suite code + Customizations
! Enables Editioning on E-Business Suite schemas + Previously Registered Custom schemas
! Creates the Logical View of the Oracle E-Business Suite and Custom Data Models.
• adop replaces adpatch as the official E-Business Suite patching tool from this point forward
R12.2 Technical Upgrade Process
Copyright © 2020, Oracle and/or its affiliates52
1 3 4 5 6 72
Enable Online PatchingR12.2 Technical Upgrade Process
Copyright © 2020, Oracle and/or its affiliates53
1 3 4 5 6 72
Prepares Code for EditioningEnables Editioning on Schemas registered with EBSCreates Logical View
APPS_NEAPPS EBS/Custom Schema
Synonym
EBS Code
Custom CodeEBS/Custom Table
Physical Data ModelUser Defined
TypeEditioning View
Logical View
Editioned Editioned Non-Editioned
Deploy Customizations and External Integrations
• Deploy customizations as per new guidelines
! Note:1577661.1 Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2
• Key differences compared to prior releases:
! Register custom tops with adsplice
! CUSTOM_TOP must reside within the APPL_TOP
! Apply latest AD&TXK during the upgrade, currently Delta.11
! AD&TXK Delta.8 introduced new synchronization method in prepare phase:
• File system delta synchronization available
• $ adop phase=prepare sync_mode=delta
• 16 character application short names adsplice support
R12.2 Technical Upgrade Process
Copyright © 2020, Oracle and/or its affiliates54
1 3 5 6 72 4
Deploy customizations to Run file system and run adop fs-cloneDeploy Customizations
Copyright © 2020, Oracle and/or its affiliates55
COMMON_TOP
Application Tier
Oracle OHS Web Listener
WebLogic Server
Oracle Developer 10g
APPL_TOPCustom
Code
COMMON_TOPCustom
Code
Oracle OHS Web Listener
WebLogic Server
Oracle Developer 10g
APPL_TOP
Sync
Sync
Dual File Systems Edition Enabled Schemas
Application Code
Application Code
Application Code
Application Code
Custom Schemas
Database
Application Schemas
Application CodeCustom Code
Custom Code
Application Data Model
Custom Data Model
Data Model Logical View
Data Model Logical View
Run Patch Run
Custom Code
Custom Code
1 3 5 6 72 4
Example: Custom APEX Application Upgrade
• Custom APEX Application interacting with E-Business Suite 12.1 via public APIs• APEX_EBS_EXTENSION Schema! Identified by Readiness Reports! Registered with the application prior to 12.2 upgrade! Editions Enabled as part of the Upgrade
• Custom APEX Workspace fully functional after the 12.2 upgrade• Review the APEX certification Whitepaper for more details
Validating Customization after 12.2 Upgrade
Copyright © 2020, Oracle and/or its affiliates56
APEXEngine
APEX_040200 Schema
Grant Select
Standard published EBS APIs
APPS Schema
Copyright © 2020, Oracle and/or its affiliates57
Agenda
• Customizations in EBS 12.1 vs 12.2• 12.2 Architecture changes to Support Online Patching• Preparing Customizations for the EBS 12.2 Upgrade• 12.2 Upgrade impact to Customizations• Managing Customizations in 12.2• Key Takeaways
Managing Customizations in R12.2
Copyright © 2020, Oracle and/or its affiliates58
• Maintain customizations with Online Patching, Full Compliance• New R12.2 Development and Deployment Process• New R12.2 Development Standards• Tools to help manage customizations
Full ComplianceMaintain Customizations with Online Patching in R12.2
Copyright © 2020, Oracle and/or its affiliates59
• Customizations are deployed during the Apply phase• Deployment instructions available in Note:1577661.1
Custom Patch
Middle Tier
Custom Code
patch
Custom Code
run
Full ComplianceMaintain Customizations with Online Patching in R12.2
Copyright © 2020, Oracle and/or its affiliates60
Editioned Schemas
Database
Application Data Model
Patch
Application Code
Custom Code
Logical View
Application Code
Custom Code
Logical View
Run
Custom Code
Application Code
Logical View
Run
Application Tier
Old
Run Patch
Sync
Dual File Systems Schemas Editions Enabled
Custom Code Custom Code
Application Code Application Code
Technology Stack Technology Stack
Online PatchingCycle
Apply
Finalize
Cutover
Cleanup
Prepare
Apply
Finalize
Cutover
Cleanup
Prepare
Custom Code
Application Code
Custom Code
Application Code
EBS/CustomPatches
fs1 fs2
Full Compliance
• Use the new Development and Deployment Process for future customizations
• Reference: 1577661.1 Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2
New R12.2 Development and Deployment Process
Copyright © 2020, Oracle and/or its affiliates61
Minimal Compliance
• Customizations Deployment extend the Cutover Phase• Deployment targets the Run File system and Run Edition
R12.2 Development and Deployment Process
Copyright © 2020, Oracle and/or its affiliates62
}Extended Cutover
Custom Patch
Middle Tier
patch
CustomCode
run
$ adop phase=cutover mtrestart=no
Minimal Compliance
• Minimal set of development standards required to develop new customizations! Data Model Access Pattern
• Deployment of customizations extend the Cutover Downtime• Deployment targets the Run File System and Run edition of the database
R12.2 Development and Deployment Process
Copyright © 2020, Oracle and/or its affiliates63
Tools to Help Manage Customizations in R12.2
Copyright © 2020, Oracle and/or its affiliates64
• Oracle Applications Manager - Patch Wizard• Oracle E-Business Suite Plug-in for Enterprise Manager Cloud Control
Patch WizardTools to Help Manage Customizations
Copyright © 2020, Oracle and/or its affiliates65
• Register customized files
• Analyze impact to customized files
Patch Wizard
Direct, Indirect and Customization Impact Analysis
Tools to Help Manage Customizations
Copyright © 2020, Oracle and/or its affiliates66
• Perform patch impact analysis on recommended patch and prerequisites
• Analyze impact to customizations
Customization Management – Customizations Catalog
• Discovery & reporting of inventory of EBS customizations
• Ability to validate, package and deploy customizations across EBS instances
• Over 200 customization file types supported
• Interface with external Source Code Version Control systems
• Validation of the custom objects using: • Oracle Defined Standards• Optionally, User Defined Standards
• Validates and reports readiness of customizations for Online Patching
Application Management Suite
Copyright © 2020, Oracle and/or its affiliates67
Copyright © 2020, Oracle and/or its affiliates68
Agenda
• Customizations in EBS 12.1 vs 12.2• 12.2 Architecture changes to Support Online Patching• Preparing Customizations for the EBS 12.2 Upgrade• 12.2 Upgrade impact to Customizations• Managing Customizations in 12.2• Key Takeaways
Copyright © 2020, Oracle and/or its affiliates69
Key Takeaways
• Get Familiar with the new R12.2 Architecture
• Decide the standards compliance level to target
• Create an upgrade project for your customizations ahead of the 12.2 Upgrade
• Get Familiar with the Development and Deployment Standards for R12.2
• Take advantage of Online Patching to deploy your customizations, Full Compliance
• Use the Right Tools to Maintain your customizations
Thank You
Santiago BastidasProduct Management DirectorE-Business Suite Development
Copyright © 2020, Oracle and/or its affiliates70