Académique Documents
Professionnel Documents
Culture Documents
com
Oct 2015
APPL_TOP APPL_TOP
Synchronization Managed Automatically
COMMON_TOP COMMON_TOP
PATCH_TOP
LOGS
Development Standards
Patching Procedures
– 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
A new schema APPS_NE (APPS Non-Editioned) introduced in R12.2 to hold potentially editioned objects
for which these dependencies would not be removed. Online patching would not be able to patch these
objects
R12.1.x
R12.2.x
APPS – Synonym MOAC/VPD Editioning View PO – Base table
PO_HEADERS_ALL PO_HEADERS_ALL# PO_HEADERS_ALL
PO_HEADERS X
Virtual Private Database (VPD) Policy must be on the Editioning View or Table
Synonym, not the base table
You must use the Editioning View in order to get the correct column
representation, that is consistent for your Edition
A crossedition trigger propagates data changes made by the old edition into the
new edition’s columns, or (in hot-rollover) vice-versa
This provides the filtered representation of the Editioning View to ensure you get a
consistent representation of the data.
If the application upgrade will change only views, synonyms, and PL/SQL objects, then the
edition alone is sufficient to allow these changes to be made while the application remains
on line. This type of change is common when, for example, new presentations of data or
new workflows are required.
If changes to table data or structure are restricted to only those tables that are not
changed via the ordinary end-user interfaces, then the edition together with the editioning
view are sufficient to allow these changes to be made while the application remains on line.
Tables whose data parameterizes the user interface layout or workflows meet this
condition. So do tables that hold the catalog of wares for a shopping application.
If changes to table data or structure are required for those tables that are changed
routinely by the end-user, then the edition, the editioning view, and the crossedition trigger
must be used in concert to allow these changes to be made while the application remains
on line.
Patch Patch
Patch Patch
Customization Guidance
Application In Release 12.2, you should use adsplice to register your application in order to ensure that the application is
set up for online patching. Do not use the Applications window to register applications in this release. Do not
use the Applications window to register applications in this release.
Customization Guidance
Effectively Editioned Database Objects
Custom Table - New Step 1: Create the initial table definition in your development database. This step includes creation of any required
indexes, storage properties, and so on.
Step 2: Upgrade the table for Online Patching using the AD_ZD_TABLE.UPGRADE procedure. This will generate an
Editioning View (EV) for the table and then create an APPS synonym that points to the Editioning View. Table is
now ready to use from APPS schema. Generated EV name would be same as table and suffix by “#”.
Step 3: Extract the table definition from your development database using the xdfgen.pl utility. Due to a database
requirement you must first insert at least one row into the table before extraction will work.
Step 4: Create the patch.
Patch Files:
fnd/patch/115/xdf/xyz_user_service.xdf
When the patch is applied, XDF will create the table and index, and will automatically call the
AD_ZD_TABLE.UPGRADE procedure to generate the editioning view and APPS table synonym.
New Logical Column to Step 1: Create new column in table by using alter command. When adding Not Null column it is
recommended to choose default value.
Table
Step 2: Regenerate Editioning View (EV) using AD_ZD_TABLE.PATCH upgrade the table for Online
Patching using the AD_ZD_TABLE. The PATCH procedure looks at the physical table columns and
then generates the editioning view which presents the logical columns for that table.
Step 3: Extract the table definition from your development database using the xdfgen.pl utility.
Step 4: Create the patch.
Patch Files:
fnd/patch/115/xdf/xyz_user_service.xdf
Manual apply phase actions for the file system:
cp fnd/patch/115/xdf/* $FND_TOP/patch/115/xdf
New Index Step 1: Create new index on selected table by using Create Index command
Step 2: Extract the table definition from your development database using the xdfgen.pl utility.
Step 3: Create the patch.
Patch Files:
fnd/patch/115/xdf/xyz_user_service.xdf
Manual apply phase actions for the file system:
cp fnd/patch/115/xdf/* $FND_TOP/patch/115/xdf
Manual apply phase actions for the database:
$FND_TOP/patch/115/xdf/xyz_user_service.xdf <apps_user>/<apps_password>
AD_ZD_TABLE.UPGRADE This will generate an Editioning View (EV) for the table and then
create an APPS synonym that points to the Editioning View. E.g.
exec ad_zd_table.upgrade('APPLSYS', 'XYZ_USER_SERVICE')
xdfgen.pl utility This produces a file called 'xyz_user_service.xdf' that contains
the definition of the table along with any related indexes,
sequences, and policies
perl xdfgen.pl
<apps_user>/<apps_password>@<DB_Instance_Name>
XYZ_USER_SERVICE
AD_ZD_TABLE.PATCH Whenever you directly alter the structure of a table, you must
call the AD_ZD_TABLE.PATCH procedure. The PATCH procedure
looks at the physical table columns and then generates the
editioning view which presents the logical columns for that
table. The PATCH procedure is called automatically when
applying table structure changes using XDF or ODF.
27
27 11/17/2015
11/16/2015 ©
© KPIT
KPIT Technologies
Technologies Limited
Limited