1. HCM Data Loading Business Objects
  2. Examples of Loading Time and Labor Event Actions

Examples of Loading Time and Labor Event Actions

An event action defines how to react to an event, for example, whether to recalculate time cards when a worker's job or location changes. This topic shows how to create event actions using HCM Data Loader.

Loading Event Actions

This example EventAction.dat file creates a single Event Action component, which is identified by its user key.

METADATA|EventAction|EventActionCode|EffectiveStartDate|EffectiveEndDate|EventActionName|EventActionTypeCode|LookbackTimeDefinitionCode|ActionSubmission|ProcessMode|AutoApprove
MERGE|EventAction|JobChangeAction|1950/01/01|4712/12/31|JobChangeAction|ORA_HWM_ACTION_TYPE_TC_RESUBMIT|12_MONTHS_AGO_MONTH_START_DATE|SYNC|MANUAL|Y

These rules apply:

  • To resubmit time cards, you must set EventActionTypeCode to ORA_HWM_ACTION_TYPE_TC_RESUBMIT.

  • The LookbackTimeDefinitionCode value identifies a time period before the action execution date. Time cards from this period are considered for resubmission. Use one of these values:

    • 3_MONTHS_AGO_MONTH_START_DATE

    • 6_MONTHS_AGO_MONTH_START_DATE

    • 12_MONTHS_AGO_MONTH_START_DATE

    For example, a job change is effective on 1st January 2018 and the time-card resubmission process runs on that date. If LookbackTimeDefinitionCode is 3_MONTHS_AGO_MONTH_START_DATE, then time cards from 1st October 2017 are considered for resubmission.

    ActionSubmission must be SYNC for time-card resubmission.

  • ProcessMode determines whether time cards are resubmitted automatically by the process or marked for resubmission but manually resubmitted. Set it to AUTO or MANUAL, as appropriate.

  • AutoApprove determines whether time cards are approved automatically after they're resubmitted. Valid values are Y and N.

Loading Event Action Criteria

The Event Action Criteria component associates an event action with a specific group of workers. This Event Action Criteria component is identified by its user key.

METADATA|EventActionCriteria|EffectiveEndDate|EffectiveStartDate|GUID|SourceSystemId|SourceSystemOwner|HCMGroupCode|EventActionCode|LegislativeDataGroupName
MERGE|EventActionCriteria|JobChangeAction|1950/01/01|4712/12/31|ABC_GRP

HcmGroupCode values are defined in the GRP_CODE column of the HWM_GRPS_VL table view and can be accessed using SQL. You can omit the Event Action Criteria component if the action applies to all workers.

You need the legislative data group name when you create an event action criteria that's referenced by an event action with a similar legislative data group.

Loading Event Group Actions

The Event Group Action component associates an event action with an event group. This Event Group Action component is identified by its user key.

METADATA|EventGroupAction|EventActionCode|EffectiveStartDate|EffectiveEndDate|EventGroupCode
MERGE|EventGroupAction|JobChangeAction|1950/01/01|4712/12/31|JobChangeEventGroup

Related Topics