OracleFree calculatorPDF, Excel, Word exportOracle E-Business SuiteAll Oracle E-Business Suite tools

Oracle EBS 12.2 Upgrade: Custom Code Remediation Effort Calculator

This calculator estimates the developer hours, cost and elapsed weeks to make EBS custom code compliant with 12.2 online patching and to retest it. Every hours-per-object default is editable so you can replace the rules of thumb with rates from a pilot batch.

Your numbers

Custom tables needing editioning view (AD_ZD_TABLE.UPGRADE)

Hours per custom table

Custom PL/SQL packages

Hours per package

Readiness report violations (ADZDPSUM / ADZDPMAN / ADZDPAUT)

Hours per violation

Custom forms

Hours per form

Custom reports (Oracle Reports / XML Publisher)

Hours per report

OAF personalizations / extensions

Hours per OAF item

Custom concurrent programs (retest)

Hours per program

Integrations / interfaces

Hours per integration

Test cycle multiplier

Hourly rate

$/h

Developers on the team

Your results

Total hours with test cycles

1,125 hrs

Base remediation hours

865 hrs

Estimated cost

$106,828

Elapsed weeks for the team

11.7 weeks

Assumes 32 productive hours per developer per week.

Database-tier share (tables, packages, violations)

37%

Hours per object are field rules of thumb for planning, not Oracle figures. Replace them with averages from a pilot batch of your own objects.

Save results:

Total hours vs number of custom PL/SQL packages

Sweeps Custom PL/SQL packages from 0 to 1000, holding your other inputs fixed.

Send us your readiness report summary

Share your ADZDPSUM and ADZDPMAN output counts and we will return a reviewed remediation estimate by object type.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

What changes for custom code in 12.2

The core difference between EBS 12.1 and 12.2 is online patching: 12.2 uses Oracle Database Edition-Based Redefinition plus a dual application file system so patches are applied to a patch edition while users stay on the run edition. Custom code must follow the same rules as Oracle code. Code objects such as packages, views, synonyms and triggers are editioned. Tables are not editioned, so each custom table needs an editioning view and an APPS synonym, which AD_ZD_TABLE.UPGRADE generates; after later structure changes you run AD_ZD_TABLE.PATCH. Code must reference the editioning view or synonym, not the base table, and must not use DDL patterns that break under editioning. The Oracle developer guide for 12.2 lists these standards in full.

How to get the counts

Run the Online Patching Readiness Report described in My Oracle Support Doc ID 1531121.1 on your 12.1.3 system before the upgrade. ADZDPSUM.sql gives the summary of schemas and objects, ADZDPMAN.sql lists violations that need manual fixes, and ADZDPAUT.sql lists issues that the enablement process fixes automatically. After enablement, run the Global Standards Compliance Checker, ADZDDBCC.sql, to find remaining violations. Count custom tables from your custom schemas, packages from DBA_OBJECTS for those schemas, forms and reports from your code repository, and concurrent programs from the FND definitions with your custom application short name.

Manual violations (ADZDPMAN) are the ones that drive the violations line
Automatic fixes (ADZDPAUT) still need retesting, so do not count them as zero
Register custom schemas with EBS so they are edition-enabled

Worked example

With the defaults: 40 tables x 2 = 80 h, 200 packages x 0.75 = 150 h, 60 violations x 1.5 = 90 h, 30 forms x 3 = 90 h, 80 reports x 1.5 = 120 h, 25 OAF items x 4 = 100 h, 150 programs x 0.5 = 75 h and 20 integrations x 8 = 160 h. The base is 865 hours; with the 1.3 test multiplier the total is about 1,125 hours, roughly 107,000 at 95 per hour. A team of three developers at 32 productive hours a week needs about 11.7 weeks. The chart shows how package count moves the total; for estates with very large PL/SQL libraries, the database tier dominates.

Common mistakes

Teams often count only the objects listed in the readiness report and forget that every custom form, report and OAF extension must be retested on the 12.2 technology stack. Other mistakes: running AD_ZD_TABLE.UPGRADE but leaving code that still selects from the base table owner; leaving custom objects in the APPS schema without following the editioning rules; skipping the Global Standards Compliance Checker after enablement; and deploying custom code outside adop in 12.2, so the next fs_clone or cutover loses the change.

Frequently Asked Questions

What is the difference between Oracle EBS 12.1 and 12.2?

12.2 adds online patching using Edition-Based Redefinition and a dual application file system (fs1 and fs2 plus fs_ne), patched with adop instead of adpatch. It also moves the application tier to WebLogic Server. For custom code this means editioning rules, editioning views on custom tables and deploying changes through patch cycles.

What does AD_ZD_TABLE.UPGRADE do?

It generates an editioning view and the corresponding APPS synonym for a custom table so the table can be used safely under online patching. Run it after creating a custom table; after later column changes, run AD_ZD_TABLE.PATCH to regenerate the editioning view.

Which readiness reports should we run before the 12.2 upgrade?

The Online Patching Readiness Report in Doc ID 1531121.1: ADZDPSUM.sql for the summary, ADZDPMAN.sql for violations needing manual fixes and ADZDPAUT.sql for those fixed automatically. After Online Patching Enablement, run ADZDDBCC.sql, the Global Standards Compliance Checker, and clear its findings.

Are the hours-per-object values Oracle numbers?

No. They are field rules of thumb for planning. Fix a sample of 10 to 20 objects of each type early in the project, measure the real average including retest, and replace the defaults. Complex integrations and OAF extensions vary the most.

If you want an AI assistant that reads your EBS custom code inventory and readiness reports on your own servers and drafts remediation notes, we can set that up.

Talk to an Expert Explore More Free Tools