Oracle Service Bus integration with Oracle Financials for message transformations
By srkastur on Jan 05, 2012
Oracle Service Bus and Oracle Financials Integration
Oracle Service Bus integration with Oracle Applications is a relatively straightforward process and this article highlights the steps involved in such an integration for message transformations in the core cash management modules.
Oracle Service Bus offers optimized connectivity to Oracle’s ERP applications and flexible choice of transports and protocols for connecting to custom or 3rd party back-office applications, databases and messaging systems.
Specifically, Oracle Service Bus provides a J2EE Connector Architecture (JCA) transport that interacts with Oracle’s E-Business Suite, letting the ERP applications and services participate in the service bus environment. In JCA proxy or business services, the JCA transport works in conjunction with a built-in JCA adapter framework and JCA-compliant adapters to interact with the ERP applications, as shown in the figure below:
This article describes a customer scenario involving end to end system Integration of customer ERP (Payables, Receivables and Payroll) to the Banking Partner through the SWIFT platform.
High Level Architecture diagram of flow:
Detailed steps for the above integration:
Generate Oracle ERP Web Services using SOA Suite and Oracle Applications adapter
To generate the required web services interfaces for the Process Payments Interface within the ACCOUNTS PAYABLE (AP) module,create a sample project within JDeveloper,in this case we have created the sample BankPayments.jws worskpace within the IDE.
Create a simple process and use the Oracle applications adapter to browse for the sample API's within the AP module of the Oracle ERP.
Below is a snapshot of the Oracle Applications adapter interface for Process Payments and Bank Statement interfaces within AP and Cash Management respectively.
Create Business Service for SOA Applications Adapter Web Service in OSB:
Create a Proxy Service to route requests to the Business Service:
The third party partner financial message designer tool provides the following capablities:
Integrated Design Environment
Customized financial message formats
Capability to define SWIFT network and code validation rules
Model custom message formats
Message catalog updated whenever SWIFT revises messages
Message formats supportedinclude ISO 8583, BAI2, EDI payments messages, FIX, FIXML, FpML
Seen below are snapshots of the transformation for the Payment messages within the designer:
Usage pattern for integrating the financial message designer with OSB:
Create a Cartridge – this is the basic unit of a project within the designer
Define financial Message format (e.g. SWIFT message)
Define Custom Message format (e.g. ERP processing results format or canonical in-house format)
Define transformation mappings between the two formats
Add persistence rules
Build output jar file (cartridge) for import into OSB
Use OSB to build message flows, using cartridge
Within OSB ,create a call out to the transformation packaged within the imported cartirdge as shown below:
solution outlined provides the advantage of using the existing
Financial modules within Oracle Applications and integrating the same
using SOA Suite and third party message transformation to comply with
requirements for integrating with banking and financial vendors in an
standards based manner with an extensible framework which takes into
account disparate needs of various entities, OUs and Banks.