Examples of Loading Actions

Actions classify changes to data such as employment and compensation records. When you create or update a record, the action value specifies the reason for the change. For example, the associated action for an assignment change may be promotion or transfer.

Action reasons, which are optional, provide additional information about a change. The Action Reason Usage component of an Actions object specifies the relationship between an action and an existing action reason. This topic shows how to load Actions objects and their Action Reason Usage components using HCM Data Loader.

Creating Actions

This example Actions.dat file creates an Actions component and associates it with an Action Reason Usage component. Both components are identified by source keys.

METADATA|Actions|SourceSystemOwner|SourceSystemId|ActionCode|ActionName|ActionTypeCode|StartDate|EndDate
MERGE|Actions|VISION|VISION_ACT_PROM|VISION_PROM|Vision Promotion|EMPL_PROMOTION|2000/01/01|
METADATA|ActionReasonUsage|SourceSystemOwner|SourceSystemId|ActionCodeId(SourceSystemId)|ActionReasonId(SourceSystemId)|StartDate|EndDate
MERGE|ActionReasonUsage|VISION|VISION_PROM_PERF|VISION_ACT_PROM|VISION_PERF|2000/01/01|

Loading Translated Action Names and Descriptions

Supply action names and descriptions in the language of the user who's loading them. You supply an ActionsTranslation.dat file to translate action names and descriptions into other enabled languages once the actions exist. This example ActionsTranslation.dat file translates an action name and its description. The action is identified by its source key.

METADATA|ActionsTranslation|SourceSystemOwner|SourceSystemId|Language|ActionName|Description
MERGE|ActionsTranslation|VISION|ACT_VISION_PROM|FR|Performance|Changement est survenu en raison de la performance des employes