Fusion Application:

File Based Loader (FBL)

Prasanna Borse
Senior Program Manager, CoE
 Safe Harbor Statements
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 Oracles products remains at the
sole discretion of Oracle.

2 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Overview
Fusion Integration Framework
Fusion Integration (Go-forward) Strategy

File Based Loader

Overview
Agenda Process flow
Supported business objects
Data loading sequence
FBL2 new features
Demo
Configuration
Cross reference key map
File format
Enterprise level setup vs Conversion objects

Appendix
A- Resources
B- Advanced features in FBL2
C- Filenames and structure
D- Delete diagnostics
E - Loading talent profiles using FBL

3 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Oracle Fusion Integration Framework
The Big Picture
File Based Loader -
Simplified high volume data
loading based on CSV ,
XML, DAT
HCM Extract - Extract,
Core HR
Spreadsheet Loader Transform and format large
Simplified Low volume data Staging HCM amounts of complex data
Area Benefits Extract
loading via spreadsheets
Performance
Specialized Loaders - Management
Payroll Batch Elemen BI Publisher - Extract data
Goal from HCM Business Object
Entries, Benefits, Talent Management repository in a preformatted
Web services Web Fusion template
Talent
Programmatic data Services Analytics
exchange with external OTBI - Extract data from
Compensation HCM Business Object
systems
repository to provide real-
time operational reporting &
file creation

4 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Oracle Fusion Integration Framework
Integration Patterns

Bulk Data (Batch

Spreadsheets Real Time
mode)

FBL Payroll Batch Element Entry HCM Web Services

HCM Extract Benefits Enrollment (External services Rel7)

Benefits Extract HCM Data Events (** future release)

BI Publisher Loaders\Spreadsheet loaders
Payroll Interface Talent (Goals, Competencies)

5 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Fusion Integration
Fusion
Go-Forward Integration Strategy Oracle Fusion Applications

Talent Review Network at Work

Performance
Management
Compensation
Management
Goal Management
File Based Loader (FBL) for all
Fusion HCM inbound integrations

Migrate
File Based HCM

Refresh

Migrate
HCM Extract for all Fusion HCM Loader: Extract

outbound integration Existing

Application

Employee Compensation
Profiles
Data Changes

Core HR

Time And Labor Payroll Benefits

6 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 File Based Loader

Overview
Load HR data from your source system to
Fusion HCM
Flat file based data upload utility
Validates and loads the data
Support for Error Correction
Supports complex data objects with full date
effective history
Supports multiple data sources
FBL2\Rel5 supports incremental updates

7 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Process Flow

Source System Fusion

8 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Process Flow
1. Prepare Fusion for Integration

9 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Process Flow
2. Transform and Generate Data Files

10 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Process Flow
2. Transform and Generate Data Files

11 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Process Flow
3. Validate and Load Data

12 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Supported Business Objects
Work Structures Talent Employment
1. Location 1. Competencies 1. Person
2. Organizations 2. Qualification Person Name
Business Unit 3. Rating Scales & Levels Person National Identifier
Departments 4. Schools & Colleges Person Address
3. Job Family Person Legislative
4. Job Person Phone
5. Position Person Email
6. Grade Person Documentation
7. Grade Rate Person Type Usage
2. Assignment
Assignment Work Measure
Compensation Assignment Supervisor
1. Salary Basis Work Term
2. Salary, Salary Components Work Relationship
3. Element Entries (Bonus, Allowances) 3. Person Profile
4. Person Profile Items

13 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Data Loading Sequence
1. Action
12. ContentItem
2. ActionReasons
13. ContentItemRelationship
3. Location
14. Person
4. BusinessUnit
15. PersonDocumentation
5. Grade
16. Department
6. GradeRate
17. Position
7. JobFamily
18. WorkRelationship
8. Job
19. Salary
9. SalaryBasis
20. Element Entry
10. Establishment
21. Profile
11. Rating Model

Object Load SQL: SELECT * FROM FUSION.hrc_loader_metadata_registry ORDER BY processing_order Asc

14 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 FBL 2 New Features
Partial LBO Hierarchy Support
Partial Date Effective BO History Rowset
Logical Start and End Date movement
Explicit setting of NULL for attribute values
UI: BAD and Log file availability
SQLLoader column reference name support
Improved error reporting
Examining error message lines
Internal diagnostics; Logical Metadata, Key Map
New Importing Batch Header status
UCM Integration (Release 7)

15 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Live Demonstration

16 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Configuration: Setup and Maintenance -> Manage HCM Configuration for
Coexistence -> Parameters

17 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

2007 Oracle Corporation Proprietary and Confidential
 Data Exchange UI- Load data into Fusion

18 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Data Exchange UI- Load data into Fusion

Example System will schedule 4 threads\processes, each process to

work on batch size of 500 transactions at a time and every process has
the limit of 250 errors (i.e. overall 250*4=1000 errors)
19 Copyright 2013, Oracle and/or its affiliates. All rights reserved.
 Cross Reference Key Map

20 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Cross Reference Key Map
GUID information for Enterprise Level Configuration

21 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Cross Reference Key Map
File format
XREF
FusionGUID *FusionKey PeopleSoftKey Description Description2
B175DC5AD1DB33FCE040E40A0F901637 0 Common Set,US COMMON
B175DC5AD10833FCE040E40A0F901637 21 Enterprise Set,US ENTERPRISE
B175DC5AD1F833FCE040E40A0F901637 100010032542659 HIRE Hire
B175DC5AD22133FCE040E40A0F901637 100010032542697 TERMINATION Termination
B175DC5AD21933FCE040E40A0F901637 100010032542689 REHIRE Rehire of Worker
B175DC5AD1E033FCE040E40A0F901637 100000012473175 HCM Seeded Enterprise 02 US
B175DC5AD22C33FCE040E40A0F901637 100010032683744 Cost of Living Adjustment CMP_COLA

FusionGUID - is a 32 alphanumeric GUID used by both Fusion and 3rd Party HCM (i.e. PSFT, EBS, JDE, etc..). This is the
unique key for each row of every XREF table.

FusionKey Is the key value Fusion HCM is going to use for this particular XREF

PeopleSoftKey Is the key value the 3rd Party HCM product (not necessarily Peoplesoft) is going to use for a particular
XREF.

Description Short descriptor to make this row of data in this table more functionally meaningful.

Description2 Long descriptor to make this row of data in this table more functionally meaningful.

For e.g When you convert business unit\organizations then you will pass B175DC5AD1DB33FCE040E40A0F901637 value as
GUID to refer to Common Set in the Business Unit VO data file.

22 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 23 Copyright 2013, Oracle and/or its affiliates. All rights reserved.
2007 Oracle Corporation Proprietary and Confidential
 Enterprise setup vs Conversion Objects
Data you setup online in Fusion Data you should not setup online, instead convert using FBL
Enterprise Level Setup Work structure & Employee Data
This is the basic setup in every project irrespective of conversion approach.
There is no GUID extract required for data converted using FBL. You will specify IDs (JOBID,
Once you configure following objects in Fusion Application, extract the GUIDs using cross Location ID, Person ID ..etc) as part of your data file. FBL will use those IDs to build the key map
reference process and use it in the input files for mapping. internally.
Objects supported by FBL for conversion:
Objects you configure online: Work Structures
ACTION Business Units
ACTION_REASON Locations
ACTION_REASON_USAGE Job Families
ACTION_TYPE Jobs
ASSIGNMENT_STATUS_TYPE Grades
ENTERPRISE Grade Rates
LEGAL_ENTITY Positions
LEGISLATIVE_DATA_GROUP Departments
PERSON_TYPE Dept Hierarchy
SETID Transaction Data
PAY_ELEMENT_TYPE_STD Person
PAY_ELEMENT_TYPE_SUPPL Work Relationships (work term, assignment, supervisor, work measure)
PAY_INPUT_VALUE_STD Workforce Compensation
PAY_INPUT_VALUE_SUPPL Salary Basis
HRT_CONTENT_ITEM_LANGUAGE Salary
HRT_CONTENT_TYPE Element Entries
HRT_CONTENT_TYPE_RELAT Talent Management
HRT_PROFILE_TYPE Content Items
HRT_QUALIFIER Rating Models
HRT_QUALIFIER_SET Establishments
HRT_RELATION_CONFIG Profiles (Qualifications, Competencies, latest Performance Rating)

24 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Appendix-A
Resources

25 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 File Based Loader Resources
Integrations Library: The Data Conversion Reference Library provides customers
and partners with timely data conversion related information specific to their Fusion
HCM implementation. It promotes library self-sufficiency by allowing users to provide
Library content feedback via a beehive workspace forum for corrections,
clarifications, enhancement suggestions or new topics of interest for the library.
Email Timm.Hannula@Oracle.com or Rashmi.mohanty@oracle.com for access
Link for UPK

Starting a new Project? If you are starting a new project and you are done with
basic enterprise level configuration then extract the cross reference file and we can
assist you with sample data files specific for your POD. Sample file will be based on
values in your cross reference so that you can quickly upload some test data and
start using FBL. (upcoming solution- FBLdi)
Email Prasanna.Borse@Oracle.com

26 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Appendix-B
Advanced features in FBL2

27 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Partial LBO Hierarchy Support
Specification of a FULL LBO hierarchy is not required
FBL 2 Key Resolution
Builds a full hierarchy for the Data Loader
Creates missing parent batch line row(s) where required with a NOOP
WorkerRelationship/WorkTerms/Assignment not supported (due to synch
model)

|---------NOOP--------------------------------> Person <PSEUDO_ROW/>

|---------CREATE------------------------------> Person Names

28 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Partial Date Effective BO History Rowset
Key Resolution/Delta Performed at runtime
All incoming DE Rowsets are treated as:
Create Logical Row: FULL (Rowset)
Update Logical Row: PARTIAL (Rowset)
Batch Lines created with: DELETE, CREATE, UPDATE, NOOP
Batch Lines are created for a FULL logical row processing
|-A-------------------------------------------> Existing Fusion
|-B----------------------------> Incoming Source

|-A------------|-B----------------------------> Target Rowset

Batch Lines:
|-A:DELETE------------------------------------>
|-A:CREATE-----|
|-B:CREATE--------------------->

29 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 SQLLoader column reference name support

SQLLoader supports columns by name (i.e. they dont have to be in a

specific position)
Unknown columns are ignored

30 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Appendix-C
Filenames and structure

31 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 FBL
Filenames

32 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 FBL
.DAT file structure

First row represents the column names

Delimiter = |
Columns can be specified in any order
Mandatory columns should exist in the dat file

33 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Appendix-D
Delete diagnostics

34 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Delete diagnostics
1: One time registration

Navigation: Help -> Troubleshooting -> Run Diagnostic Tests

Register New Test
Enter /u01/APPLTOP/fusionapps/applications/hcm/hcm_delete_object.xml
Register

35 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Delete diagnostics
2: Running the delete diagnostics

Navigation: Help -> Troubleshooting ->

Run Diagnostic Tests
Search for Tests -> HCM Delete Object ->
Search
Select and add to Run

36 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Delete diagnostics
2: Running the delete diagnostics

In the Choose Tests to Run and

Supply Inputs panel-

37 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Delete diagnostics
2: Running the delete diagnostics

Click on Input Status icon to open

parameters window.

38 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Delete diagnostics
3: Parameters
Type - Object Type, one of the following (must be entered Id - Fusion Id value
exactly as below): GUID - GUID value as used in HR2HR
BusinessUnit
Created By - user who created the data to be
Department
deleted
Grade
GradeRate Created By Current User (Y/N)
Job Created By HR2HR (Y/N)
JobFamily
Commit (Y/N) - If N the diagnostic will indicate
Location how many top level objects will be removed
Position but will rollback, if Y it will commit
Person
PersonDocumentation
WorkRelationshipByPerson - the work relationships for the person will
be deleted, the count of objects affected is the number of people (not
work relationships)
ElementEntry ** As you see, it does not support all the
Salary objects. I have logged ER 16781757 No
AllByPerson ETA received from dev.

39 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Appendix-E
Loading Talent Profiles using FBL

40 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Loading Talent Profiles
Pre-requisite steps
Person data has already been loaded into Fusion apps through HR2HR
(or) FBL
Profile setup data has been completed on Fusion side
Rating Models, Rating Levels
Establishments
Any changes to seeded Content Types
Custom Content Types defined
Content Items created (Competencies / Degrees / Licenses etc.)

41 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Loading Talent Profiles
Profile Objects
Three primary objects representing Profile Data
Profiles
There are two types of Profiles Person Profile, Model Profile
Person Profile represented by one row of data in the profile data file
Model Profile - represented by one row of data in the profile data file
Profile Items
Child of Profile object with each row representing and capturing different profile attributes
Example: A competency in Java is one row, a Degree of Bachelors in Science is a row, a Certification in Nursing is
one row in the profile items data file
Profile Relationship
Primarily used for Model Profiles and we have 1-Many relationship between Profile and Profile Relationships
A single row in Profile Relationship is used to associate the Model Profile to a specific Work Structure (Job, Position,
Organization, Job Family)

42 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Loading Talent Profiles
Step1:- Determine GUIDs for Profile setup data a

Filter the Key Map Reference data based on OBJECT_NAME. Following is a listing of
various OBJECT_NAMES and their Logical Business Object mapping

OBJECT_NAME Fusion Object OBJECT_NAME Fusion Object

PERSON_VO Person ESTABLISHMENT_VO Establishment

HRT_PROFILE_TYPE_VO Profile Type HRT_CONTENT_TYPE_VO Content Type

RATING_MODEL_VO Rating Model CONTENT_ITEM_VO Content Item

RATING_LEVEL_VO Rating Level HRT_QUALIFIER_VO Qualifier

The FusionGUID from the cross reference data for each of the above Objects will be used in the data loader
files

43 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Loading Talent Profiles
Step2:- Prepare the parent file that links profile id with person id
Define Profiles data loader file (F_PROFILE_VO.csv). Following is a description of each row
of data in the file (one row needs to be give for one person profile record)
Attribute
Position Datastore Attribute Name Data Type Length Mandatory Description
1 PROFILE_ID NUMERIC 18 Yes GUID (customer should give a random unique value)
2 DESCRIPTION VARCHAR 4000 No Name of the person (eg: Stewart Holmes)
3 SUMMARY VARCHAR 4000 No <leave it blank>
4 BUSINESS_GROUP_ID NUMERIC 18 Yes Specify as 1 or can be left null and will be defaulted during data load
GUID value to be obtained from Key Map Reference table corresponding
to OBJECT_NAME = HRT_PROFILE_TYPE_VO and Additional
5 PROFILE_TYPE_ID NUMERIC 18 Yes Description of Person
6 PROFILE_CODE VARCHAR 30 Yes <leave it blank>

7 PROFILE_STATUS_CODE VARCHAR 30 Yes A (lookup code to indicate Active)

8 PROFILE_USAGE_CODE VARCHAR 30 Yes P (lookup code to indicate Person Profile)

GUID value to be obtained from Key Map Reference table corresponding
to OBJECT_NAME = PERSON_VO and Additional Description of the
9 PERSON_ID NUMERIC 18 No person name for whom we are creating the Profile
10 PARTY_ID NUMERIC 18 No <leave it blank>

11 OWNER_PERSON_ID NUMERIC 18 No GUID thats the same as used for PERSON_ID above

44 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Loading Talent Profiles
Step3:- Define Profile Items
Define Profile Items data loader file (F_PROFILE_ITEM_VO.csv). This is
a child of the Profiles object and one row represents a specific profile item
for the Person
Example: Each of the row can be a Person having a Competency of Java with a
Proficiency Rating of 4 , Person having a Degree in Bachelors of Science from MIT,
or even a row of data representing a custom content type
As part of this step,
We first need to understand how the Profile Items data has been defined on the Fusion
side
Map the source data to the definition and represent them as a single row in CSV file

45 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Loading Talent Profiles
Step3:- Define Profile Items continued
Taking the example of Degrees, in the screenshot below there are two pieces of data we
need to use for file loader data - (Column Name and Label)

46 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Loading Talent Profiles
Step3: Define Profile Items continued
Using the definition of the Degrees content type we now can define the Profile Item data in the csv file
Attribute
Position Datastore Attribute Name Data Type Length Mandatory Description
1 PROFILE_ITEM_ID NUMERIC 18 Yes GUID (customer should give a random unique value)
GUID that was used earlier to load the Profile record for the respecting
2 PROFILE_ID NUMERIC 18 Yes Person

3 BUSINESS_GROUP_ID NUMERIC 18 No <leave it blank> - will be defaulted during data load

GUID from Key Map reference data corresponding to
OBJECT_NAME=HRT_CONTENT_TYPE_VO and
4 CONTENT_TYPE_ID NUMERIC 18 Yes ADDITIONAL_INFO=Degrees
GUID from Key Map Reference table corresponding to OBJECT_NAME =
CONTENT_ITEM_VO and Additional Description of <Degree Name>
5 CONTENT_ITEM_ID NUMERIC 18 Yes that we want to enter the data for and applicable to this person
6 DATE_FROM DATE 30 Yes <leave it blank> - will be defaulted to sysdate
7 DATE_TO DATE 30 Yes <leave it blank>
8 ITEM_TEXT240_1 VARCHAR 240 Yes Major for this degree
9 ITEM_TEXT240_6 VARCHAR 240 No Average Grade
GUID from Key Map Reference table corresponding to OBJECT_NAME =
ESTABLISHMENT_VO and Additional Description of <School Name>
10 ITEM_NUMBER_9 VARCHAR 18 No from where the Person obtained the degree
11 ITEM_NUMBER_8 NUMERIC 18 No Year the Degree was acquired

47 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

 Loading Talent Profiles
Step4: File upload and registration
The F_PROFILE_VO.csv and F_PROFILE_ITEM_VO.csv need to be packaged in a zip file
The zip file needs to be copied over to Fusion SFTP and register the file using end point
URL.
Run the batch program from Data Exchange UI
Check that the Profiles UI in Portrait shows the data that has been loaded

48 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

49 Copyright 2013, Oracle and/or its affiliates. All rights reserved.