Examples of Loading Action Reasons
Action reasons, which are optional, provide additional information about an action. For example, the reason for promoting a worker may be good performance or seniority. This topic shows how to load action reasons using HCM Data Loader.
Creating Action Reasons
This example ActionReasons.dat file creates two Action Reasons components. The components are identified by source keys.
METADATA|ActionReasons|SourceSystemOwner|SourceSystemId|ActionReasonCode|ActionReason|StartDate|EndDate
MERGE|ActionReasons|VISION|AR_VISION_PERF|VISION_PERF|Performance|2000/01/01|4712/12/31
MERGE|ActionReasons|VISION|AR_VISION_TXFR|VISION_TXFR|Internal Transfer|2000/01/01|Loading Translated Action-Reason Names
Supply action-reason names in the language of the user who's loading them. You supply an ActionReasonsTranslation.dat file to translate action-reason names into other enabled languages once the action reasons exist. This example translates the names of existing action reasons. The Action Reasons components are identified by their source keys.
METADATA|ActionReasonsTranslation|SourceSystemOwner|SourceSystemId|ActionReason|Language
MERGE|ActionReasonsTranslation|VISION|AR_VISION_PERF|Accomplissement|FR
MERGE|ActionReasonsTranslation|VISION|AR_VISION_TXFR|Transfert interne|FRDeleting Action Reasons
You can delete Action Reasons components using HCM Data Loader. This example ActionReasons.dat file deletes two action reasons. It identifies the components using source keys.
METADATA|ActionReasons|SourceSystemOwner|SourceSystemId
DELETE|ActionReasons|VISION|AR_VISION_PERF
DELETE|ActionReasons|VISION|AR_VISION_TXFR