1. HCM Data Loading Business Objects
  2. Example of Loading Assignment Changes

Example of Loading Assignment Changes

You supply the assignment component of the Worker object when making assignment changes under the existing work relationship. This topic shows how to load assignment changes using HCM Data Loader.

Loading Assignment Changes

You can use HCM Data Loader to make the assignment changes for an existing worker. Keep these rules in mind:

  • You must load the relevant Employment Terms and Assignment components in the same Worker.dat file.

  • The values of the EffectiveStartDate and EffectiveEndDate attributes must be the same on the two components.

  • The EffectiveStartDate value is the start date of the assignment change.

  • The EffectiveEndDate value must be the end of time if the assignment record is the latest record.

The following example shows how to load the Employment Terms and Assignment components for an assignment change.

METADATA|WorkTerms|AssignmentNumber|PersonNumber|LegalEmployerName|DateStart|WorkerType|ActionCode|ReasonCode|EffectiveStartDate|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|AssignmentStatusTypeCode|BusinessUnitShortCode
MERGE|WorkTerms|ET955160008178426|955160008178426|Vision Corporation|2009/01/01|E|ASG_CHANGE||2020/01/01|4712/12/31|Y|1|ACTIVE_PROCESS|Vision ADB
METADATA|Assignment|AssignmentNumber|PersonNumber|LegalEmployerName|DateStart|WorkerType|ActionCode|ReasonCode|WorkTermsNumber|EffectiveStartDate|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|AssignmentStatusTypeCode|BusinessUnitShortCode|FLEX:PER_ASG_DF|hdlG(PER_ASG_DF=Global Data Elements)
MERGE|Assignment|E955160008178426|955160008178426|Vision Corporation|2009/01/01|E|ASG_CHANGE||ET955160008178426|2020/01/01|4712/12/31|Y|1|ACTIVE_PROCESS|Vision ADB|Global Data Elements|TestValue

Terminating an Assignment

To terminate an assignment, you must load the Assignment component with the TerminateAssignmentFlag attribute set to Y and specify the termination date for the TerminationDate attribute.

This example terminates an assignment.
METADATA|Assignment|ActionCode|AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|EffectiveStartDate|WorkTermsAssignmentId(SourceSystemId)|SourceSystemOwner|SourceSystemId|TerminationDate|NotificationDate|LastWorkingDate|ReviewUserAccess|TerminateAssignmentFlag
MERGE|Assignment|END_ASG|INACTIVE_PROCESS|E|Vision Corporation Enterprise|4712/12/31|Y|1|2022/07/03|TEST_WT_ut_hdl18_02|HRC_SQLLOADER|TEST_ASG_ut_hdl18_02|2022/07/02||2022/07/02|A|Y
Note: If you don’t provide the WorkTerm attribute along with the Assignment component on the same date, the following error message will be displayed: WorkTerms records required. For date effective records having TerminateAssignmentFlag as Y, the error won’t be displayed. However, for date effective records without TerminateAssignmentFlag, the error will still apply.

Correcting an Assignment Termination

To correct an assignment termination, you must load the Assignment component with the CorrectAssignmentTerminationFlag attribute to Y.

This example corrects an assignment termination.

METADATA|Assignment|ActionCode|AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|EffectiveStartDate|WorkTermsAssignmentId(SourceSystemId)|SourceSystemOwner|SourceSystemId|TerminationDate|NotificationDate|LastWorkingDate|ReviewUserAccess|CorrectAssignmentTerminationFlag
MERGE|Assignment|END_ASG|INACTIVE_PROCESS|E|Vision Corporation Enterprise|4712/12/31|Y|1|2022/07/03|TEST_WT_ut_hdl18_02|HRC_SQLLOADER|TEST_ASG_ut_hdl18_02|2022/07/02||2022/07/02|A|Y
Note:
  • The LastWorkingDate attribute must be on or before the termination date. If the last working date exists and you don't provide a value, the existing last working date will be retained in case of postpone and auto calculated to the termination date in case of prepone. If you provide the last working date value, the new value will take precedence.
  • The notification date will be retained in case of postpone if you don’t provide a value. If you provide a value, the new value will take precedence. In case of prepone, you must provide a notification value. No error message will be displayed even if the notification date is after the termination date in case of postpone or prepone.
  • If you correct the termination date for a terminated assignment to a specific date, the end date must be blank or end of time (12-31-4712).
  • If you correct the existing assignment termination record data without modifying the termination date, you must pass the EffectiveStartDate and EffectiveEndDate attributes of the existing assignment termination record. In this case, your changes will be applicable for the first inactive record (termination record).
  • Prepone will be allowed if there are future updates after the existing Termination or End Assignment inactive record. Future records will be deleted.
  • Postpone won’t be allowed if there are future updates after the existing Termination or End Assignment inactive record.

Reversing an Assignment Termination

To reverse a termination, you must load the Assignment component with the ReverseAssignmentTerminationFlag attribute set to Y.

This example reverses an assignment termination.
METADATA|Assignment|WorkTermsAssignmentId(SourceSystemId)|SourceSystemId|SourceSystemOwner|ActionCode|ReasonCode|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|EffectiveLatestChange|ReverseAssignmentTerminationFlag
MERGE|Assignment|300100553121597|300100553121600|FUSION|ORA_EMPL_REV_TERMINATION||2022/05/02|4712/12/31|1|Y|Y

Ending an Assignment

To end date an assignment, you must load an inactive assignment update with an ActionCode of type EMPL_END_ASG starting from the end date + 1 day.

This example end dates an assignment.
METADATA|Assignment|ActionCode|AssignmentStatusTypeCode|AssignmentType|BusinessUnitShortCode|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|EffectiveStartDate|WorkTermsAssignmentId(SourceSystemId)|SourceSystemOwner|SourceSystemId
MERGE|Assignment|END_ASG|INACTIVE_PROCESS|E|Vision Corporation Enterprise|4712/12/31|Y|2|2022/07/03|SSI_0004H_WTERM_1201_2|HRC_SQLLOADER|SSI_0004H_WASGN_1201_2
Note:
  • It’s recommended to use an ActionCode of type EMPL_END_TEMP_ASG to end date a temporary assignment.
  • For temporary assignment loads, you can additionally use an active update on the same date for the suspended assignments. Additionally, you can load the active update in a separate DAT file.
  • You can use UserKeys (AssignmentNumber, WorkTermsNumber) or surrogateIds (AssignmentId, WorkTermAssignmentId) in the DAT file instead of SourceSystemIds (SSIDs) mentioned in the example.