Fixed-price pilot
OAF-to-APEX Modernization
A low-risk way to start modernizing: we rebuild one live OAF page in Oracle APEX for a fixed fee, integrated cleanly with EBS, so you can evaluate the approach before committing to a program.
Why it matters
The problem it solves
OAF and Oracle Forms customizations are increasingly expensive to own: the talent pool is shrinking, framework internals are fragile across upgrades, and every change requires a specialist who understands both EBS and OA Framework.
Rebuilding these surfaces in Oracle APEX cuts the maintenance tax. Any competent APEX developer can own the result, while keeping the EBS integration that made the customization valuable in the first place.
Scope
What's included
- Discovery of the target OAF page, its controllers, VO/AM/EO chain and embedded business rules
- APEX rebuild with equivalent behaviour and cleaner data access
- EBS integration via standard APIs, MOAC and org context
- Security parity with the original page
- Parallel-run plan and cutover checklist
- Handover documentation for your internal team
Investment
Pricing
Pilot
from $1,500
one OAF page → production-ready APEX page. Larger programs are quoted per scope.
What the pilot covers
- One OAF page with a single primary function
- Standard EBS data access through existing views and public APIs
- Standard security: responsibility, function security, org context and MOAC
- Parallel run against production data, then cutover of that page
Not included in the pilot price
- Multi-page or multi-step flows
- Custom Java or framework-level logic beyond the page itself
- New integrations to third party systems
- Data migration or data remediation
Complex pages are quoted after a short assessment.
Delivery
How we work
Step 1
Discovery
Walk the OAF page, its controllers, VO/AM/EO chain, and the business rules embedded in it.
Step 2
Mapping
Map the OAF surface to an APEX equivalent: pages, regions, processes, security model.
Step 3
Rebuild in APEX
Ship the page in APEX with matching behaviour, cleaner data access, and modern UX.
Step 4
EBS integration
Wire it back into EBS the right way: standard APIs, MOAC, org context, and security.
Step 5
Cutover
Parallel run, validate against production data, retire the OAF customization.
Answers
FAQ
Why start with just one page?
Because it's honest. You get to see how we work, on your real environment, at a fixed cost, before scaling to a broader modernization program.
Will the APEX page still respect EBS security and MOAC?
Yes. We integrate through standard EBS APIs and set org context correctly, so the rebuilt page behaves the same way as a native EBS surface from a security and multi-org perspective.
What happens after the pilot?
Most clients move into a retainer to modernize additional pages incrementally. There is no obligation. The pilot stands on its own.
What if our OAF page is more complex than that?
We do a short assessment first and quote it honestly. We would rather tell you the real number up front than discover it halfway through and burn your budget on surprises.