Professional Documents
Culture Documents
JANUARY 2016
Table of Contents
Loading Element Entries Using HCM Data Loader
Introduction
Element Entry
Element Entry
Table of Figures
Figure 1: Create Element Entry ................................................................................................................................ 5
Figure 2: Manage Person Details ............................................................................................................................. 5
Introduction
Whether implementing Oracle Fusion Payroll for the first time or providing regular updates, you can
create element entry records using HCM Data Loader.
For general information about preparing data for loading using HCM Data Loader or the HCM Data
Loader file format, see the HCM Data Loader Users Guide (MOS Doc ID: 1664133.1).
Loading Describes the business object hierarchy. For each business object component, a table of
the attributes that are commonly supplied when creating new records is provided. These tables
have the following columns:
HCM Data Loader Attribute The attribute name to supply when providing your data in the
business object data (.dat) file. Attribute names with a *1 suffix are foreign-object references
that support the integration key types. As source keys are recommended where possible, the
document describes how to supply source key values. User key attributes are identified for
when you do not have the source key value.
User Interface Prompt The prompt seen on the user interface. The data that you supply in
the associated attribute derives this field value, which is not necessarily the same as the value
that you supply. For example, for the Location field on an Organization page you can supply
the Oracle Fusion surrogate ID, source key, or Oracle Fusion GUID to identify the location
uniquely. The value seen on the user interface will be the location name.
If the User Interface Prompt is prefixed with an asterisk (*), then the attribute is mandatory
when you create a new record.
Functional Description Additional information describing the attribute and how to supply
valid values.
Errors Identifies errors that may occur when loading data for the business object. Information
about resolving the error is provided.
Deletion Support Describes the extent to which the business object supports data deletion. Some
objects do not support deletion, while others may support deletion of child records only.
Translation Information on how to provide translation data for the translatable attributes in the
business object hierarchy.
For both user key and source key examples, ensure that any references to foreign objects refer to data
that exists in your test environment.
Element Entry
Element entries are used to capture earnings, deductions, absences, and basic benefit details for an employee
assignment. For example, you can create element entries for an employee's overtime hours or medical premium
deduction amount.
See the Manage Element Entries topic in the help documentation for further information on element entries.
Component
Functional Description
Discriminator
Element Entry
An element entry holds the actual payroll element and benefits granted to a worker.
These may be ongoing, recurring entries, such as salary, or single-period, nonrecurring
entries, such as a bonus.
ElementEntry
Element entry values are the individual values that are contained in the input values for
an element entry. They can be defaulted or entered by a user.
ElementEntryValue
Element Entry
Value
Element Entry
The Element Entry holds details of the payroll element and benefits granted to a worker.
The discriminator ElementEntry is used to load element entry records using HCM Data Loader. The following
ElementEntry attributes are commonly supplied when loading a new element entry.
ELEMENT ENTRY ATTRIBUTES
Functional Description
* Element
You must provide a unique reference for the record being created. Supply either a
source key or the user key attributes LegislativeDataGroupName, ElementName,
AssignmentNumber, and MultipleEntryCount.
* Assignment Number
* Sequence Number
EffectiveStartDate
The start date of the element entry or the update to the element entry, if you are
supplying date-effective history.
Functional Description
EffectiveEndDate
The end date of the element entry or the update to the element entry, if you are
supplying date-effective history. If left blank, this value is the end of time by
default.
AssignmentNumber
* Assignment
Specify the assignment number for the element entry. The feature creates the
entry in the appropriate employment record based on the element type definition.
For example, if the element is defined at assignment level, then the entry is
created for the assignment number passed in the batch. If the element is defined
at terms level, the entry is created for the terms associated with the assignment
number passed in the batch. If the element is defined at payroll relationship level,
then the entry is created for the terms associated with the assignment number
passed in the batch.
MultipleEntryCount
* Sequence Number
Supply the sequence number for the element entry. This is 1 if this is the first
occurrence of this element on this date.
CreatorType
Source
This is a derived value. It indicates whether the element entry was added through
the user interface, loaded by a batch, or created by an HCM product such as
Absence Management.
ElementName
* Element
LegislativeDataGroupI
d *1
* not displayed
Provide a reference to the legislative data group. If you are using user keys, then
supply the attribute LegislativeDataGroupName.
Attribute
DateEarned
This object also supports source keys. If you supplied a source key when you
created the legislative data group, then you can supply it here by adding the
source key hint to this attribute. For example,
LegislativeDataGroupId(SourceSystemId).
EntryType
* Entry Type
User key attributes that need to be supplied only if no other key type is provided.
LegislativeDataGroup
Name
The name of the legislative data group. Supply this if no other key type is provided
to reference the legislative data group.
The attribute value supplied will derive the value seen in the field specified in the User Interface Prompt.
* Required
*1
The foreign object reference supports all four key types: Oracle Fusion surrogate ID, Oracle Fusion GUID, source key, and user
key.
User Interface
Attribute
Prompt
SourceSystemId /
SourceSystemOwner
* Element
* Assignment Number
* Sequence Number
Functional Description
You must provide a unique reference for the record being created. Supply either a
source key or the user key attributes LegislativeDataGroupName, ElementName,
AssignmentNumber, MutipleEntryCount, and InputValueName.
* Element
* Assignment Number
* Sequence Number
The unique reference to the element entry this value is for. If supplying user keys,
use the attributes LegislativeDataGroupName, ElementName,
AssignmentNumber, and MultipleEntryCount.
This attribute also supports the integration key types. If you supplied a source key
for the element entry, supply the same value here and append the source key hint
to the attribute name, for example, ElementEntryId(SourceSystemId).
EffectiveStartDate
The start date of the element entry value or the update to the element entry value,
if you are supplying date-effective history.
EffectiveEndDate
The end date of the element entry value or the update to the element entry value,
if you are supplying date-effective history. If left blank, this value is the end of time
by default.
LegislativeDataGroupN
ame
* not displayed
ElementName
* Element
AssignmentNumber
* Assignment Number
Specify the assignment number for the element entry. The feature creates the
entry in the appropriate employment record based on the element type definition.
For example, if the element is defined at assignment level, then the entry is
created for the assignment number passed in the batch. If the element is defined
at terms level, then the entry is created for the terms associated with the
assignment number passed in the batch. If the element is defined at payroll
relationship level, then the entry is created for the terms associated with the
assignment number passed in the batch.
InputValueName
ScreenEntryValue
* value displayed
MultipleEntryCount
* Sequence
The attribute value supplied will derive the value seen in the field specified in the User Interface Prompt.
* Required
*1
The foreign object reference supports all four key types: Oracle Fusion surrogate ID, Oracle Fusion GUID, source key, and user
key.
Resolution
The input value could not be identified, usually because not all attributes that identify it uniquely
were included. Ensure that ElementName, LegislativeDataGroupName, and InputValueName are
all specified.
Worldwide Inquiries
Phone: +1.650.506.7000
Fax: +1.650.506.7200
CONNECT W ITH US
blogs.oracle.com/oracle
facebook.com/oracle
twitter.com/oracle
oracle.com
Copyright 2014, 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, 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 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 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. 0116
Loading Element Entries using HCM Data Loader
January 2016