Position actions
At the position level, all calculation types of salary, benefit, or cost 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_position_action_prepare_staging
. - The stored procedure to process staged data is
depm_integration_wb_benefitcost_position_action
. - The data is imported to:
- The DAT_BENEFITCOST_POSITION_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 position actions, you must also import benefit cost data and position data.
This table describes DAT_BENEFITCOST_POSITION_ACTION_STAGE:
Field | Required | Description |
---|---|---|
BenefitCostCode | Y | Unique BenefitCostCode identifier of the salary/benefit/cost
definition. 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. |
EffectiveDate | N | Effective start date for the benefit, cost, salary action. The format is YYYY/MM/DD. Required for position actions if the date type in the benefit definition is Calendar Date or the action is one of these types:
When the date type in the benefit definition is Calendar Date, these rules apply:
When the date type in the benefit definition is not the Calendar Date, do 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. 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:
Do 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. |
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:
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 action. If the calculation type is YTDRanges, Value1 does not apply. Do not specify a value for Value1. Amount of the benefit, cost, salary action. If the calculation type is not YTDRanges, Value1 must 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 | N | Amount of the benefit or cost action. For the calculation type QuantityXRate:
If Value2 is not specified, then 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. Only valid for these calculation types:
Valid for actions on hourly positions. |
FTE | N | Full time equivalent value. Only valid for these calculation types:
Valid for actions on annual, monthly, and hourly positions. If FTE is specified, it must be greater than 0. There is no default value. |