Assignment actions

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

These calculation types can be assigned to the position assignment only one time in a specific time period.

  • PremiumPercentBaseRate
  • PremiumPercentPremiumRate
  • PremiumAmountBaseRate
  • PremiumAmountPremiumRate

The table is WFB_AssignmentAction.

The Assignment Action business object is used in these dimensions and cubes:

  • Dimensions
    • Workforce Budgeting Action (WBDACTION)
  • Cubes
    • WFB Calculation (WBCCALCULATION)
    • WFB Calculation Order (WBCCONFIG_ACTION_ORDER)
    • WFB Scenario Configuration (WBCCONFIG_SCENARIO)

The Assignment actions business object is related to these business objects:

  • Entity
  • Organization
  • Salary, Benefit, Cost Definition
  • Position
  • Employee

This table describes the Assignment Actions business object:

Field Type Required Description
BenefitCostCode nvarchar (200)

NOT NULL

Y Unique ID of the Benefit or Cost in the Salary, Benefit, Cost Definition business objects.

The related table is Benefit Cost, the field is BenefitCostCode.

PositionID [nvarchar] (200)

NOT NULL

Y Unique position ID in the Position business object.

The related table is Position, the field is PositionID.

EmployeeID [nvarchar] (200)

NOT NULL

Y Unique employee ID in the Employee business object.

The related table is Employee, the field is EmployeeID.

EffectiveStart [datetime]

NULL

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

A start date is required for assignment actions.

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

  • If the user does not specify a start date, the start date is set to the assignment start date.
  • If the user specifies a start date, 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, the user should not specify a start date. The start date is set based on the date type in the benefit definition and the position/employee attributes.

EffectiveEnd [datetime]

NULL

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

Do not specify an EffectiveEnd for these calculation types:

  • BaseRatePercentChange
  • BaseRateAmountChange
  • PercentOfAnnualized including dated values
  • 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 [float] (53)

NULL

N

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 and the definition does not have dated values:

  • 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 [float] (53)

NULL

N Amount of the benefit or cost action.

For the calculation type QuantityXRate that does not have dated values:

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

Not used by other calculation types.

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

Hours [float] (53)

NULL

N Valid for these calculation types:
  • PremiumPercentBaseRate
  • PremiumPercentPremiumRate
  • PremiumAmountBaseRate
  • PremiumAmountPremiumRate

Valid for actions on hourly positions.

FTE [float] (53)

NULL

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.