HCM Data Loader in Fusion - Part 1

In this article we will go through the basics of HCM Data Loader aka HDL which is one of the most
familiar data loading tools in Fusion HCM.

Here is the Agenda for this post:

 What is HCM Data Loader?
 Configure HCM Data Loader Parameters
 Who Can Load Data Using HCM Data Loader?
 Navigation of HDL in Fusion Applications
 Reviewing Supported Business Objects
 Understanding the Business Object Shape
 Supported File Line Instructions
 Definition and Data Line Structure
 File Discriminators
 Line Validation
 Keys and its importance

What is HCM Data Loader?

It is a Flat File based bulk loading of data into Oracle HCM Cloud. 
It is used for Data Conversion into Fusion from any legacy system (PeopleSoft, EBS, SAP, Workday,
etc.) for one-time or incremental loads. 
It is suited for large volumes of data loads and hierarchical data.
It supports multiple data sources. If the customer is a global customer and they might be using different
legacy applications in different countries, we can load all legacy systems data into fusion using HDL.
It uses two step approach, first it will load into staging table and then imports data into the core tables.
It supports loading complex data objects like Worker with full date effective history.

Configure HCM Data Loader Parameters:

More details on configuring HCM Data Loader parameters has been posted at Configure HDL
Parameters. Please check it out and come back to this article.

Who Can Load Data Using HCM Data Loader?

Human Capital Management Integration Specialist job role is required to access the HCM Data Loader
related tasks.
Navigation of HDL in Fusion Applications
Navigate to Navigator > My Client Groups > Data Exchange
Now on the right hand side tasks bar, we can see the tasks for HDL as seen below:
Reviewing Supported Business Objects
In the HCM Data Loader tasks, click on "View Business Objects" task

Understanding the Business Object Shape

The HDL file supports Hierarchical shape of business object components. 
It supports Multiple child occurrences and it has the ability to load child components independently
Supported File Line Instructions

These are the most frequently used File line instructions and is not an exhaustive list. There are some
business object specific file line instructions that can be used. However it would be a new topic of
discussion to get into business object wise file line instructions. Exhaustive list of all SET operations have
been listed at SET Operations on HDL file

Definition and Data Line Structure

METADATA / MERGE / DELETE line format:
<INSTRUCTION>|<DISCRIMINATOR>|<Attribute 1>|...|<Attribute n>

Example:
METADATA|Job|JobCode|SetCode|Name|EffectiveStartDate|EffectiveEndDate|ActiveStatus
MERGE|Job|ACC1|COMMON|Accountant|2012/02/01||A

File Discriminators
Sample for Job Business Object. We can see that it has two discriminators Job and JobGrade.
Line Validation
 First METADATA line is defined for each object and the next line is followed by the
corresponding MERGE/DELETE data Line.
 One .dat file cannot have same METADATA Line repeated more than once.
 Each METADATA line should have a valid discriminator
 Contain unique reference for itself using any one of the supported key       resolutions
 Child component must include a unique reference to its parent.
 MERGE/DELETE Line should contain the values of the same attributes as defined in the
corresponding METADATA Line

Keys and its importance

Keys are used to uniquely identify one of the below
 The local business object component
 The parent of a business object component
 Any other object referenced by a business object component
Types of Keys supported by HDL
HCM Data Loader supports Four types of keys to uniquely identify a business object.
 Oracle Fusion GUID
 Oracle Fusion Surrogate ID
 Source Keys
 User Keys
Oracle Fusion GUID
 Generated in Oracle Fusion when a record is created
 It holds an Hexadecimal value
 Unique across all objects in Fusion system
 Held in Integration Key Map (HRC_INTEGRATION_KEY_MAP) table
 Cannot be assigned in the HDL file while creating Business Object
 Can be assigned in HDL file while updating/deleting Business Object
Source Keys
 Two values combined "SourceSystemOwner" and "SourceSystemID" make a unique source key
combination
 Multiple Source System Owners can be configured if the customer uses multiple legacy systems
 Held in Integration Key Map table
 Can be used in creating/updating/deleting data in HDL file
Oracle Fusion Surrogate ID
 Generated in Oracle Fusion when the record is created
 Numeric value
 Unique only for the object type
 Held against the object definition
 Cannot be used while creating Business Object in HDL file
 Can be used while Updating/Deleting Business Object in HDL file
User Keys
 Natural values
 One or many attributes
 Sometimes alternatives
 Sometimes updateable
 Can be used while creating/updating/deleting Business Objects in HDL file
Key Resolution Sequence
1.Oracle Fusion GUID
2.Oracle Fusion Surrogate ID
3.Source Keys
4.User Key
HDL file will use this sequence to identify the key fields that have been provided in the HDL file. If
multiple types of key fields are provided, then it will pick up the first in this sequence.

Configuring the HCM Data Loader Parameters in Fusion

One of the first step to use the HCM Data Loader is to Configure the HDL Parameters. In this article we
will discuss available options and evaluate pros and cons for each.

Where to Configure the HCM Data Loader Parameters?

Login to Fusion Applications > Click on Navigator > Setup and Maintenance >
Search for "Configure HCM Data Loader" and open the task
 

We will discuss some of the important Parameters which impact the HDL loads.

HCM Data Loader Scope: Limited/Full.. This parameter was introduced in R10 and at that time FBL
and HDL both were used for data loads. Now in R13 Oracle is decommissioning the FBL tool
completely, this parameter is defaulted to Full for all new customers since R11 release.
Enable Audit Data: Yes/No - Specifies whether audit data is captured for business objects loaded using
HCM Data Loader. If you set this parameter to Yes, then audit must also be enabled for Oracle Fusion
Applications.
Enable Load Group Size Calculation: Specifies whether the load-group size is to be calculated
automatically. Set to Yes to enable the optimal load-group size to be calculated based on the number of
objects to process and the available concurrent threads. When Enable Load Group Size
Calculation is Yes, the Load Group Size parameter doesn't appear on the Schedule Request page. Also,
the default value of the Load Group Size parameter is ignored.
Purge Person Enabled Key: Key value supplied by Oracle Support to enable the Purge Person Data in
Test Environments process. You can't enable and run this process in production environments.

Business Object Parameters:

Calculate Worker Full Time Equivalent: Yes/No - Set this Flag if the FTE needs to be calculated
automatically for all worker assignments in Worker.dat
Create Worker Default Work Hour Pattern: Yes/No - Set this to Yes if the workers need to have a
default Work Hour Pattern when they are loaded.

SET Operations on HDL file in Fusion

In HDL dat file, we can use different SET commands which change the way the data load happens.
Below is the exhaustive list of all SET operations that can be performed in HDL dat files.
SET CALCULATE_FTE Y/N
To request automatic calculation of full-time equivalent (FTE) values for all worker assignments in a
Worker.dat file, include the SET CALCULATE_FTE instruction.
For example:
SET CALCULATE_FTE Y

SET CREATE_DEFAULT_WORKING_HOUR_PATTERN Y/N

To request automatic creation of a default working-hour pattern for all worker assignments in a
Worker.dat file, include the SET CREATE_DEFAULT_WORKING_HOUR_PATTERN instruction.
For example:
SET CREATE_DEFAULT_WORKING_HOUR_PATTERN Y

SET DISABLE_POST_PROCESS_TASKS
By default, these processes run automatically after we load worker.dat file:
Refresh Manager Hierarchy
Update Person Search Keywords
To prevent Refresh Manager Hierarchy from running automatically, include this SET instruction in the
Worker.dat file:
SET DISABLE_POST_PROCESS_TASKS RefreshManagerHierarchy
To prevent Update Person Search Keywords from running automatically, include this SET instruction in
the Worker.dat file:
SET DISABLE_POST_PROCESS_TASKS UpdatePersonSearchKeywords
Tip: To prevent both processes from running automatically, use the SET INVOKE_POST_PROCESS
instruction.

SET INVOKE_POST_PROCESS
By default, these processes run automatically after we load workers:
Refresh Manager Hierarchy
Update Person Search Keywords
To prevent both processes from running automatically, include this SET instruction in the Worker.dat
file:
SET INVOKE_POST_PROCESS N

SET FILE_DELIMITER
Use this instruction to change the default file delimiter, which is the vertical bar (|). For example, to
change it to a comma, include this instruction:
SET FILE_DELIMITER ,
The new value can be up to 10 characters.

SET FILE_ESCAPE
Use this instruction to change the default file escape character, which is the backslash (\). For example, to
change it to the equal sign (=), include this instruction:
SET FILE_ESCAPE =
The new value can be up to 10 characters.

SET FILE_NEWLINE
Use this instruction to change the default file newline character, which is the character n. For example, to
change it to the string newline, include this instruction:
SET FILE_NEW_LINE newline
The new value can be up to 10 characters. For example, you could set the newline character to newline
and the file delimiter to comma (,) using the following SET commands:
SET FILE_DELIMITER ,
SET FILE_NEW_LINE newline
In this case, METADATA and MERGE lines could appear as follows:
METADATA,Address,AddressLine1
MERGE,Address,TheSteading\newlineKier Allan

SET PURGE_FUTURE_CHANGES
When you create business objects containing date-effective components, you include this instruction at
the start of the file:
SET PURGE_FUTURE_CHANGES Y -> Replace mode
This instruction sets the date-effective maintenance mode to Replace. In this mode, which is the default
mode, the contents of the .dat file replace any existing data.
A single record replaces existing date effective records for the date range specified on the update.
SET PURGE_FUTURE_CHANGES N -> Retain Mode
This instruction sets the date-effective maintenance mode to Retain. In this mode, any existing future-
dated changes are retained.

Example:
To change the working hours to 37.5 from 2012/01/10 without affecting future-dated records, you use this
data file:
SET PURGE_FUTURE_CHANGES N
METADATA|Assignment|SourceSystemId|EffectiveStartDate|EffectiveSequence|EffectiveLatestChange|
EffectiveEndDate|ActionCode|NormalHours
MERGE|Assignment|223724|2012/01/10||Y|#RETAIN|ASG_CHANGE|37.5

If you know any other SET operations post them in the comments section, I will update the post with
those details.

Hope this helps. Stay tuned to the blog for latest updates

Defining Source System Owner for HDL in Fusion

HCM Data Loader is one of the most familiar Bulk Data Loading tool available in Fusion. Basics of HDL
have been covered at HCM Data Loader. If you haven't got a chance to look into it, please look into it and
then continue reading this article.

We can use User Keys/Source Keys when we load data for Business Objects. For using Source Keys, we
first need to define the Source System Owner and then use the defined Source system owner in the HDL
file.

Configuring Source System Owner:

Login to Fusion Applications > Click on Navigator > Setup and Maintenance
Search for task "Manage Common Lookups"
Search for the Lookup Type of "HRC_SOURCE_SYSTEM_OWNER"
We can create a new Source System Owner by Clicking the + sign and then save it.

Once the Source System Owner has been defined, we can use this Source System Owner in the HDL file.

Sample HDL:
METADATA|Worker|SourceSystemOwner|SourceSystemId|EffectiveStartDate|PersonNumber|
ActionCode|ReasonCode|StartDate|CountryOfBirth|CategoryCode MERGE|Worker|
HRC_SQLLOADER|PER_11111|1945/02/12|11111|HIRE|NEWHIRE|1945/02/12|US|PER_EIT
Sample CostAllocationAccount.dat HDL file
In the below post, we will try to see how to load the Cost Allocation Account Information. The Cost
Allocation Account can be loaded at multiple levels Job, Position, Organization, Payroll, Payment
Method, Assignment, Assignment Terms, Payroll Relationship, Person, Element Entry and Element Link
(Element Eligibility) levels.

How the Payroll Costing works is out of scope of this article.. We will try and see how this information
can be loaded using HDL..Source Type would be different for costing at each of the above levels.

Some Info on costing levels and hierarchy:

For more info on payroll costing refer
to https://docs.oracle.com/en/cloud/saas/global-human-resources/r13-update18a/faipc/payroll-
costing.html#FAIPC1266589

HDL File Sample:

METADATA|CostAllocationAccount|SourceType|ElementLinkName|DepartmentName|JobCode|
PositionName|SetCode|PaymentSourceName|PayrollName|Name|AssignmentNumber|
PayrollRelationshipNumber|TermNumber|ElementTypeName|MultipleEntryCount|
LegislativeDataGroupName|EffectiveDate|SourceSubType|Proportion|SubTypeSequence|
ConcatenatedSegment|Segment1|Segment2|Segment3|Segment4|Segment5|GUID|SourceSystemId|
SourceSystemOwner
MERGE|CostAllocationAccount|ORG||DDT_DEPT01|||COMMON|||||||||LDG US|2011/12/31|COST|0.8|
1||3|330|1333||210|||
MERGE|CostAllocationAccount|JOB|||DDT_JOB01_CD||COMMON|||||||||LDG US|2011/12/31|COST|1|
1||4|340|1100|1400|240|||
MERGE|CostAllocationAccount|POS||||DDT_POS01|COMMON|||||||||LDG US|2011/12/31|COST|1|1||5|
350|1320|1410|200|||
MERGE|CostAllocationAccount|PAY|||||||PAY01_TEST|||||||LDG US|2011/12/31|COST|1|1||1|300|1300|
1420||||
MERGE|CostAllocationAccount|PM||||||DDT_CHECK_PS01||||||||LDG US|2011/12/31|CASH|1|1|
81.421.1510.2100.8784||||||||
MERGE|CostAllocationAccount|ASG|||||||||ASG_PER01|PER_01||||LDG US|2011/12/31|COST|1|1||||||
300|||
MERGE|CostAllocationAccount|TERM|||||||||ASG_PER01|PER_01||||LDG US|2011/12/31|COST|1|4|||||
2102|400|||
MERGE|CostAllocationAccount|PREL||||||||ASG_PER01_NAME||PER_01||||LDG US|2011/12/31|COST|
1|7||||1400|2103|500|||
MERGE|CostAllocationAccount|AET|||||||||ASG_PER01|PER_01||StdEarning_ASS_OFFSET_TEST
Earnings Results||LDG US|2011/12/31|COST|1|10|||330|1410|||||
MERGE|CostAllocationAccount|TET|||||||||ASG_PER01|PER_01||StdEarning_TEM_001_TEST Earnings
Results||LDG US|2011/12/31|COST|1|13||28|340|1420|||||
MERGE|CostAllocationAccount|PRET||||||||ASG_PER01_NAME||PER_01||
VolDeduction_PR_001_TEST Results||LDG US|2011/12/31|COST|1|16||29|350|1431|||||
MERGE|CostAllocationAccount|EE|||||||||ASG_PER01|PER_01|WT_PER01|
StdEarning_ASS_COST_TEST|1|LDG US|2011/12/31|COST|1|1||||||600|||
MERGE|CostAllocationAccount|EL|StdEarning_ASS_COST|||||||||||||LDG US|2011/12/31|COST|1|1|||100|
1200|5000|100|||
Hope this helps when you have requirement to load the Cost Allocation Account information using
HDL. Stay tuned to the blog for more updates.
SQL Query to get the HDL file from staging tables
Normally when we load the data using HCM Data Loader aka HDL, the File Delete Option would be
defaulted to 'Y' and the input zip file would be deleted post processing of that file.

However out of my enthusiasm, I searched for options to get that HDL file from staging tables and finally
figured out a way to get it using BI Report. Below is the SQL that need to be used on Data Model to get
the HDL file as output.

SQL Query:
SELECT fl.TEXT
,bo.data_file_name
FROM fusion.hrc_dl_file_lines fl
,fusion.hrc_dl_data_set_bus_objs bo
,fusion.hrc_dl_data_sets ds
WHERE ds.ucm_content_id = 'UCMFA00014838' -- Replace this with the actual
content id
AND fl.data_set_bus_obj_id = bo.data_set_bus_obj_id
AND ds.data_set_id = bo.data_set_id
ORDER BY fl.seq_num ASC
HCM Data Loader Overview
23
Intro

A week ago I started to learn new bulk loader feature HCM Data Loader which was recently released (You can see
details here HCM Data Loader: Notice of General Availability (Doc ID 2022629.1))
I got ready to spend a lot of time, but I was wrong. It wasn’t very difficult to understand how it works.
HCM Data Loader is very flexible and easy in use. And I would like to share a little experience working with HDL.

Some additional features available in HDL in comparison with FBL

1. Finally you don’t need to think about internal GUIDs of business objects. (Supports user keys for all
objects. Knowledge of Oracle HCM Cloud internal IDs is not required)
2. HDL can both create/update records and DELETE records. (Of course if you don’t have references from
dependent objects)
3. You can use |SourceSystemOwner|SourceSystemId| Attributes to hold references from third-party systems
4. Now you can load translations for translatable business objetcs
5. You can load attachments
6. You can bulk load photos for employees
How it works

1. HDL Parameters
First of all you need to check HCM Data Loader Configuration Parameters. As far as I know starting from Release
10 HDL will be the main tool for bulk loading data into the system. In Release 9 you can still decide what tool you
wish to use (FBL or HDL). To make sure that HDL will be accessible you have to set HCM Data Loader Scope
parameter to Full.
To load data using HCM Data Loader, you must have the Human Capital Management
Integration Specialist job role.
In addition you have to add the HCM Data Loader Duty to the Human Capital Management
Integration Specialist Job Role.

2. Preparation of DAT File

You can download template files for every business object supported by HDL form the
system.
You can use HCM Data Loader: Business Object Documentation (Doc ID 2020600.1) as a start point
for preparation of DAT files.
There are a lot of instructions and features you can use in DAT file. You can read complete
list of features in documentation. But I’d like to note: Never put MERGE and DELETE
instructions into one DAT file.
Please see my Worker.dat sample:
As you can see the structure of HDL file is quite simple in comparison with the FBL file
structure. Attachments and photos you have to put into separate directory (BlobFiles,
ClobFiles) in ZIP file.

3. HCM Data Validator

And for validation of DAT file we can use Data Validator tool. You can read about it
here: Data File Validator Tool for HCM Data Loader (Doc ID 2022617.1)
4. Import and Load
Finally you need to upload zip file to WebCenter Content Server and submit Import and
Load Process.

To achieve full automation you can use tools for transferring HDL files to content Server and
invoke web service (https://<url-to-your-environment>/hcmCommonDataLoader/HCMDataLoader?WSDL )
to submit import process.
See details here: Automating HCM Data Loader
Submit Import and Load process you can from Data Exchange Work Area:
And finally you can see my successfully loaded worker with the personal photo:

After loading workers, you usually need to run ESS jobs to perform specific operations:

 Update Person Search Keywords

 Synchronize Person Records
 Refresh Manager Hierarchy
Fusion HCM Interview Questions
5. Q : What is Legislative Data Group in Fusion HCM?
Legislative data groups are a means of partitioning payroll and related data.
At least one legislative data group is required for each country where the
enterprise operates. Each legislative data group is associated with one or more
payroll statutory units. Each legislative data group marks a legislation in which
payroll is processed, and is associated with a legislative code, currency and its
own cost key flexfield structure.

6. Q : What are Oracle Fusion Trees?

Oracle Fusion trees are graphical representations of hierarchical data such
as the structure of your organization. Oracle Fusion Human Capital
Management (HCM) provides predefined tree structures for department,
organization, position, and geography trees. You cannot change the
predefined HCM tree structures. With the exception of geography trees, you
can create multiple trees for each HCM tree type, and multiple versions of
each tree. For all HCM tree types, however, only one version of each tree can
be active at one time.

7. Q : If you update an assignment record multiple times in

a single day, can you still track the record, if yes how?
For some objects, such as assignments, more than one update per day is
maintained by creating a physical record for each update. Such objects include
an effective sequence number in each physical record to show the order in
which updates made to an object on a single day were applied.

Q : What is Functional Setup Manager or FSM as it is

8.

more commonly known as?

 Oracle Fusion Functional Setup Manager (FSM) is an application that provides
an end-to-end guided process for managing your functional implementation
projects throughout the entire implementation life cycle.

Q : What is Enterprise Structure Configurator (ESC) and

9.

what are the benefits of using it?

The ESC is an interview-based tool that guides you through the configuration
of your enterprise structures. Use the ESC as part of your set up to define the
organization structures and job and position structures of the enterprise.

To access ESC, In the Setup and Maintenance work area, select the Establish

Enterprise Structures task under the Define Initial Configuration task list.
Benefits of ESC:
 Create all the organizational structures at one time.
 Create multiple configurations to test multiple scenarios.
 Review the enterprise configuration prior to loading it.
 Rollback an enterprise configuration after loading it.
10. Q : What do you understand by Reference Data Sharing?
In oracle Fusion Reference data sharing facilitates sharing of configuration
data such as jobs, grades across business units. It can be understood as
buckets of reference data assigned to multiple business units. It helps
to reduce duplication and maintenance by sharing common data across
business entities where appropriate. In Oracle Fusion Applications reference
data sharing feature is also known as SetID. A set, which is available out of the
box is called Common Set
In HCM Set enabled objects are: Departments, Locations, Jobs & Grades
Q : What’s the difference between the Watchlist and the
11.

Worklist?
Watchlist feature provides a set of shortcuts to items that you want to track or
that require your attention. Watchlist is used to see a count for each item and
to navigate to the relevant work area where you can view or perform tasks on
the item. For example, a Watchlist item is for expense reports awaiting
submission. You can see how many expense reports you have created but not
 yet submitted, and click the Watchlist item link to navigate to the work area
where these reports appear.

Whereas Worklist feature presents workflow tasks that require your approval
or other action, as well as notifications for you to view. Worklist is used to
manage tasks, access their details, or take appropriate action. For example,
some managers might see approval tasks for invoices, and select a particular
task to approve, reject, or otherwise act on the corresponding invoice.

Q : Could you please list down some of common task

12.

used during implementation

Here are few basic and frequently used task

1. Manage Enterprise HCM Information

2. Manage Legal Entity HCM Information
3. Manage Legal Addresses
4. Manage Legal Entity
5. Manage Location
6. Manage Divisions
7. Manage Departments
8. Manage Business Unit
9. Manage Actions
10. Manage Job
11. Manage Grades
12. Manage Profile Options
13. Manage Gallery Portrait
14. Manage Person Types
15. Manage Common Lookups
16. Manage Review Periods
17. Manage Performance Document Types
18. Manage Worker Goal Setting Profile Option Values
19. Manage Worker Goal Setting Lookups
20. Manage Goal Management Notification Settings
P.S. Task names are not case-sensitive

Q : What is distribution threshold in fusion performance

13.

management?

When we
create Rating Model for performance management we do define Rating
Distribution to tell what is the minimum and maximum percentage of worker
should fall in each rating level. This is more commonly known as
Normalization. Now the Distribution Threshold is a filed to control “Number
of eligible workers a manager must have to see distribution target“.
Q : How many sections a performance template can hold
14.

and what are those?

An Oracle Fusion Performance Template can hold maximum of six sections,
which are given below

1. Competency Section
2. Goal Section
3. Worker Final Feedback Section
4. Manager Final Feedback Section
5. Questionnaire Section
6. Overall Review Section
15.Q : What are the different absence type patterns available
in Fusion Absence Management?
 An absence pattern contains a predefined set of rules that you can use as a
starting point to create an absence type. The pattern that you select
determines whether special fields appear on the absence type pages, as well
as the options available to display and process various aspects of absence
recording. For example, the Illness or injury pattern displays a field that
enables you to select whether the absence type applies for childbirth or
adoption placement.

Following are the three patterns available in Fusion Absence Management.

 Illness or injury
 Childbirth or placement
 Generic absence
Q : What are the different plan types available in Fusion
16.

Absence Management?
There are three different plan types available in Fusion Absence Management,
which are given below:

Accrual
Use this type to create absence plans that enable workers to accrue time for
the purpose of taking paid leave, for example, a vacation plan. Our
requirement qualifies for this plan type.

Qualification
Use this type to create an absence plan where workers qualify for the plan as a
result of events, such as long term illness or maternity, and receive payments
during the absence period.

No Entitlement
Create absence plans of this type to track paid or unpaid absences without
maintaining an accrual balance or providing leave entitlements, such as
periodic accruals. You can also use plans of this type in combination with a
 qualification plan. For example, use a no-entitlement plan to pay workers if
they are not eligible for a standard maternity absence qualification plan.

Q : Here are few questions for you to share answer in

17.

comment section
 What is instance qualifier?
 What if content type, content item and free form content type?
 What minimum roles you should have to initiate fusion HCM
implementation?
 What are the key steps you need to follow for fusion performance
management?
 How Fusion is different than R12/PeopleSoft?
 What is the difference between Legal Entity and Legal Employer?
18. Q : What is Oracle Sandbox?
We have good collection of interview questions on Sandbox, which you can
access here » How to replace oracle fusion logo with custom logo?
19.Q : Here are some fusion individual compensation plan
interview questions
Question : Is it possible to set up the approvals based on the amount entered
for the individual compensation plan?
Question : You have setup Individual Compensation Plan how would you bulk
enrollment large employees?
Question : How to add Validation for Individual Compensation, for example
an employee can be granted special bonus only once in a lifetime.
Question : What is the difference between workforce compensation and
Individual compensation
To see answer of these question, please read article  Oracle Fusion Individual
Compensation Plan Explained With Examples
Q : May I have additional interview questions on fusion
20.

compensation
For interview questions on fusion workforce compensation please visit the
page Fusion Compensation Interview Questions
21. Do you have any question?
If you have any question to ask, please do ask them in our forum. All you need
to do is click on link Ask Question  and you are done.
22. Additional Oracle Fusion HCM interview questions:
For oracle Fusion certification or interview you may like to see more questions.
We suggest to visit our Interview Question section and
select  category Fusion. Please also share your Oracle Fusion HCM interview
Question in the comments box below.If you have any question, just ask here