Escolar Documentos
Profissional Documentos
Cultura Documentos
Full HR Deployment 5
References 10
Data Extraction 11
Build Your Own: Custom Extracts 12
References 16
Data Loading
Depending on how customers implement HCM Cloud, there are two deployment patterns: co-existence
deployment or full HR deployment. The data loading use case differs for each pattern.
Co-Existence Deployment
For a Talent coexistence deployment, you are keeping part of your existing HCM System and moving your talent
modules to the HCM Cloud as the first step in your full HCM Transition. In this deployment mode, the existing
Core HR continues to be the system of record for HR data.
In this case, keeping the two HCM systems in sync is done using bulk data import:
One time Data Load of Employee data to HCM Cloud for initialization.
Migration of Talent Profile information migrated to HCM Cloud.
Ongoing data load to sync employee changes from the Core HR system of record.
HCM Cloud used for Talent Review, Goals and Performance Management, Workforce compensation,
Analytics.
Feed profile and compensation changes information to other systems from HCM Cloud.
In this deployment mode, you transition your Core HR systems from On Premise to the HCM Cloud.
In this case, the data migration when you are moving your on premise HCM System to the cloud is done via bulk
data import. This allows you to move large amounts of history into the new Cloud Based HCM System.
Data Migration/Initial Conversion: Includes Load Setups, Work Structures, and Employee Data from
legacy HR systems.
HCM Cloud becomes the system of record for HR data.
Feed downstream systems with New Hires, Employee Updates, Transfers, Promotions, Terminations,
Work structures & Updates.
Interfaces to downstream Payroll, Benefits and Time and Labor systems.
Feeds from Recruiting System to HCM Cloud.
Ongoing data load runs: Sometimes if there is an external system that needs to feed to HCM Cloud on a
regular basis even if HCM Cloud is the Master HCM system, you will need the data loaders to run on a
periodic system. Example: Kronos for Time Information feeding to HCM Cloud Payroll.
Considerations for Full History data load vs. Partial data load:
o Cost/benefit of converting historical data should be evaluated at an early stage in the
implementation.
o Historical data is typically dirtier and therefore more costly to convert the older it is.
o Customers need to design (technically and process-wise) to make historical conversion offline.
o For example, it can be done before a critical cutover window or after go-live.
o As part of the implementation design, customers have to identify the volumes of data loads for
each object and evaluate the impact of historical data in their source instance.
o Additionally, customers should review the process-wise flows in Fusion for the importance of
historical data. For example, a Fusion Financials customer might have a preference for Historical
data to be loaded after a production cutover.
o If its Full HR customer and does not want to go back to old Legacy system for any reason then it is
Historical data has to be loaded before production cutover.
Implementation Considerations:
o It’s a good practice to identify integration requirements prior to the initial design of
implementation for initial loads. This helps customers foresee the data impacts of integrations
ahead of time.
Testing considerations:
o Leverage the Data Validator Tool to verify the quality of the data. Any new changes to source
system data files should to be verified in the stage pod before going to production.
o The Data File Validator Tool can be downloaded from My Oracle Support Doc ID: 2022617.1. You
can use this tool to validate the format of the data file extracted from your source system,
including flex field configuration. It allows some custom rules to be added for more precision in
your extracted data.
References
HCM Data Loader (HDL)
HCM Data Loader: Notice of General Availability Doc ID 2022629.1
This note provides the announcement of availability, a brief overview and some basic guidance for
new and existing customers.
HCM Data Loader Frequently Asked Questions (FAQ) Doc ID: 2022630.1
This note provides some questions you may have which include advantages of HDL, object related
information, and other common questions.
Oracle HCM Data Loader: User Guide Doc ID: 1664133.1
This note contains the User Guides for both Release 9 and 10.
HCM Data Loader: Business Object Documentation Doc ID 2020600.1
This note contains detailed information about the objects supported.
Migrating from File-Based Loader to HCM Data Loader Doc ID 2022628.1
This note contains key information that existing customers should think about when planning to
migrate from FBL to HDL.
Integration Guide for Oracle Fusion HCM and Taleo Recruiting (Doc ID 1947417.1)
Payroll ADP US Extracts Employee, Work structure ,Salary Depends on the Yes
Payforce (ADP Payroll/tax data, Gross Earning Calculation as customer
Connections for per the third party specification scenario
Payforce) May require SI configuration for customer
specific ADP Data definition and HCM Cloud
configuration
North Gate Extracts Employee, Work structure ,Salary Depends on the Roadmap
Arinso Payroll Payroll/tax data, Gross Earning Calculation as customer
per the third party specification scenario
May require SI configuration for customer
specific ADP Data definition and HCM Cloud
configuration
Global Generic Consists Payroll/tax data , Gross Earning Depends on the Roadmap
Payroll Interface Calculation etc customer
Used to extract Common HR and Regional scenario
data from an LDG.
SI adds local data as specified by regional
payroll vendors.
Benefits Benefits XML HR xml based Extracts with Employee Benefit Depends on the Yes
Integration Enrollments data that’s transformed by customer
Benefits XML to various Benefits carrier scenario
specifications
Incremental info on
Health/Savings/FSA/Disability/Life AD&D info,
Enrollment, Life Events info, and so forth.
Scenario: small organization that needs 5-10 extracts from HCM Cloud
In this case, you can define and run the extracts and transport the output files to target systems directly from
HCM Cloud.
HCM Extracts
Middleware on Premise
(File Transformation, Load,
transport )
References
HCM Extracts:
o Oracle Fusion HCM Extracts Guide
o Extracts delivery options
o Defining Simple Outbound Interface Using HCM Extracts
o How to use DBIs for formulas and Extracts in Fusion HCM
CONNECT W ITH US
blogs.oracle.com/oracle Copyright © 2015, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents
hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions,
facebook.com/oracle whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We
specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this
twitter.com/oracle document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose,
without our prior written permission.
oracle.com
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or
registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.0115