1. HCM Data Loading Business Objects
  2. Example of Loading a Contract Extension

Example of Loading a Contract Extension

You supply the Contract component of the Worker object when creating workers, if appropriate.

However, you can load a contract extension for a worker who has a contract. This topic shows how to load a contract extension using HCM Data Loader.

Loading a Contract Extension

You can use HCM Data Loader to give an existing worker a contract extension. Keep these rules in mind:

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

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

  • The EffectiveStartDate value is the start date of the extension period. This value must be the projected end date of the last contract period, plus one day, meaning no gaps are permitted between contract periods.

  • The EffectiveEndDate value must be the end of time if this contract record is the latest record. It must not be the contract end date.

  • You can specify the extension period by updating the ExtensionPeriod and ExtensionPeriodUnits attributes of the Contract component.

    In this case, the new projected end date is calculated automatically.

  • The value of the ActionCode attribute on the Employment Terms and Assignment components must be associated with the action type EMPL_CONTRACT_EXTN.

  • You can't delete a contract extension record using HCM Data Loader.

The following example shows how to load the Employment Terms, Assignment, and Contract components for a contract extension.

METADATA|WorkTerms|SourceSystemOwner|PersonId(SourceSystemId)|PeriodOfServiceId(SourceSystemId)|SourceSystemId|AssignmentId|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|EffectiveLatestChange|ActionCode
MERGE|WorkTerms|FUSION|300100162474267|300100162474475|300100162474482|300100162474482|2011/01/31|4712/12/31|1|Y|CONTRACT_EXTENSION
METADATA|Assignment|SourceSystemOwner|PersonId(SourceSystemId)|PeriodOfServiceId(SourceSystemId)|WorkTermsAssignmentId(SourceSystemId)|SourceSystemId|AssignmentId|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|EffectiveLatestChange|ActionCode
MERGE|Assignment|FUSION|300100162474267|300100162474475|300100162474482|300100162474487|300100162474487|2011/01/31|4712/12/31|1|Y|CONTRACT_EXTENSION
METADATA|Contract|SourceSystemOwner|PersonId(SourceSystemId)|PersonNumber|AssignmentId(SourceSystemId)|SourceSystemId|ContractId|EffectiveStartDate|EffectiveEndDate|ExtensionPeriod|ExtensionPeriodUnits
MERGE|Contract|FUSION|300100162474267|960000000000615|300100162474482|300100162474490|300100162474490|2011/01/31|4712/12/31|100|D
Tip: If you want to correct an existing contract row (for example, contract extension), ensure that you pass the assignment record and the corresponding contract record in the same DAT file.You can only correct the contract end date and contract duration attributes for the latest contract record (second extension record in the table). This is because any changes that you make to these attributes in the initial records aren't propagated to the subsequent future records.