Migrating and Managing Customizations For Oracle EBS 12.2 (CON5455)

Oracle OpenWorld 2019
SAN FRANCISCO
Migrating and Managing
Customizations for
Oracle E-Business Suite R12.2
Santiago Bastidas
Product Management Director

Applications Development, Oracle
2 Copyright © 2019 Oracle and/or its affiliates.

Safe Harbor
The following is intended to outline our general product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code,
or functionality, and should not be relied upon in making purchasing decisions. The development,
release, timing, and pricing of any features or functionality described for Oracle’s products may change
and remains at the sole discretion of Oracle Corporation.
Statements in this presentation relating to Oracle’s future plans, expectations, beliefs, intentions and
prospects are “forward-looking statements” and are subject to material risks and uncertainties. A detailed
discussion of these factors and other risks that affect our business is contained in Oracle’s Securities and
Exchange Commission (SEC) filings, including our most recent reports on Form 10-K and Form 10-Q
under the heading “Risk Factors.” These filings are available on the SEC’s website or on Oracle’s website
at http://www.oracle.com/investor. All information in this presentation is current as of September 2019
and Oracle undertakes no duty to update any statement in light of new information or future events.
Copyright © 2019 Oracle and/or its affiliates.

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

Agenda

• Key Takeaways

Customizations in E-Business Suite
• 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 Release 12.1
Application Tier Forms

Reports
Database
Scripts PLSQL
APPL_TOP Application Schemas
Custom
Application Code Custom Code
Code OAF
Java
COMMON_TOP Application Code
Custom Application Data Model
Application Code
Code
Oracle Developer 10g Custom Schemas
Tables
OC4J Custom Code Indexes
Web Listener Custom Data Model

Oracle E-Business Suite 12.2 and Online Patching
Quick High-level Recap
Production Copy of Production
E-Business Suite Patches

E-Business Suite
12.2.3 - 12.2.9
12.2.3
- Customization
-…
• Copy the production code, including customizations

• Apply patches to the copy

Dual File System
Application Tier
File System 1 File System 2
APPL_TOP APPL_TOP
COMMON_TOP COMMON_TOP
INST_TOP INST_TOP
Oracle Developer 10g Oracle Developer 10g
WebLogic Server WebLogic Server
Oracle OHS Web Listener Oracle OHS Web Listener
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
Edition-Based
Redefinition

Customizations in Oracle E-Business Suite R12.2
• 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
Application Tier Database

APPL_TOP APPL_TOP Application Schemas
Custom Custom Custom Code
Application Code Sync Application Code
Code Code Application Code
COMMON_TOP COMMON_TOP Data Model Logical View
Custom Custom Application Data Model
Code Code
Custom Schemas
Oracle Developer 10g Oracle Developer 10g Custom Code
WebLogic Server WebLogic Server Data Model Logical View
Oracle OHS Web Listener Oracle OHS Web Listener Custom Data Model
Dual File System Editioned DB Schemas

Agenda

• Key Takeaways

Prepare for the New 12.2 Architecture
• 11gR2/12R1/19c Database
– Edition Based Redefinition
– Understand which objects are editioned (versioned)
– Understand which objects are NOT edition (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

Editioned Database Objects
• All code type objects support editioning
• The Database automatically manages multiple copies of these objects during patching
Editioned Objects
• PLSQL • Views
Package Spec • Editioning views
Package Body • Triggers
Function • Types
Procedure • Synonyms

Non-Editioned Database Objects
• Storage objects do not support editioning
• Online Patching uses advanced EBR features to manage these objects during patching
Non-Editioned Objects
• Tables
• Indexes
• Materialized Views
• Sequences

Managing 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

Handling Non Editioned Objects in Online Patching
Patch Driver
– Code Changes
– Data Model Changes
• Existing columns are never

changed in a patch
• Data model changes are
implemented as new columns
• Running application does not see
the new column

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

Logical view of the Application 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
• E-Business Code Apps APPLSYS
• Custom Code
WF_ITEMS WF_ITEMS# WF_ITEMS

• 3rd Party Code (Synonym) (Editioning view) (Table)

Database Editioning and Transactional Data
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 Views
Data Model Changes
Service Request Table Definition
Name Type
Run Edition View ID NUMBER Patch Edition View
Service Request Editioning View FILED_BY VARCHAR2(30) Service Request Editioning View
STATUS
STATUS NUMBER
NUMBER
Name Type Name Type
STATUS#1 VARCHAR2(30)
ID NUMBER ID NUMBER
FILED_BY VARCHAR2(30) FILED_BY VARCHAR2(30)
STATUS NUMBER STATUS VARCHAR2(30)
Run & Patch Edition see a different projection of the table

Code 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 column
Values = ‘OPEN’, ‘INFO_REQUESTED’, ‘FIXED’

Transparent Data Model Changes
• 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

Cross-Edition Triggers Fire for Existing Rows
Cross Edition Trigger
Service Request Table
ID FILED_BY STATUS STATUS#1

1 JSMITH 11 OPEN
2 RGUPTA 30 INFO_REQUESTED
3 SDUBOIS 90 FIXED
Run Edition view of the data Patch Edition view of the data
ID FILED_BY STATUS ID FILED_BY STATUS
1 JSMITH 11 1 JSMITH OPEN
2 RGUPTA 30 2 RGUPTA INFO_REQUESTED
3 SDUBOIS 90 3 SDUBOIS FIXED

Cross-Edition Triggers Fire for New Rows
Cross Edition Trigger
Service Request Table

1 JSMITH 11 OPEN
2 RGUPTA 30 INFO_REQUESTED
3 SDUBOIS 90 FIXED
4 ACHANG 11 OPEN
Run Edition view of the data Patch Edition view of the data
ID FILED_BY STATUS ID FILED_BY STATUS
1 JSMITH 11 1 JSMITH OPEN
2 RGUPTA 30 2 RGUPTA INFO_REQUESTED
3 SDUBOIS 90 3 SDUBOIS FIXED
4 ACHANG 11 4 ACHANG OPEN
Handling Seed Data
• 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

Editioned Data Storage
Database FND_LOOKUPS
Run Edition
• Always operates on a private
copy of the seed data
• Never affected by patching
Patch Edition
• Seed data Loader
• Prepares table for patching
• All rows are copied
• Loads seed data changes into

the copy
AD+TXK.Delta.8: 2 Sets of Rows permanent. Sync only the changes

Agenda

• Key Takeaways

Preparing
Customizations for the
12.2 Upgrade
• Customizations Upgrade Project

• Create a customizations catalog
• Analyze and Implement code remediation
• Deploy revised customizations

Customizations Catalog
Customizations Upgrade Project
• Make sure the catalog identifies all the artifacts
– Database
– Middle Tier
– Technologies Used
• OAF, Forms, Reports, Java, PLSQL, etc

Application Management Suite - Customization Management
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

12.2 Development Standards for Custom Code
Decide Which Standards Compliance Level to Target
Minimal Full
Required, minimal set of standards must be met Optional, additional standards must be met for
for custom code to operate correctly on 12.2 custom code to be Online Patchable
• Decision is based on importance of minimizing downtime

• In either case, EBS Patches are always applied online

Utilities available for the Analysis
• 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

Online Patching Readiness Reports
• 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

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 Report
Section Headers indicate how to fix the standards violations
Sample Report: ADZDPMAN.sql
DOC> **********************************************************************
DOC> SECTION-1
DOC> **********************************************************************
DOC>
DOC> MANUAL FIX: Objects in Non-EBS schemas that depend on Editioned
DOC> 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 to
DOC> report ADZDPSUM.sql
DOC> - Drop object, if not required
DOC> - Redefine object to remove dependency
DOC> - 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 Standards Compliance Report
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)

Data Model Access Pattern
Pre-12.2 Database
APPS EBS Schema
Synonym
EBS Code
Custom Code
EBS Table
CUSTOM Schema
All code must access the data
Custom Code model via the Logical View
(APPS synonyms)
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

Code Naming Standards
• Table name cannot end with a “#” character
– Reason: Editioning View name matches the name of the table + “#”
FND_CONCURRENT_REQUESTS#
Editioning View ID FILED_BY STATUS
• Column name may only use “#” as last character

– Reason: “#” character reserved for identifying patched columns
Table FND_CONCURRENT_REQUESTS

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

Application Tier Data Model Access Pattern
All code must access the data model via the Logical View (APPS synonyms)
APPS EBS Schema

Synonym
E-Business Code
Custom Code EBS Table
Application Tier Custom Table Pre-12.2 Database

Custom Schema
Section headers indicate the type of compliance: Minimal or Full
Report: ADZDDBCC.sql
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 an
DOC> object name is reserved for the Online Patching tool.
DOC> - Fix: Change the object name to use an ordinary identifier character
DOC> 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

Deploy Revised Customizations
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

E-Business Suite 12.1 Instance Ready for 12.2 Upgrade

APPL_TOP Application Schemas
Custom
Application Code Custom Code
Code
COMMON_TOP Application Code
Custom Application Data Model
Application Code
Code
Oracle Developer 10g Custom Schemas
OC4J Custom Code
Web Listener Custom Data Model
Minimal/Full Online Patching Compliant

Agenda

• Key Takeaways

R12.2 Technical Upgrade Process
Upgrade Upgrade To 12.2.0 Upgrade to Configure
Database 12.2.x RUP System to
Production
Capacity
1 2 3 4 5 6 7
Lay down Enable Deploy Customizations

R12.2 File Online and External
System Patching Integrations

Key Stages for Customization Migration
Upgrade Upgrade To 12.2.0 Upgrade to Configure
Database 12.2.x RUP System to
Production
Capacity
1 2 3 4 5 6 7
Lay down Enable Deploy Customizations

R12.2 File Online and External
System Patching Integrations

1 2 3 4 5 6 7

Lay Down R12.2 File System
• Completely New Dual File System
• Does not carry over any code from pre-12.2 file system
Oracle E-Business Suite R12.2

Application Tier
APPL_TOP APPL_TOP
Application Code Application Code
Rapid
COMMON_TOP COMMON_TOP
Wizard Application Code Application Code
Oracle Developer 10g Oracle Developer 10g
Oracle WebLogic Server Oracle WebLogic Server
OHS Web Listener OHS Web Listener

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

1 2 3 4 5 6 7

• 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

1 2 3 4 5 6 7

APPS EBS/Custom Schema APPS_NE

Editioned Editioned Non-Editioned
EBS Code
Custom Code
Editioning View
EBS/Custom Table User Defined
Synonym Logical
Physical View
Data Model Type
• Prepares Code for Editioning

• Enables Editioning on Schemas registered with EBS
• Creates Logical View

1 2 3 4 5 6 7

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

1 2 3 4 5 6 7
Deploy Customizations
Deploy customizations to Run file system and run adop fs-clone

APPL_TOP APPL_TOP Application Schemas
Custom Custom Custom Code
Code Code Application Code
COMMON_TOP COMMON_TOP Data Model Logical View
Custom Custom Application Data Model
Code Code
Custom Schemas
Oracle Developer 10g Oracle Developer 10g Custom Code
WebLogic Server WebLogic Server Data Model Logical View
Oracle OHS Web Listener Oracle OHS Web Listener Custom Data Model
Run Patch Run
Dual File Systems Edition Enabled Schemas
Validating Customization after 12.2 Upgrade
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 APEX_040200 Schema
– Editions Enabled as part of the Upgrade
APEX
• Custom APEX Workspace fully functional after the 12.2 upgrade
Engine
• Review the APEX certification Whitepaper for more details
Grant Select
APPS Schema
APEX Workspace
Standard published EBS APIs
Agenda

• Key Takeaways

Managing Customizations in R12.2
• Maintain customizations with Online Patching, Full

Compliance
• New R12.2 Development and Deployment Process
• New R12.2 Development Standards
• Tools to help manage customizations

Maintain Customizations with Online Patching in R12.2
Full Compliance
• Customizations are deployed during the Apply phase
• Deployment instructions available in Note:1577661.1
Middle Tier
run patch
Custom Custom
Code Code
Custom
Patch

Maintain Customizations with Online Patching in R12.2
Full Compliance
Online Patching
Cycle
Prepare Run Patch Editioned Schemas
Apply Old Run Run

Patch
Custom Code Custom Code Custom Code
Custom Code
Finalize Sync
Application Code Application Code ApplicationApplication

Code Code
Cutover Logical ViewLogical View
Technology Stack Technology Stack
Cleanup Application Data Model
fs1 fs2
Dual File Systems Schemas Editions Enabled

EBS/Custom
Patches

New R12.2 Development and Deployment Process
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

R12.2 Development and Deployment Process
Minimal Compliance
• Customizations Deployment extend the Cutover Phase
• Deployment targets the Run File system and Run Edition
Middle Tier
run patch
}
Extended Cutover
Custom
Code
Custom
$ adop phase=cutover mtrestart=no Patch

R12.2 Development and Deployment Process
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

Tools to Help Manage Customizations in R12.2
• Oracle Applications Manager - Patch Wizard

• Oracle E-Business Suite Plug-in for Enterprise
Manager Cloud Control

Tools to Help Manage Customizations
Patch Wizard
• Register
customized files
• Analyze impact to
customized files

Tools to Help Manage Customizations
Patch Wizard
Direct, Indirect and Customization Impact Analysis
• Perform patch impact

analysis on recommended
patch and prerequisites
• Analyze impact to
customizations

Application Management Suite
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

OMCS - Oracle Functional Services
Maximizing Value for Hybrid Cloud Deployments
Functional Help Desk Services Cloud Integration & Custom

Oracle SPOC Incident & Problem Services
Management Managed Cloud Integration
Minor CEMLI enhancement Service (MCIS) Setup
(legacy) CEMLI Migration
Apps Cloud Extensions on PaaS CEMLI Advisory
Continual Service Improvement Cloud DR Testing Support
Technical Administration Automated Testing Support

Non-Certified Configuration Regression Testing
Oracle Applications Oracle Applications Testing Suite-
Oracle Technology based
3rd Party Products on Oracle Performance Testing
@ Customer, @ Oracle, Oracle Leverage for UPK-based training
Tech Cloud

Agenda

• Key Takeaways

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 Bastidas
Product Management Director

Applications Development, Oracle

Migrating and Managing Customizations For Oracle EBS 12.2 (CON5455)

Uploaded by

Copyright:

Available Formats

You might also like

Migrating and Managing Customizations For Oracle EBS 12.2 (CON5455)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Migrating and Managing Customizations For Oracle EBS 12.2 (CON5455)

Uploaded by

Copyright:

Available Formats

Oracle OpenWorld 2019

Product Management Director

2 Copyright © 2019 Oracle and/or its affiliates.

Copyright © 2019 Oracle and/or its affiliates.

• Customizations in EBS 12.1 vs 12.2

5 Copyright © 2019 Oracle and/or its affiliates.

• Customizations in EBS 12.1 vs 12.2

6 Copyright © 2019 Oracle and/or its affiliates.

• Implemented in several technologies

7 Copyright © 2019 Oracle and/or its affiliates.

Application Tier Forms

Web Listener Custom Data Model

8 Copyright © 2019 Oracle and/or its affiliates.

Production Copy of Production

E-Business Suite Patches

• Copy the production code, including customizations

9 Copyright © 2019 Oracle and/or its affiliates.

Oracle Developer 10g Oracle Developer 10g

WebLogic Server WebLogic Server

Oracle OHS Web Listener Oracle OHS Web Listener

Two Complete Copies of the File System

10 Copyright © 2019 Oracle and/or its affiliates.

• Efficiently stores multiple copies of Application

11 Copyright © 2019 Oracle and/or its affiliates.

• To be patched Online they have to comply with Online Patching:

12 Copyright © 2019 Oracle and/or its affiliates.

Application Tier Database

Dual File System Editioned DB Schemas

13 Copyright © 2019 Oracle and/or its affiliates.

• Customizations in EBS 12.1 vs 12.2

14 Copyright © 2019 Oracle and/or its affiliates.

15 Copyright © 2019 Oracle and/or its affiliates.

16 Copyright © 2019 Oracle and/or its affiliates.

17 Copyright © 2019 Oracle and/or its affiliates.

18 Copyright © 2019 Oracle and/or its affiliates.

– Data Model Changes

• Existing columns are never

19 Copyright © 2019 Oracle and/or its affiliates.

20 Copyright © 2019 Oracle and/or its affiliates.

• E-Business Code Apps APPLSYS

WF_ITEMS WF_ITEMS# WF_ITEMS

21 Copyright © 2019 Oracle and/or its affiliates.

22 Copyright © 2019 Oracle and/or its affiliates.

Run & Patch Edition see a different projection of the table

23 Copyright © 2019 Oracle and/or its affiliates.

• Cross Edition Triggers replace traditional upgrade scripts

• Pre and Post upgrade schema and data coexist

24 Copyright © 2019 Oracle and/or its affiliates.

ID FILED_BY STATUS STATUS#1

25 Copyright © 2019 Oracle and/or its affiliates.

ID FILED_BY STATUS STATUS#1

• Editioned Data Storage

27 Copyright © 2019 Oracle and/or its affiliates.

• Loads seed data changes into

AD+TXK.Delta.8: 2 Sets of Rows permanent. Sync only the changes

• Customizations in EBS 12.1 vs 12.2

29 Copyright © 2019 Oracle and/or its affiliates.

• Customizations Upgrade Project