Académique Documents
Professionnel Documents
Culture Documents
CONTENTS
Introduction ...................................................................................................................................................................2
Inbound Integration.......................................................................................................................................................2
HCM File-Based Loader .............................................................................................................................................2
HCM Spreadsheet Loader..........................................................................................................................................2
Payroll Batch Loader .................................................................................................................................................3
HCM Data Loader ......................................................................................................................................................3
V2 SOAP services .......................................................................................................................................................3
REST Services .............................................................................................................................................................4
Outbound Integration....................................................................................................................................................4
HCM Extract ..............................................................................................................................................................4
ATOM Feeds ..............................................................................................................................................................5
BI Publisher and Services...........................................................................................................................................5
BI Agent .....................................................................................................................................................................5
File Security ...................................................................................................................................................................6
R7 and Early R8..........................................................................................................................................................6
Advanced Data Security ............................................................................................................................................6
HCM Connect V1 .......................................................................................................................................................6
ROADMAP ......................................................................................................................................................................7
Purpose:
This document provides an overview of features and enhancements included in Oracle Fusion Applications 11gR1 Release 11.1.1.7.0 and
applicable updates. It is intended solely to help you assess the business benefits of upgrading your existing Oracle Products to this release, or
implementing completely new Oracle developed products, and planning your I.T. Projects.
Disclaimer:
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access
to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement or other
applicable contract with Oracle, with which you agree to comply. This document and information contained herein may not be disclosed,
copied, reproduced or distributed to anyone outside Oracle without Oracles prior written consent. This document is not part of your license
agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.
This document is intended to outline our general product direction. It is intended for informational purposes only and solely to assist you in
planning for the implementation and upgrade of the product features described. Release information contained in this document is not a firm
development plan. Release information published here should not be used as the basis for customer delivery commitments, as part of
marketing efforts, or during contract negotiations. This is not a commitment to deliver any material, code, or functionality, and should not be
relied upon in making purchasing decisions. The development, release, and timing of any features or functionality, and inclusion or not thereof
in the commercially available version of the Software, if any, is subject to change at any time and is always at Oracles sole discretion. This
document is not considered part of the applicable program documentation.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking
significant destabilization of the code.
INTRODUCTION
This document provides a summary of the tools available in Fusion HCM and the techstack that allow
implementers to develop integrations into and out of Fusion HCM. In addition there is a timeline showing the
targeted releases by which new integration functionality will be made available.
INBOUND INTEGRATION
The inbound integration into Fusion HCM can be handled using either the bulk loading tools such as File Based
Loader, Spreadsheet Loader, Payroll Batch Loader and in the future HCM Data Loader. Additionally specific
integrations can be done in future by a set of REST services that will also be available from R9. All of these tools
have the capability to be automated from outside of Fusion.
HCM Spreadsheet Data Loader generates spreadsheets dynamically for several Oracle Fusion HCM business
objects. Each spreadsheet contains columns for the object attributes, identifies required values, and uses lists of
values (LOVs) for many attributes to aid completion. Once you have populated the spreadsheet with your data, the
upload, validation, and correction of the data are straightforward processes.
HCM Spreadsheet Data Loader is most suitable for loading setup data, nonhierarchical data and simple hierarchical
data, small-to-medium volumes of data.
HCM Spreadsheet Loader requires manual intervention meaning that it does not lend itself well to automated
integration. However it does lend itself to ad-hoc end user data loading.
V2 SOAP SERVICES
In R7 a set of external, message protected SOAP based services was developed as an evolution of the original V1
services that were delivered as internal only. The V2 services as they are known are based on a framework that
allows them to be used independently but also to underpin the future HCM Data Loader tool
Hence the SOAP Services developed in R7 are under controlled release and are only available to specific partners. If
customers have compelling use cases that justify the use of a V2 SOAP Service then development management will
determine whether to approve their use on an exception basis.
REST SERVICES
From R9 HCM will begin to deliver a set of REST services and these will be the primary mechanism for interacting
with Fusion on an ad-hoc / real-time basis.
The REST services have the benefits of standardization and discoverability and in particular they lend themselves to
integration on mobile apps more readily than SOAP.
The initial set of REST resources being delivered in R9 will focus on the Employee allowing the management of the
employee lifecycle, maintenance of the employee details, roles and responsibilities. They will also allow the extract
of individual employee details providing real-time outbound capability.
OUTBOUND INTEGRATION
Data can be extracted out of Fusion in bulk using the HCM Extract tool and also via BI Publisher both of which have
services that allow the processes to be automated from outside Fusion.
In R9 a set of ATOM feeds will be delivered that allow a consumer to be notified when certain business events
occur in Fusion. This will introduce the ability for Fusion to trigger processing in downstream systems outside of
Fusion.
HCM EXTRACT
The primary tool for bulk retrieval of data from Fusion is HCM Extract which is a flexible tool for generating data
files and reports.
HCM Extract has a dedicated UI for specifying the records and attributes to be extracted. The set of records to be
extracted can be controlled using complex selection criteria. Data elements in an HCM Extract are defined using
fast formula database items and rules.
The output of an extract can optionally be generated in the following formats by leveraging the built-in integration
with BI Publisher: CSV, XML, Excel, HTML, RTF and PDF.
HCM Extracts can be invoked from the UI in the Data Exchange workarea or from the Checklists UI in the Payroll
workarea. Alternatively they can be invoked using the FlowActionsService from outside of Fusion allowing the
outbound extract to be automated as part of an overall integration flow.
Once an HCM Extract has completed the raw hierarchical XML can be downloaded using the
PayrollProcessingActionService. Alternatively the formatted BI report (CSV etc) can be downloaded using the BI
ScheduleService. In both cases the output is streamed in a byte array and so any orchestration mechanism would
have to be able to handle this possibly via wrapper code.
It is also possible to generate an HCM Extract with no output format specified at the design stage, and then to
subsequently generate a BI report output based on the specific extract using BI Publisher or the BI ReportService.
This technique uses a dedicated BI Data Model that is delivered to interface with the HCM Extract XML that is
generated.
ATOM FEEDS
In order to provide notifications of events that have occurred in the Fusion the ability to generate ATOM feeds has
been added in R9. These ATOM feeds will be tightly integrated with the REST resources described above.
When an event occurs in the Fusion system the corresponding ATOM feed will be pushed to the ATOM server. The
feed will contain details of the REST resource on which the event occurred. Subscribers will be able to consume the
ATOM feeds allowing them to use the REST resource to call back to Fusion to retrieve additional information about
the resource, and allowing them to orchestrate downstream processing based on the Fusion event.
Examples of the ATOM feeds being delivered in the first instance are New Hire, Employee Terminated, Employee
Basic Info Changed, Employee Contact Info Changed.
BI AGENT
A BI Agent is a mechanism for using a BI Analysis report or KPI to determine if certain conditions have been
satisfied and to invoke one or more actions if such conditions have occurred. An action can include calling out to
an external service so using this technique it is possible to monitor the Fusion instance and to invoke downstream
processing when certain conditions are detected.
The BI Agent is executed on a schedule basis i.e. it is not real-time detection of events, however in theory the
schedule could be set up to monitor Fusion on a frequent basis.
FILE SECURITY
A number of the integration tools listed above rely on data files being moved to and from Fusion. Many of these
files contain sensitive information and customers therefore need to be able to ensure that the contents are
protected from unauthorized access. The following sections discuss the current and future positions on this.
R7 AND EARLY R8
In Release 7 there is no native file encryption or file security when using File Based Loader or HCM Extract. The
only security is as result of access limitations based on the username/password and roles granted.
Files delivered to and from the Fusion sftp site are only restricted based on the access to the sftp site. However
files that are sent to File Based Loader for processing are removed from the sftp site once they are consumed.
From there the file is moved to the Fusion server where it will reside unencrypted. Only the cloudOps engineers
with access to the customer environments would be able to reach these files.
Files that are placed in UCM prior to uploading to Fusion are restricted to only those users with the access rights
arising from a provisioned role. In the same way as with sftp, once the file has been consumed it is moved from
the UCM site.
HCM Extract writes output files to the BI server and these can be downloaded using the BI ScheduleService. These
files are not encrypted by default.
HCM Data Loader streams files from UCM and does not explicitly move a file to the Fusion server. It currently
leaves the file in UCM, but in the future there will be a configuration setting that will allow the file to be removed
once it has been processed.
HCM CONNECT V1
HCM Connect v1 will be available in the second half of 2014 on Release 8 and will enable the transfer of PGP
encrypted files from the customers server to UCM (Web Content Server). As well as coordinating the invocation of
FBL/HCM Data Loader to upload the files. FBL and HCM Data Loader will be modified to handle an encrypted file
and to accept instructions to decrypt it before uploading the data to Fusion.
HCM Connect v1 will also allow customers to generate PGP encrypted output from HCM Extract and provide their
servers or 3rd party servers as destinations for this output.
The product facilitates the automated transfer and at the same time ensures data in transit and at rest stays
encrypted. It is comprised of a set of light-weight binaries and use-case driven instructions. HCM Connect V1
utilizes existing Fusion data migration tools, such as FBL, to perform migration of business objects into Fusion
HCM. The binaries, which can be downloaded or hosted in the PaaS cloud, perform the more mundane steps of
typical Fusion HCM in-bound integration process by performing the file transfer, loading the file into UCM, and
triggering the FBL/HCM Data Loader process.
ROADMAP
The following tables gives an indication of the integration tools that are or are planned to be available in the
forthcoming releases.
R7
Yes
Yes
Yes
No
Yes Controlled Release
No
Yes
Yes
Yes
Yes additional cost
No
R8
Yes
Yes
Yes
Limited Availability
Yes Controlled Release
No
Yes
No
Yes
Yes additional cost
Patch on R8 from mid-year
R9
Yes
Yes
Yes
Controlled Availability
Controlled Release
Yes
Yes
Yes
Yes
Yes additional cost
Yes