Example of Loading a Recurring Element Entry With an Open End Date
Lisa Jones has been asked to work from the company's headquarters from 01-Apr-2019 until further communication. As part of this assignment, she's paid a Commutation Allowance of 1000 per pay period.
Load the element entry details for Lisa, as shown in this table:
|
Attribute |
Value |
|---|---|
|
Legislative Data Group |
Vision Corp |
|
Element Name |
Commutation Allowance |
|
Assignment Number |
E3141464 |
|
Start Date |
01-Apr-2019 |
Load the element entry values, as shown in these tables:
|
Attribute |
Value |
|---|---|
|
Legislative Data Group |
Vision Corp |
|
Element Name |
Commutation Allowance |
|
Assignment Number |
E3141464 |
|
Start Date |
01-Apr-2019 |
|
Input Value Name |
PRD |
|
Screen Entry Value |
1000 |
This ElementEntry.dat file creates the element entry values.
METADATA|ElementEntry|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|LegislativeDataGroupName|ElementName|EntryType|CreatorType|HrAssignmentId(SourceSystemId)
MERGE|ElementEntry|VISION|12351_COM_ALW|2019/06/01|4712/12/31|Vision Corp|Commutation Allowance|E|H|12351_ASG
METADATA|ElementEntryValue|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|LegislativeDataGroupName|ElementName|InputValueName|ScreenEntryValue|ElementEntryId(SourceSystemId)
MERGE|ElementEntryValue|VISION|12351_COM_ALW_PRD|2019/06/01|4712/12/31|Vision Corp|Commutation Allowance|PRD|1000|12351_COM_ALW-
You don't need to supply the MultipleEntryCount attribute as source keys to uniquely identify the records.
-
When loading a recurring element entry with an end date, supply the EffectiveEndDate attribute on all file lines for the element entry.