Explain SOAP Web Services in Oracle EBS Integration Repository in Oracle Applications

37 / 60

Integrationintermediate

SOAP Web Services in Oracle EBS Integration Repository

Explain how EBS exposes SOAP web services through the Integration Repository for external system integration

The Oracle Integration Repository (iRep), embedded within EBS, is a searchable catalog of all interfaces available for integration — including PL/SQL APIs, open interfaces, concurrent programs, and Business Service Objects (BSOs) exposed as SOAP web services. Before OIC and modern REST-based approaches became dominant, SOAP-based web services (exposed through EBS's Web Services Assembler or, in R12, natively through iRep) were the primary supported integration mechanism for external systems needing to invoke EBS business logic synchronously.

SOAP web services via iRep are like a hotel's international phone operator service: guests (external systems) speaking a standardized protocol (SOAP/XML) can request services (business logic) through the operator without needing to know the hotel's internal room-to-room extension system (raw PL/SQL API calls).

Key Concepts

A Business Service Object wraps a PL/SQL public API (like a specific procedure in AP_INVOICES_PKG) in a WSDL-described SOAP interface, allowing external systems (even non-Oracle ones) to call EBS business logic using standard SOAP/XML messaging, without needing direct database connectivity or PL/SQL knowledge. This was the standard approach for point-to-point integrations before iPaaS platforms like OIC or SOA Suite became the norm for orchestration.

AP_INVOICES_PKG

iRep also serves an important discovery and governance purpose beyond just SOAP — it documents every registered interface (including which ones are recommended integration points versus internal-only), helping technical teams identify the officially supported way to interact with a given business process rather than resorting to unsupported direct table access.

Interviewers occasionally ask legacy-integration-focused candidates to explain the difference between exposing a PL/SQL API directly as a SOAP service (via BSO) versus wrapping it inside a broader OIC or SOA Suite orchestration, and when each approach remains appropriate (SOAP BSOs still exist in many long-running EBS environments that haven't modernized their integration layer).