Assignment actions

At the assignment position level, all calculation types of benefit, cost, salary actions can be assigned.

The process uses these tables and stored procedures:

  • The staging table is DAT_BENEFITCOST_POSITION_ACTION_STAGE.
  • The stored procedure to validate staged data is depm_integration_ wb_benefitcost_assignment_action_prepare_staging.
  • The stored procedure to process staged data is depm_integration_wb_benefitcost_assignment_action.
  • The data is imported to:
    • The DAT_BENEFITCOST_ASSIGNMENT_ACTION_TRANSFORMED table.
    • The WBCCONFIG_ACTION_ORDER cube.

The output tables are:

  • ATT_WBCCONFIG_ACTION_ORDER contains configuration cube data.
  • DIM_WBDACTION_ELEMENTS contains action placeholder elements.
  • DIM_WBDACTION_PARENTS contains parent/child relationships for the WBDACTION dimension.

If you are importing assignment actions, you must also import benefit cost data, position data, and employee data.

This table describes DAT_BENEFITCOST_ASSIGNMENT_ACTION_STAGE:

Field Required Description
BenefitCostCode Y Unique BenefitCostCode identifier of the salary/benefit/cost definition from Benefit Cost table.

The related field is BenefitCostCode in the DAT_BENEFITCOST_STAGE

table.
PositionIdentifier Y Valid position identifier.

The related field is Identifier in the DAT_ATCDATA_POSITION_STAGE table.

EmployeeIdentifier Y Valid employee identifier.

The related field is Identifier in the DAT_ATCDATA_EMPLOYEE_STAGE table.

EffectiveDate N Effective start date for the benefit, cost, salary action.

The format is YYYY/MM/DD.

A start date is required for assignment actions.

When the date type in the benefit definition is Calendar Date, these rules apply:

  • If a start date is not specified, the start date must be set to the assignment start date.
  • If a start date is specified, it must be less than or equal to the assignment start date and greater than or equal to the assignment end date.

When the date type in the benefit definition is not CalendarDate, do not specify a start date. The start date is set based on the date type in the benefit definition and the position/employee attributes.

EndDate N Effective end date for the benefit, cost, salary action.

The format is YYYY/MM/DD.

Do not specify an EffectiveEnd for these calculation types:

  • BaseRatePercentChange
  • BaseRateAmountChange
  • PercentOfAnnualized
  • FlatAmount that applies for a single period (CalculationMethod = 0)
  • QuantityXRate that applies for a single period (CalculationMethod = 0)

The end date of the action must be greater than or equal to the start date of the action.

Value1 N Amount of the benefit, cost, salary action.

If the calculation type is YTDRanges, do not specify a value for Value1. Value1 does not apply to YTDRanges.

If the calculation type is not YTDRanges, Value1 must be specified.

If Value1 is not specified, it defaults to Value1 from the benefit/cost definition.

If Value1 is specified, it must be greater than 0.

Value2 N Amount of the benefit or cost action.

For the calculation type QuantityXRate, Value2 must be specified.

If Value2 is not specified, it defaults to Value2 from the benefit and cost definition.

If Value2 is specified, it must be greater than 0.

Not used by other calculation types.

Hours N Number of hours assigned.

Valid for these calculation types:

  • PremiumPercentBaseRate
  • PremiumPercentPremiumRate
  • PremiumAmountBaseRate
  • PremiumAmountPremiumRate

Valid for actions on hourly positions.

FTE N Full time equivalent value.

Valid for these calculation types:

  • PremiumAmountBaseRate
  • PremiumPercentBaseRate
  • PremiumAmountPremiumRate
  • PremiumPercentPremiumRate

Valid for actions on annual, monthly, and hourly assignments.

There is no default value.

If FTE is specified, it must be greater than 0.