Escolar Documentos
Profissional Documentos
Cultura Documentos
Applications
Overview
One of the most critical technical work streams associated with implementing Oracle Fusion
HCM is building and deploying new Inbound and Outbound interfaces with the system.
Fusion Applications support both inbound and outbound integration; however different tools
are available to build each kind of integration. Some of the considerations while designing
interfaces are
Interface scheduling
This document outlines details of above considerations and proven approaches to build
inbound and outbound integration in Fusion.
Outbound Integration
Outbound integration in Fusion is based on following Oracle delivered tools
HCM Extract
BI Publisher
Oracle Transaction Business Intelligence (OTBI)
Following table should be used to decide approach for the outbound integration. The
approach below is applicable to HR, Benefits and Payroll interfaces.
Output Type
The delivered tool can be used to generate output in different formats XML, Excel,
CSV, Flat Files
Approach using HCM Extract and BI Publisher
Using Fusion BI Publisher for developing interfaces and reports involves these steps -
Inbound Integration
Integration using Oracle File-Based Loader (FBL)
Oracle File Based Loader (FBL) tool has been released by Oracle in Release 4 of Fusion HCM
Applications and further refined in current release. The interface design using File Based
Loader (FBL) is based below assumptions
All foundation data should be converted using File Based loader tool
The integration is based on Comma Separated File (CSV) in File Based Loader (FBL)
format
The interface cannot be scheduled, and must be run manually
Once FBL data file is generated, the batch is created and processed
Oracle Fusion Applications exposes many web services which can be used to build inbound
integration.
Note: Fusion Applications Releases 7 is expected to expose web services that are available
for external use. The list of available Web Services and Business Events are published in
Oracle Enterprise Repository (OER). Though Oracle Fusion Applications are designed using
the Service-Oriented Architecture (SOA) principles, not all services are necessarily suited for
integration purposes. Those services that are tagged in OER with the EXTERNAL keyword
and have Compatibility equal to Supported Backward Compatibility Assured should be
used for Interface and Integration purposes.
Fusion Applications exposed web services can be consumed by any existing middleware
platform that enterprise is using (i.e. TIBCO, Fusion Middleware)
In this approach java program is used to call web services. This approach needs a third party
scheduler to schedule the interface
Interface Scheduling
Interfaces can be scheduled to run as per the requirement Hourly, Daily, Weekly etc.
Before scheduling interfaces, following steps should be performed
Note: Currently, recurring schedule is not available for HCM extract based interfaces