Import data rahul vishwanath

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Proprietary and Confidential – Distributed to Authorized Customers Subject to Safe Harbor1
IMPORT DATA
ORACLE FUSION HCM IMPLEMENTATION
PARTNER WORKSHOP
Oracle Fusion Human Capital Management

The following is intended to outline our general product direction. It is intended
for information purposes only, and may not be incorporated into any contract.
It 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
described for Oracle’s products remains at the sole discretion of Oracle.
Safe Harbor Statement

The information in this presentation is correct as of the presentation date.
However, Oracle Fusion HCM continues to evolve and software patches are
applied frequently; therefore this information is subject to change.
Check with your Oracle Representative for updates. This content is not
warranted to be error-free.
Content Subject to Change

Objectives
 Introduction - Importing Data.
 Import Data Using :-
 File Based Loaders.
 Spreadsheet Data Loaders.
 Future Enhancements.

Introduction – Importing Data

 Why is Data Import required or Where can it be used ??
 Migrating existing data completely before retiring a legacy
product. *
 Importing data from a third party supplier.
 In a co-existence scenario where Oracle Fusion HCM is being
used with another product. **
e.g. Using Oracle Fusion HCM along with another legacy system
in place.
 Oracle Fusion HCM supports the importing for:-
 Initial enterprise structures such as legal entities. ***
 Setup data such as jobs, departments & benefit plans.
 Transactional data such as employee records.
 Transactional history such as salary changes & performance
reviews.
**Note Before
* Typically requires a one time data upload.
** Such scenario’s may require repeated data uploads into Oracle
Fusion HCM depending on the business scenario.
*** Generally done using spreadsheet loaders. The enterprise structures
can also be loaded using the Enterprise Structures Configurator
(ESC)

Sr. No Spreadsheet Data Loader HCM File Based Loader
1.
Helps loads simple hierarchical and non-
hierarchical data.
Helps load complex hierarchical data.
2.
Can support only small to medium data volumes
since MS Excel has limited number of rows and
columns.
Can support large data volumes.
3. Best suited for one time migration. Can be useful where a frequent data update is required.
4. Does not support loading of object history. Supports loading of object history.
5.
Data cleansing and validation is required since data
is on an excel based format.
No such restriction.
6.
Supports update only for limited number of
business objects.
No such restriction.

HCM – File Based Loaders

How it Works
1. Define & Extract Cross –
Reference Data
SFTP Server / UCM
2. Map Cross Reference
Data to Source Data
3. Extract Source Data
4. Import Source Data Into
Stage Tables
5. Load Data to Oracle
Fusion Application Tables
DATA VALIDATION
DATA VALIDATION
DATA PUSHED IN .DAT FORMAT
1. Users define any Oracle Fusion business
objects that are referenced by your source data
and extract the cross reference data for those
business objects. The cross reference
information is written automatically to the
SFTP / UCM server.
2. Import the cross reference information to your
source environment and map them with your
data.
3. Users then map the data to the Oracle Fusion
business object model, extract the data and
deliver it to the SFTP / UCM server.
4. HCM file based loader imports your source
data to the stage tables.
5. Load batch data loads your source data from
the stage tables to the Oracle Fusion
application tables.

HCM – File Based Loaders – Supported Functionality
 Supported Business Objects – HCM File Based
Loader : -
 Action & action reasons.
 Locations.
 Business units.
 Grades.
 Grade rates.
 Job families.
 Jobs.
 Salary bases.
 Educational establishments.
 Rating Models.
 Talent profile content items.
 Talent profile content item relationships.
 Persons (employees, contingent workers, non-
workers etc)
 Supported Business Objects – HCM File Based
Loader : -
 Person contacts.
 Person documentations (if any).
 Departments.
 Positions.
 Work relationships & assignments.
 Salaries.
 Element entries.
**Note Before
- Business objects listed in the recommended initial upload order .
- Business objects which are not listed here will have to be taken through
the HCM extracts to pin point the exact fusion source ID.
- Custom business objects are not a part of the file based loader’s
capabilities. E.g. capturing of Facebook statuses, integration with twitter
etc.

HCM – File Based Loaders – Points To Note
 While Updating Objects :-
 Best practice states that only the relevant entities and attributes of a related object (s) should be updated and not the entire
business object. e.g. If a person’s address changes, then users can just upload the new address. *
 Within an entity for an object, users can chose to omit optional attributes and can also change the order of the columns.
 Users should note that if they change an attribute that appears in all entities of an object, then they should remember to
change it in all the entries of an object. e.g. The logical start date for a work relationship.
 For Date Effective Objects :-
 Users should avoid from uploading the complete object history. They can chose to upload a partial history. The changes are
applied automatically to the relevant physical records. e.g. changed attribute values within a effective start date and end
dates.
 Users should specify logical start dates and logical end date for any object. **
 Any primary objects such as primary assignments cannot be end dated with a logical end date unless they are tagged as
non-primary first.
**Note Before
* The exception to this general rule is work relationships. Users must upload all entities of the work relationship while uploading.
** For date effective objects, two additional columns exist in the data (.dat file) called LSD (logical start date )& LED (logical end date). Setting either of them to “Y”
indicates that a new value has been specified.

 While Setting Attributes to NULL:-
 Users can set non null attributes to “Null” using an appropriate directive value.
For example : If the value is a
 VARCHAR2 or NUMBER value then users can use #NULL
 DATE value then, users can set it to 31-DEC-0001 (or the equivalent date format)
 For Any Flexfeilds:-
 Users cannot upload any flexfeild data using the HCM File Based Loader. Only descriptive flexfeilds (DFF) are
supported by the File Based Loader. Users need to know the following steps.
1) Configure and deploy your flexfeilds using the Manage Flexfeilds Task.
2) Enter your flexfeild data in a supplied data (.dat) file and save it in .csv format.
3) Open a service request to have the required flexfeild data loaded from the .csv file into your environment.
 This workaround is applicable only to the following tables :-
(1) PER_JOBS_F (2) PER_JOBS_LEG_F (3) PER_PERSONS (4) PER_ALL_ASSIGNMENTS_M (5) HR_ALL_ORGANIZATION_UNITS_F

 For Cross Reference Business Objects :- Business objects which originate in the source environments may
reference other business objects within Fusion. For such objects cross referencing data is required.
Business Objects Oracle Fusion Tasks
Employment Action Reason Manage Action & Manage Action Reasons
Person Assignment Status Type Manage Assignment Status
Enterprise Manage Enterprise HCM Information
Talent Profile Content Item Manage Profile Content Items
Talent Profile Content Type Manage Profile Content Type
Talent Profile Type Manage Profile Types
Talent Instance Qualifier Sets Manage Instance Qualifiers
Legal Entity Manage Legal Entity
Legislative Data Group Manage Legislative Data Groups
Payroll Element Type Manage Elements
Payroll Element Input Value Manage Elements
Person Type Manage Person Types
Application Reference Data Sets Manage Reference Data Sets

FILE BASED LOADER - DEMONSTRATION
Step # 1
Configure load
batch process
Step # 2
Generating the
mapping file
Step # 3
Running the
inbound loader
process
Step # 4
Running the import
process and
reviewing the log
Step # 5
Load data into the
Fusion Application
tables
Step # 6
Validating the
loaded data
Step # 7
Updating the
loaded data
Step # 8
Correcting the
loaded data
Step # 9
Validating
corrected data

HCM – Spreadsheet Based
Loader

How It Works
 Supported Business Objects – HCM
Spreadsheet Based Loader : -
 Locations.
 Grade ladders.*
 Grades.
 Job families.
 Jobs.
 Departments.
 Positions.
 Persons (employees & contingent workers only).
 Work relationships & assignments.
 Educational establishments.
 Salaries.
 Talent profile content items.
 Talent profiles.
Data Exchange Work
Area
Business Object
Spreadsheet
Oracle Fusion
Application Tables
Error HandlingLoad Batch Data To
Stage Tables
Generate Spreadsheet
Upload
Failed Objects
Load Batch Data
Upload
**Note Before
* Some of the spreadsheets support multiple objects. Grade ladders can also be used
to upload grade rates, grade rate values & grades.
Business objects listed in the recommended initial upload order .

HCM – Spreadsheet Loader – Supported Functionality
 Using the spreadsheet loader, users can : -
 Create supported objects.
 Update any worker assignment records.
 Users can also update salary records by indicating in the spreadsheet whether to create, update or delete.
 Date Effectivity : -
 While creating or updating worker assignment records, users can use SBL to both correct and update records.
 To correct a record, specify the same effective start date which was used to create the record.
 To update a record, specify a different effective start date.
 Flexfeild Support : -
 Descriptive flexfeilds - Locations, departments, jobs, job families, worker, worker relationship assignment spreadsheets.
 Developer descriptive flexfeilds – worker & worker relationship assignment spreadsheets.
 Extensible flexfeilds – Organization manager information, GL cost center information.
 Work Day information is supported in the department spreadsheet.

SPREADSHEET LOADER - DEMONSTRATION
Step # 1
Generating the
spreadsheet
Step # 2
Entering the data
within the
spreadsheet
Step # 3
Importing data into
stage tables &
correcting data
Step # 4
Load data into the
application tables
Step # 5
Correcting load
errors (if any)
Step # 6
Validating the
loaded data

Future Enhancements

Future Enhancements
 Spreadsheets to include a ‘Configure Flexfeild’ option. With this functionality, the users can select the
respective flex field type to include the columns within the spreadsheet.
 Both import & load functions to be performed with you click the ‘Upload ’ . With this functionality, the load
batch data process can be eliminated.
 Load errors will be reported in the original spreadsheet itself. With this functionality, users would not have to
extract the file into a separate 'errors spreadsheet’.
 Use of inbound web services as an alternative to the conventional upload tools available.

Import data rahul vishwanath

More Related Content

What's hot (20)

Viewers also liked (9)

Similar to Import data rahul vishwanath (20)

More from mohamed refaei (9)

Recently uploaded (20)

Import data rahul vishwanath