Oracle EBS

R12.2
Highlights People First.
Driving Solutions
and Together.
Development
Standards
Prepared by:
Gerald Jones
Senior Developer
Consultant
CherryRoad 1
About the Presenter
 Gerald Jones
 Independent Consultant based in Dallas, Texas
 Worked with Oracle EBS since 1995
 Presented papers at local and national Oracle
Users conferences
 Worked with several clients on 12.2 upgrades
 First upgrade in 2016
2
AGENDA
 New Technical Features in EBS 12.2
 Online Patching
 Editioning Concepts
 File System Changes
 Oracle Development Standards

3
Online Patching
 Oracle Introduced the concept of online patching
 Patches can be applied while the EBS application is
still up and running
 Online patching minimizes the amount of downtime
required when applying many patches
 Minimum downtime to restart application tier
 Database typically remains online

4
Online Patching – cont’d
 Must use adop utility to perform online patch cycle
 Adpatch can no longer be used
 Online patching is accomplished through major
changes at the database level and file system level

 Database Level – Editioned Based Redefinition (EBR)

 File System Level – Dual File Systems

5
Editioned Based Redefinition
(EBR)

6
Editioned Based Redefinition
(EBR)
 Editioning allows for multiple versions of
a schema object to exist in the same database
 During patching, one version is seen by users
while the other can be modified
 Database objects that do not hold data can be
editioned (e.g. Views, Functions, Packages,
Procedures)
 Database objects that hold data cannot be
editioned (e.g. Tables, Indexes, Materialized
Views)
7
EBR – Editioned Views
 For non-editionable objects, Oracle created “editioned-views”
 Editioned views ensure any changes to underlying objects are
visible to the user.
 Mainly applies to database tables
 Oracle apps synonyms point to the “editioned-view” instead of
the schema table
 Editioned view denoted by <view name>#
 Example: AP_INVOICES_ALL#
 Editioned view owned by schema owner

8
EBR – Editioned Views Cont’d
 Oracle SELECT statements required to point to editioned view
to ensure most current instantiation of the object is accessed
 Cross-Edition triggers ensure consistency of data in the event
data changes occur during patching
 Example: Table structure changes via patching. Triggers
handle any necessary data synchronizing between run and
patch edition version

9
File System Changes (Dual File
System)

10
 Dual File System – Cont’d
In an R12.2 application server, two file systems
exist:
 Run file system
 Patch file system
The patch directory structure is a copy of the ru
directory structure
Application uses run file system to execute EBS
code
11
 Dual File System – Cont’d
Patching copies current version of run filesystem to
patch filesystem prior to making any file level change
After patching completes, a cutover phase
switches the run file system to patch filesystem
to get the latest version of code. Run filesystem
becomes the patch file system
Non-editioned directory structure is used for files
not impacted by patch cycles (e.g. conc program out
files, log files,custom interface data files)
12
Development Standard Changes

13
Oracle Coding Standard
Changes
 The introduction of Oracle EBS R12.2 requires
some changes to custom development to support
online patching technical infrastructure changes

 Table Names can be no longer than 29 characters

 Column Names should be no longer than 28
characters
 Creation of custom tables should include call to
API ad_zd.upgrade to generate editioned view
14
Oracle Coding Standard Changes
– Cont’d
 SQL SELECT statements must point to the editioned view
and not a direct schema table
 Cannot ensure results if pointing to schema table
 For example, this is no longer acceptable
SELECT invoice_id FROM ap.ap_invoices_all
- Should be instead -
SELECT invoice_id FROM ap_invoices_all
 Materialized views must be recreated as normal views and
renamed as <Materialized View>||#
15
Oracle Coding Standards –
Editioning Example
Prior to Oracle Release 12.2
 Base table owned by schema owner (e.g. AP)
 Synonym for MOAC owned by APPS
 Synonym for _ALL object owned by APPS

16
Oracle Coding Standards –
Editioning Example
Oracle Release 12.2 Changes
 Editioned View added and owned by schema
owner (e.g. AP)
 APPS synonyms point to editioned view

17
Oracle Coding Standards – Custom
Table
 Creating a custom table involves the following steps
 Create the table in your RUN database as normal
 Execute the Oracle utility ad_zd.upgrade to create
editioned view of custom table
Syntax: ad_zd.upgrade (<table owner>, <table name>)
 Example: ad_zd.upgrade (‘XXXX’,’Cust_Table1’)
 Additional grants must use API ad_zd.grant_privs
Syntax: az_zd.grant_privs (<grant type>, <table name>
, <role_name>
 Example: ad_zd.grant_privs(‘SELECT’,’Cust_Table1’,
‘XXXX Role’)
18
Oracle Coding Standards – Custom
Table cont’d
 Updating a custom table involves the following steps
 Alter table in your RUN database as normal
 Execute the Oracle utility ad_zd.patch to update
editioned view of custom table
Syntax: ad_zd.patch (<table owner>, <table name>)
 Example: ad_zd.patch (‘XXXX’,’Cust_Table1’)

19
Oracle Coding Standards –
Materialized View
 Materialized view must be created as a logical view and include
# at the end of the name
 Once the logical view is created, using Oracle utility ad_zd.mview
to create editioned view of logical view
Syntax: ad_zd.mview (<schema name>, <logical view name
without the #>
 Example: ad_zd.mview (‘APPS’,’XXXX_CUSTOM_MVIEW’)
 Note: Views should be created and owned by APPS schema

20
 Oracle Coding Standards – Other
Object Types

 The coding standards for other object types such as packages,

functions, Oracle Forms, Oracle Reports, BI Publisher reports,
etc. have not really changed in the 12.2 environment. The main
point to remember with these object types is any place within
the object type’s construct that utilizes SQL statements,
remember to refer to editioned views instead of schema table
directly.

21
 Additional References
This was a cursory look at some of the new technical features and
coding standards impact introduced in Release 12.2. There are many
great additional sources of documentation on Oracle’s Metalink site:

cle E-Business Suite Developer’s Guide Release 12.2 (Part No. E22961
loying Customizations in Oracle E-Business Suite Release 12.2
S Doc ID 1577661.1)
g the Online Patching Readiness Report in Oracle E-Business Suite
ase 12.2 (MOS Doc ID 1531121.1)
cle E-Business Suite Release 12.2: Online Patching FAQ
OS Doc ID 1583902.1)
22
CherryRoad-Oracle Offerings

Oracle Cloud
Applications (SaaS)

Enterprise Resource Planning

(ERP)
Enterprise Performance
Management (EPM)
For the 5 year in a
th
Human Capital Management
Oracle Business Intelligence Suite
row, Gartner has (HCM)
(OBIEE)
named Oracle Fusion Supply Chain Management (SCM)
Cloud ERP as a Leader
in its 2021 Magic CherryRoad Innovations
Quadrant for Cloud Oracle On-Premise
Core Financial Applications
Time & Attendance – TimeKeeper
Management Suites for
Midsize, Large and
PeopleSoft Suite Travel Calc Engine ( TCE)
Global Enterprises.
E-Business Suite (EBS) Historical Filing Cabinet (HFC)

23
Thank You

CherryRoad Technologies Inc.

6 Upper Pond Road Parsippany N J 07054
Phone : 973-402-7802
Email: [email protected]
Visit: www.cherryroad.com

Private and 24