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

Oracle Forms to APEX Migration for EBS: Effort Calculator

This calculator estimates the effort to rebuild EBS custom Oracle Forms, built from TEMPLATE.fmb and dependent on APPCORE and CUSTOM.pll, as Oracle APEX pages launched from the EBS navigator. It splits forms by complexity and adds the one-time integration setup.

Your numbers

Simple custom forms (single block, LOVs)

Hours per simple form

Medium forms (master-detail, flexfields, 5-15 triggers)

Hours per medium form

Complex forms (multiple canvases, APPFLDR folder blocks, EBS API calls)

Hours per complex form

One-time integration setup hours

EBS session validation, custom schema with grants, menu functions.

Forms with descriptive flexfields to replace

Each adds 12 hours.

Test multiplier

Hourly rate

$/h

Your results

Total hours with setup and testing

1,275 hrs

Build hours

940 hrs

Estimated cost

$121,125

Average hours per form

58 hrs

Setup share of total

7.8%

Effort defaults are field rules of thumb, not Oracle figures. Rebuild one form of each complexity first and replace the defaults with measured hours.

Save results:

Total hours vs number of medium forms

Sweeps Medium forms (master-detail, flexfields, 5-15 triggers) from 0 to 60, holding your other inputs fixed.

Send us your custom forms list

Share your forms inventory with trigger counts and we will classify them and return a reviewed APEX migration estimate.

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

Was this tool useful?

The integration pattern

Oracle's My Oracle Support whitepaper on extending Oracle E-Business Suite 12.1 and above with Oracle Application Express (Doc ID 1306563.1) describes the supported approach. APEX runs against the EBS database but parses as a separate custom schema, not APPS. That schema gets SELECT grants on the views it needs and calls EBS public APIs through wrapper packages, so it never writes to base tables directly. Users launch the APEX page from an EBS menu through a function of type SSWA jsp function, and APEX validates the existing EBS session (the ICX session) instead of asking for a separate login. Responsibility and function security therefore stay in EBS. The setup hours input covers this plumbing, done once.

How to classify your forms

Simple forms have one data block, a few LOVs and little trigger logic; APEX interactive grids or forms replace them quickly. Medium forms are master-detail with flexfields and a handful of WHEN-VALIDATE and PRE/POST triggers whose logic must move into PL/SQL packages. Complex forms use multiple canvases, folder blocks from the APPFLDR library, calls to EBS APIs and custom zoom logic in CUSTOM.pll; these need redesign, not translation. Descriptive flexfields have no direct APEX widget, so each form that uses one carries extra hours to build the segments and validation from the flexfield definitions.

Build hours = sum of count x hours per class + DFF forms x 12
Total = (build + setup) x test multiplier
Average per form = total / number of forms

Worked example

With the defaults: 10 simple forms x 16 = 160 h, 8 medium x 40 = 320 h, 4 complex x 100 = 400 h and 5 DFF forms x 12 = 60 h give 940 build hours. Adding 80 hours of setup and applying the 1.25 test multiplier gives 1,275 hours, about 121,000 at 95 per hour, or about 58 hours per form on average. The setup share is under 10 percent here, but for a pilot of two or three forms it can be a third of the total, so pilot cost per form always looks high.

Gotchas

Do not grant the APEX schema access to APPS itself; keep it to named views and wrapper packages so EBS security is not bypassed. On 12.2, any custom database objects in the EBS database must follow online patching rules, including editioning views for custom tables. Forms that rely on folder-level personal layouts, attachments or Oracle Forms personalizations need explicit replacements. Plan how APEX pages respect operating unit and MOAC access, typically by initialising the EBS context from the session.

Frequently Asked Questions

How do you integrate Oracle APEX with EBS R12?

Follow the approach in Doc ID 1306563.1: install APEX in the EBS database or a linked one, create a custom parsing schema with grants on the EBS objects it needs, register an EBS function of type SSWA jsp function that launches the APEX page, and validate the EBS ICX session in APEX for single sign-on.

Can Oracle Forms be converted to APEX automatically?

There is no automatic conversion that carries Forms trigger logic or EBS-specific libraries such as APPCORE and CUSTOM.pll into APEX. For EBS custom forms, treat it as a rebuild: move logic into PL/SQL packages and design new pages.

Should the APEX application parse as APPS?

No. Use a separate custom schema with only the grants it needs, and call EBS public APIs through wrapper packages. This limits damage from bugs, keeps audit clear and follows the separation the Oracle whitepaper recommends.

Are the effort numbers Oracle benchmarks?

No. They are field rules of thumb for planning. Build one simple, one medium and one complex form as a pilot, measure the hours including testing, and replace the defaults before committing a budget.

If you are modernising EBS screens anyway, we can also add a private AI assistant that answers questions over the same EBS data on your own servers.

Talk to an Expert Explore More Free Tools