Examples of Loading Seniority Date Adjustments

A seniority date is the date on which the calculation of a worker's length of service with the enterprise is based. This topic provides examples showing how to update V3 seniority dates using HCM Data Loader.

The following table identifies attributes that you can use to identify the entity on which the seniority date is based. You can use alternative key types, where available. For example, to identify a job you can use the user key (JobCode and BusinessUnitShortCode) instead of the JobId value.

Entity	Identifying Attribute
Bargaining unit	BargainingUnitCode
Collective agreement	CollectiveAgreementId
Department	DepartmentId
Enterprise	BusinessUnitShortCode
Grade	GradeId
Grade step	GradeStepId
Job	JobId
Legal employer	LegalEntityId
Legislation	LegislationCode
Location	LocationId
Position	PositionId
Union membership	UnionId

Updating Seniority Dates Using User Keys

The following example Worker.dat files update a worker's seniority date based on various assignment attributes. They use user keys to reference the Seniority Date component. As these examples show, you must include the ManualAdjustmentComments attribute when you make a manual adjustment to the seniority date. In these examples, the seniority date rule is configured at the person level.

This example updates a worker's seniority date based on the assignment.

METADATA|SeniorityDate|SeniorityDateCode|PersonNumber|EntryDate|EffectiveStartDate|EffectiveEndDate|BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|JobCode|AssignmentNumber
MERGE|SeniorityDate|JUN_A|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data Correction|JOBCD7|E9990401

This example updates a worker's seniority date based on the department.

METADATA|SeniorityDate|SeniorityDateCode|PersonNumber|EntryDate|EffectiveStartDate|EffectiveEndDate|BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|DepartmentName
MERGE|SeniorityDate|JUN_DEPARTMENT|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data Correction|Commercial Sales

This example updates a worker's seniority date based on the enterprise.

METADATA|SeniorityDate|SeniorityDateCode|PersonNumber|EntryDate|EffectiveStartDate|EffectiveEndDate|BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments
MERGE|SeniorityDate|JUN_ET|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data Correction

This example updates a worker's seniority date based on the grade.

METADATA|SeniorityDate|SeniorityDateCode|PersonNumber|EntryDate|EffectiveStartDate|EffectiveEndDate|BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|GradeCode
MERGE|SeniorityDate|JUN_GRADE|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data Correction|DHRX-AE-IC1

This example updates a worker's seniority date based on the job.

METADATA|SeniorityDate|SeniorityDateCode|PersonNumber|EntryDate|EffectiveStartDate|EffectiveEndDate|BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|JobCode
MERGE|SeniorityDate|JUN_JOB|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data Correction|JOBCD7

This example updates a worker's seniority date based on the job but uses the seniority date rule name rather than its code.

METADATA|SeniorityDate|SeniorityDateCode|PersonNumber|EntryDate|EffectiveStartDate|EffectiveEndDate|BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|JobCode
MERGE|SeniorityDate|SeniorityDateJUnit Person Job|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data Correction|JOBCD7

This example updates a worker's seniority date based on the legal employer.

METADATA|SeniorityDate|SeniorityDateCode|PersonNumber|EntryDate|EffectiveStartDate|EffectiveEndDate|BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|LegalEmployerName
MERGE|SeniorityDate|JUN_LEMP|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data Correction|Vision Corporation

This example updates a worker's seniority date based on the location.

METADATA|SeniorityDate|SeniorityDateCode|PersonNumber|EntryDate|EffectiveStartDate|EffectiveEndDate|BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|LocationCode
MERGE|SeniorityDate|JUN_LOCATION|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data Correction|V1-_NEW_YORK_CITY_0_2450399170046

This example updates a worker's seniority date based on the position.

METADATA|SeniorityDate|SeniorityDateCode|PersonNumber|EntryDate|EffectiveStartDate|EffectiveEndDate|BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|PositionCode
MERGE|SeniorityDate|JUN_POSITION|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data Correction|POSCD66

This example updates a worker's seniority date based on the work relationship.

METADATA|SeniorityDate|SeniorityDateCode|PersonNumber|EntryDate|EffectiveStartDate|EffectiveEndDate|BusinessUnitShortCode|ManualAdjustmentDays|ManualAdjustmentComments|JobCode|WorkerType|LegalEmployerName|DateStart
MERGE|SeniorityDate|JUN_WR|9990101|2012/01/01|2015/01/01|4712/12/31|Vision Corporation Enterprise|20|Data Correction|JOBCD7|E|Vision Corporation|2001/05/05