Position actions

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

These are the calculation types:

  • PremiumPercentBaseRate
  • PremiumPercentPremiumRate
  • PremiumAmountBaseRate
  • PremiumAmountPremiumRate

These calculation types can be assigned to the position only one time in specific time period and cannot be inherited.

The table is WFB_PositionAction.

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

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

The Position Action business object is related to these business objects:

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

This table describes the Position Action business object:

Field Type Required Description
BenefitCostCode nvarchar (200)

NOT NULL

Y Unique ID of the benefit, cost, salary in the Salary, Benefit, Cost Definition business objects.

The related table is table 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.

EffectiveStart [datetime]

NULL

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

Required for position actions if the date type in the benefit definition is Calendar Date or the action is one of these types:

  • BaseRateAmountChange
  • BaseRatePercentChange
  • PremiumAmountBaseRate
  • PremiumPercentBaseRate
  • PremiumAmountPremiumRate
  • PremiumPercentPremiumRate

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 position start date.
  • If the user specifies a start date, it must be less than or equal to the start date of the position and greater than or equal to the end date of the position.

When the date type in the benefit definition is not the Calendar Date, the user should not specify a start date in the table. The start date is set based on the date type in the benefit definition and position attributes.

A start date is not required for position actions if the date type in the definition is other than CalendarDate and the position action is one of these types:

  • FlatAmount
  • QuantityXRate
  • PercentOfAnnualized
  • PercentOfPeriodic
  • YTDRanges

The user should not specify a start date in the staging table. The start date is set based on the date type in the benefit definition and position 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. The related table is BenefitCost, the field is CalculationMethod = 0.
  • QuantityXRate that applies for a single period. The related table is Benefit Cost, the field is 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 Amount of the benefit, cost, salary action.

If the calculation type is YTDRanges or the calculation type uses dated values, do not specify a value for Value1 as Value1 does not apply as the values are supplied from:

  • Benefit cost range business object for YTDRanges.
  • Benefit cost dated values business object for calculation types with dated values.

If the calculation type is not YTDRanges and the definition does not have dated values:

  • Value1 should be specified.
  • If Value1 is not specified, it defaults to Value1 from the benefit, cost, salary 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 is used for quantity.
  • Value2 must be specified.
  • If Value2 is not specified, then 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 Only valid for these calculation types:
  • PremiumPercentBaseRate
  • PremiumPercentPremiumRate
  • PremiumAmountBaseRate
  • PremiumAmountPremiumRate

Valid for actions on hourly positions.

FTE [float] (53)

NULL

N Full time equivalent value.

Only valid for these calculation types:

  • PremiumAmountBaseRate
  • PremiumPercentBaseRate
  • PremiumAmountPremiumRate
  • PremiumPercentPremiumRate

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

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

There is no default value.