eAppSys
The Mille, 1000 Great West

info@eappsys.com

Contact Title
Blog
Contact Title
Locations
Free Consultation
Free Consultation

Oracle Forms · Custom Bolt-Ons · Discoverer · Reports — Rebuilt on APEX

Moving EBS Custom Modules
to Oracle APEX

Legacy EBS custom applications can become major blockers during an Oracle Fusion Cloud migration. eAppSys assesses each customisation to determine whether it should be retired, configured, or rebuilt. We modernise Oracle Forms, bolt-ons, workflows, data loaders, Discoverer workbooks, and custom reports on Oracle APEX — preserving critical business functionality while creating secure, browser-native applications designed for seamless Oracle Fusion Cloud integration.

Book a Free Consultation
200+
Oracle consultants
15+
Years Oracle expertise
100%
Oracle focused
UK & India
Delivery centres

Home › Services › Oracle Fusion Cloud › Moving EBS Custom Modules to APEX

eAppSys — Oracle EBS Services

Moving EBS Custom Modules to Oracle APEX — Rebuild, Preserve, Future-Proof

As eappsys.com explains: “Over the years, businesses have built numerous custom apps and extensions around EBS to address gaps, streamline operations, and meet industry-specific needs. As they move to Oracle Fusion — a SaaS platform that promotes configuration over customisation — these legacy solutions often become blockers unless modernised in parallel.” eAppSys guides enterprises through the process of identifying, rebuilding, and integrating their EBS-era custom applications on Oracle APEX — the rapid, secure, upgrade-friendly platform that is ideal for portals, mobile apps, and workflow apps around EBS and Fusion. Critically, APEX applications built by eAppSys are not just EBS replacements — they are designed from the outset to integrate with Oracle Fusion Cloud, so when your organisation completes its migration, every custom module continues to work seamlessly, connected to Fusion via REST APIs and Oracle Integration Cloud (OIC).
“Oracle APEX has become the preferred platform for implementing Oracle E-Business Suite (EBS) extensions. Oracle APEX is a low-code application development platform for the Oracle database — combining the qualities of a personal database (productivity, ease of use, and flexibility) with the qualities of an enterprise database (security, integrity, performance, scalability, availability, and built for the web).”

eAppSys’s Custom App Triage — What Gets Retired, Configured, or Rebuilt

As eappsys.com describes the Custom App Discovery & Assessment: “We catalogue existing EBS customisations and map them against available Fusion functionality to determine: What can be retired; What can be configured within Fusion; What should be rebuilt in APEX or VBCS.”
eAppSys’s Custom App Triage — What Gets Retired, Configured, or Rebuilt

As eappsys.com describes the Custom App Discovery & Assessment: “We catalogue existing EBS customisations and map them against available Fusion functionality to determine: What can be retired; What can be configured within Fusion; What should be rebuilt in APEX or VBCS.”

OutcomeCriteriaExamples
Retire Fusion covers the requirement natively and better than the custom app Custom approval workflows replaced by Fusion’s native BPM approvals; custom expense forms replaced by Fusion Expenses
Configure in Fusion Requirement can be met by Fusion configuration — no rebuild needed Custom EBS finance reports replaced by OTBI/BIP in Fusion; custom HR screens replaced by Fusion HCM self-service
Rebuild in APEX Genuine bespoke requirement; data-centric; needs Oracle database integration — and must integrate with Oracle Fusion Cloud post-migration Custom billing module; sub-contractor management; reconciliation tools; data loaders; internal approval portals with complex logic
Rebuild in VBCS Needs tight integration with Fusion UI; extends Fusion workflows or screens Custom Fusion extensions adding new screens; supplier or employee self-service portals embedded in Fusion pages

Why EBS Custom Applications Become Blockers in Fusion

As Oracle’s own documentation confirms: “Oracle Fusion discourages deep customisations within its core environment. It provides a modern, API-first architecture designed for scalability and continuous updates. Custom forms and workflows can’t be ported directly and must be rebuilt. Point-to-point integrations must be redesigned using REST APIs or middleware tools like Oracle Integration Cloud.”

Legacy EBS Custom Apps — The Problems

  • Built on Oracle Forms — a technology Oracle is sunsetting; no browser support
  • Depend on direct EBS schema database access — not possible in Oracle Fusion SaaS
  • Point-to-point integrations that cannot be ported to Fusion’s API-first architecture
  • OAF and ADF customisations inside the EBS core — expensive to maintain, break on upgrade
  • Custom PL/SQL and database triggers deeply embedded in EBS tables
  • Between 60–80% of EBS customers have built these — in complex sectors, even higher

Rebuilt on APEX — The Solution

  • Browser-native, mobile-ready applications — no client-side installation needed
  • Connects to Oracle databases via secure REST APIs — compatible with both EBS and Fusion
  • Lives outside the EBS/Fusion core — unaffected by Oracle quarterly updates
  • Rapid, low-code development — complex forms rebuilt in days, not months
  • Full audit trail, role-based security, and workflow built into APEX natively
  • Integrates with OIC, Fusion REST APIs, and existing EBS back-end data seamlessly

Book a Free Consultation

Talk to our experts today

Oracle E-Business Suite

Accreditation & Recognition

ISO 9001:2015
BS EN ISO/IEC 27001:2022
Cyber Essentials Plus
ICO Certified
Download Brochure

How APEX Modules Integrate with Oracle Fusion Cloud

Rebuilding EBS custom modules on APEX is not just about replacing Oracle Forms — it is about ensuring those modules continue to deliver value after you move to Oracle Fusion Cloud. eAppSys designs every APEX application with a forward-looking integration architecture so nothing needs to be rebuilt again when your Fusion go-live happens.

Oracle Integration Cloud (OIC)

For complex data flows, eAppSys uses OIC as integration middleware. As oracle.com confirms: “Oracle Integration connects applications, data, and AI services across on-premises and cloud environments… Use the same application adapters that seamlessly connect Oracle Fusion SaaS apps.” This includes a dedicated EBS adapter for OIC — moving EBS integrations to OCI as-is.

During EBS → Fusion Migration

eAppSys updates APEX integration layers to call Oracle Fusion REST APIs alongside EBS — ensuring business users experience no disruption as data progressively moves to Fusion. Oracle REST APIs · OIC · Dual-source queries

Post-Fusion Go-Live

APEX applications connect to Oracle Fusion Cloud via the pre-configured Fusion REST API integration in APEX — OAuth SSO, REST Data Sources for all Fusion pillars (ERP, HCM, SCM), and bi-directional data integration in real time. Fusion REST APIs · OIC · Oracle APEX on OCI

Oracle Fusion REST APIs

Oracle Fusion Cloud exposes REST APIs for all business objects across ERP, HCM, SCM, and CX. As Oracle’s APEX documentation confirms: “Extending Oracle Fusion Applications with Oracle APEX lets you tailor the system to meet unique business needs not covered by the standard suite.” eAppSys builds APEX applications using Oracle’s pre-configured Fusion REST API Catalog — covering all Fusion pillars out of the box.

Oracle Integration Cloud (OIC)

For complex data flows, eAppSys uses OIC as integration middleware. As oracle.com confirms: “Oracle Integration connects applications, data, and AI services across on-premises and cloud environments… Use the same application adapters that seamlessly connect Oracle Fusion SaaS apps.” This includes a dedicated EBS adapter for OIC — moving EBS integrations to OCI as-is.

Security & Access Control

APEX applications built by eAppSys inherit Fusion’s role-based access model via API authentication — ensuring that the same security rules that govern Fusion also govern what users see and do in APEX custom modules.

Real-Time & Batch

APEX custom modules can both call Fusion APIs in real time (for live data queries and transactional writes) and receive data from Fusion via OIC batch feeds — supporting both operational and reporting use cases.

What eAppSys Delivers

Custom App Discovery & Assessment

eAppSys catalogues all EBS customisations and maps them against Fusion functionality — determining what to retire, configure, or rebuild, so APEX investment is focused where it delivers the most value.

APEX Architecture & Setup

eAppSys establishes secure, scalable APEX environments that integrate with both EBS (during migration) and Oracle Fusion Cloud (post-migration) — using REST APIs rather than direct database connections.

Oracle Forms Replacement

eAppSys rebuilds Oracle Forms-based custom applications as browser-native APEX equivalents — preserving all business logic, data access, and user workflows without Oracle Forms client installation.

Custom Bolt-On Rebuild

eAppSys rebuilds complex EBS bolt-on modules (Customer Billing, Sub-Contractor, Plant, Project tools) on APEX — preserving bespoke business logic outside the EBS/Fusion core.

Approval Workflow Applications

eAppSys rebuilds multi-step approval processes on APEX — with role-based access, email notifications, audit trail, and configurable routing logic.

Data Loaders & Reconciliation Tools

eAppSys rebuilds custom data loading, batch processing, and reconciliation tools as APEX applications — faster, more maintainable, and with built-in validation and error reporting.

Discoverer & Custom Report Replacement

eAppSys replaces Discoverer workbooks and custom Oracle Reports with APEX dashboards and interactive reports — connected directly to EBS or Fusion data sources.

EBS & Fusion Integration

eAppSys connects APEX applications to EBS via database connections and to Oracle Fusion via REST APIs and OIC — ensuring APEX works across both platforms throughout and after migration.

eAppSys’s Delivery Process

01

Discover

eAppSys catalogues all EBS customisations and assesses each against the triage framework

02

Design

eAppSys designs the APEX/VBCS architecture and establishes the integration approach

03

Build

Implement and configure the platform to your specific requirements

04

Test & Deploy

eAppSys tests all rebuilt applications and deploys alongside the EBS or Fusion migration

Why Our Customers Choose eAppSys

Deep EBS and APEX Expertise

eAppSys has delivered APEX development alongside EBS implementations and migrations across construction, healthcare, manufacturing, and public sector — understanding both the EBS data model and the APEX development platform from the inside.

Structured Triage — Not Rebuild Everything

eAppSys doesn’t rebuild every custom module — eAppSys first determines what to retire, what Fusion covers natively, and what genuinely needs rebuilding in APEX, so the programme delivers the right scope at the right cost.

Works During and After Migration

APEX applications built by eAppSys work against EBS during migration and switch to Fusion REST APIs post-migration — ensuring no disruption to business users throughout the transition.

Upgrade-Safe by Design

eAppSys builds all APEX applications outside the EBS/Fusion core — unaffected by Oracle quarterly updates to the Fusion application layer, with clean upgrade paths built in from day one.
Your EBS custom applications represent years of accumulated business logic — the bespoke capabilities that differentiate your organisation. eAppSys preserves every one of them, rebuilt on Oracle APEX: faster to maintain, upgrade-safe, browser-native, and fully integrated with Oracle Fusion Cloud. When you go live on Fusion, your custom modules go live with you — connected, operational, and seamlessly part of your Oracle Cloud environment.
Moving EBS Custom Modules to APEX

Frequently Asked Questions

Common questions before engaging eAppSys for EBS custom module migration to APEX.

Why do EBS custom modules need to be moved to APEX?
As eappsys.com explains: ‘As they move to Oracle Fusion — a SaaS platform that promotes configuration over customisation — these legacy solutions often become blockers unless modernised in parallel.’ Specifically: Oracle Fusion does not allow direct database access; Oracle Forms cannot be ported directly; point-to-point integrations must be redesigned using REST APIs; and security roles differ significantly. APEX solves this — it is browser-native, integrates with both EBS and Fusion via secure APIs, and preserves critical functionality outside the EBS/Fusion core, maintaining clean upgrade paths.
eAppSys describes APEX as ‘ideal for rebuilding operational apps such as data loaders, reconciliations, approval forms, and internal reporting tools.’ eAppSys has also rebuilt complex bolt-ons: as the EBS R12 Harmonisation case study on eappsys.com confirms, eAppSys rebuilt Customer Billing, Sub-Contractor, and Plant Solution modules for a global construction company. The eAppSys EBS page also notes the technical stack replaced: Oracle Forms, Reports, OAF, ADF, PL/SQL — all of which can be superseded by APEX applications.
eAppSys’s Custom App Discovery & Assessment triage, as described on eappsys.com: ‘We catalogue existing EBS customisations and map them against available Fusion functionality to determine: What can be retired; What can be configured within Fusion; What should be rebuilt in APEX or VBCS.’ This ensures APEX investment is focused only where genuine bespoke requirements exist that Fusion cannot cover natively. Some modules are retired. Some are configured in Fusion. Only those with real bespoke requirements are rebuilt in APEX or VBCS.
Yes. As eappsys.com states: ‘APEX is ideal for rebuilding operational apps… It allows organisations to preserve critical functionality without embedding it in the Fusion core — maintaining clean upgrade paths.’ eAppSys builds APEX applications outside the EBS/Fusion core, connecting to EBS via database and to Fusion via REST APIs and OIC. This means they are unaffected by Oracle quarterly updates to the Fusion application layer and continue to operate throughout and after migration.
As eappsys.com explains: APEX is ‘rapid, secure, and upgrade-friendly — ideal for portals, mobile apps, and workflow apps around EBS’ — best for data-centric applications, data loaders, reconciliations, approval forms, and dashboards. VBCS is ‘tailored for building SaaS-integrated web and mobile applications, particularly where tight integration with Oracle Fusion is essential’ — best for extending Fusion screens and workflows. eAppSys ‘guides enterprises through the process of identifying, rebuilding, and integrating their EBS-era custom applications using the most appropriate tools for their use case — whether that’s APEX, VBCS, or a combination of both.’
eAppSys Oracle Cloud Services FAQs
Chat