HDL documentation: Overview of Loading Element Entries

You may click on the business object to get details of the attributes as follows.
Data Exchange -> HCM Data Loader->View Business Objects
Click on the link for the business object (Element Entry)
Click Attributes tab->Click Export to Excel

First consider whether the element is recurring or non recurring; then consider
whether the element allows multiple entries.

A non recurring element will exist only within the pay period of the employee
assigned payroll in the element entry.
If multiple entries for the element is checked, then you can load multiple entries
within the same pay period.
A recurring element will exist in every pay period of the employee’s assigned payroll
until end dated in the entries. As a default the end date will be End Of Time (EOT)
4712/12/31.

Verify what input values are mandatory; use the sql below

select petf.element_type_id
,pettl.element_name
,petf.processing_type Recurring_NonRecurring
,petf.effective_start_date
,petf.effective_end_date
,petf.multiple_entries_allowed_flag
,pivf.base_name
,pivf.mandatory_flag
from pay_element_types_f petf
,pay_element_types_tl pettl
,pay_input_values_f pivf
where petf.element_type_id = pettl.element_type_id
and pivf.element_type_id=petf.element_type_id
and pettl.element_name = 'WK_PerDiem'
and pettl.language='US'
and pivf.user_enterable_flag='Y'

Verify the existing element entries for a person with the sql below:

select
aaa.person_number,aaa.element_name,aaa.creator_type,aaa.created_by,aaa.creation_Da
te,aaa.entry_range,aaa.multiple_entry_count,
(select min(date_from)||'~'||max(date_to) from pay_entry_usages where
element_entry_id=aaa.element_entry_id) usage_range,
aaa.element_entry_id,
(select --LISTAGG(piv.name, '; ') WITHIN GROUP (ORDER BY piv.display_sequence)
rtrim(xmlserialize(content extract(xmlagg(xmlelement("e", piv.name||'; ') order by
piv.display_sequence), '//text()')), ',' )
from PAY_INPUT_VALUES_VL piv
where piv.element_type_id = aaa.element_type_id and aaa.start_Date between
piv.effective_start_date and piv.EFFECTIVE_END_DATE) inputs,
(select --LISTAGG(piv.name||'='||peev.screen_entry_value, '; ') WITHIN GROUP
(ORDER BY piv.display_sequence)
rtrim(xmlserialize(content extract(xmlagg(xmlelement("e", piv.name||'='||
peev.screen_entry_value||'; ') order by piv.display_sequence), '//text()')), ',' )
from PAY_INPUT_VALUES_VL piv,pay_element_entry_values_f peev
where peev.element_entry_id = aaa.element_entry_id and peev.input_value_id =
piv.input_value_id
and piv.element_type_id = aaa.element_type_id and aaa.start_Date between
piv.effective_start_date and piv.EFFECTIVE_END_DATE
and aaa.start_Date between peev.effective_start_date and peev.EFFECTIVE_END_DATE)
input_values,
(select max('PERL:'||prl.payroll_relationship_number||'('||
prl.payroll_relationship_id||'); '||'TERM:'||trm.assignment_number||'('||
trm.relationship_group_id||'); '||'ASG:'||asg.assignment_number||'('||
asg.relationship_group_id||'); ')
from pay_entry_usages peu,
pay_rel_groups_dn asg,
pay_rel_groups_dn trm,
PAY_PAY_RELATIONSHIPS_DN prl
where peu.element_entry_id=aaa.element_entry_id
and peu.payroll_assignment_id=asg.relationship_group_id (+)
and peu.payroll_term_id=trm.relationship_group_id (+)
and peu.payroll_relationship_id = prl.payroll_relationship_id
) Payroll_Employment,
(select max('TERM:'||htrm.assignment_number||'('||htrm.assignment_id||');
'||'ASG:'||hasg.assignment_number||'('||hasg.assignment_id||'); ')
from pay_entry_usages peu,
pay_rel_groups_dn asg,
pay_rel_groups_dn trm,
per_all_assignments_m hasg,
per_all_assignments_m htrm
where peu.element_entry_id=aaa.element_entry_id
and peu.payroll_assignment_id=asg.relationship_group_id (+)
and peu.payroll_assignment_id=trm.relationship_group_id (+)
and hasg.assignment_id (+) = asg.assignment_id
and htrm.assignment_id (+) = trm.term_id
) HR_Employment
from (select peo.person_number,
pet.element_name,
pee.creator_type,
pee.created_by,
pee.creation_Date,
pee.element_entry_id,
pee.element_type_id,
pee.multiple_entry_count,
min(pee.effective_start_date) as start_Date,
min(pee.effective_start_date)||'~'||max(pee.effective_end_date) entry_range
from per_all_people_f peo,
pay_element_entries_f pee,
pay_element_types_vl pet
where peo.person_number = '<enter person number here>'
and pee.person_id = peo.person_id
and pee.element_type_id = pet.element_type_id
and pet.element_name = '<enter element name here>'
group by peo.person_number,
pet.element_name,
pee.element_type_id,
pee.creator_type,
pee.created_by,
pee.creation_Date,
pee.element_entry_id,
pee.multiple_entry_count) aaa
order by aaa.person_number,
aaa.element_name,
aaa.creator_type,
aaa.created_by,
aaa.creation_Date,
aaa.element_entry_id

Navigation: Payroll –> Administration->Manage Elements

In the example below, the element "WK_PerDiem" is a recurring element which

Since the element "WK_PerDiem" allows multiple entries, the multiple entry count /
sequence number would need to be used.

Download sample sql to assist in identifying load issues here: Element Entries
Sql.txt

For example, here is a sample file

ElementEntry.dat

Since the element "WK_PerDiem" allows multiple entries, the multiple entry count /
sequence number would need to be used.

Download sample sql to assist in identifying load issues here: Element Entries
Sql.txt

For example, here is a sample file

ElementEntry.dat

METADATA|ElementEntry|CreatorType|EffectiveStartDate|EffectiveEndDate|ElementName|
LegislativeDataGroupName|EntryType|AssignmentNumber|MultipleEntryCount
MERGE|ElementEntry|WK_LOAD|2018/01/01||WK_moving_expense|WK_LDG|E|E1000576|1

METADATA|ElementEntryValue|EffectiveStartDate|EffectiveEndDate|InputValueName|
ScreenEntryValue|AssignmentNumber|ElementName|LegislativeDataGroupName|
LegislationCode|MultipleEntryCount|EntryType
MERGE|ElementEntryValue|2018/01/01||Amount|4000.99|E1000576|WK_moving_expense|
WK_LDG|US|1|E

Note: The CreatorType is an extensible common lookup for which you may add
values to "PAY_CREATOR_TYPE"

Setup and Maintenance->Manage Common Lookups

NOTE: For existing element entries, modifying the creator type will ONLY allow to
be modified to one of the following:
F (Element Entry Page),
H (Loader),
CWB (Comp Work bench),
VC (Individual Comp)

The following is an example of Multiple Entries, when an Element is setup with

METADATA|ElementEntry|CreatorType|EffectiveStartDate|EffectiveEndDate|ElementName|
LegislativeDataGroupName|EntryType|AssignmentNumber|MultipleEntryCount
MERGE|ElementEntry|WK_LOAD|2018/04/02||WK_Bonus|WK_LDG|E|EWK_1997|1
MERGE|ElementEntry|WK_LOAD|2018/04/02||WK_Bonus|WK_LDG|E|EWK_1997|2
MERGE|ElementEntry|WK_LOAD|2018/04/02||WK_Bonus|WK_LDG|E|EWK_1997|3
MERGE|ElementEntry|WK_LOAD|2018/04/02||WK_Bonus|WK_LDG|E|EWK_1997|4
METADATA|ElementEntryValue|EffectiveStartDate|EffectiveEndDate|InputValueName|
ScreenEntryValue|AssignmentNumber|ElementName|LegislativeDataGroupName|
LegislationCode|MultipleEntryCount|EntryType
MERGE|ElementEntryValue|2018/04/02||Amount|100.99|EWK_1997|WK_Bonus|WK_LDG|US|1|E
MERGE|ElementEntryValue|2018/04/02||Amount|200.99|EWK_1997|WK_Bonus|WK_LDG|US|2|E
MERGE|ElementEntryValue|2018/04/02||Amount|300.99|EWK_1997|WK_Bonus|WK_LDG|US|3|E
MERGE|ElementEntryValue|2018/04/02||Amount|400.99|EWK_1997|WK_Bonus|WK_LDG|US|4|E

NOTE: A base pay element associated with a salary basis must be recurring.
Loading of Salary elements with HDL use Salary.dat and should not be created
directly using ElementEntry.dat file.

MultipleEntryCount uniquely identifies the row; in UI called Sequence Number