Dimensions Accruals
Customers using Dimensions for Accruals must manage
accruals in Dimensions the single source of record. Only Dimensions
pay codes of unit type Hours are
supported; for example, when adding a vacation requests for accrual
validation.
Work codes in this application must be mapped to pay codes in
Dimensions. The integration handles accrual balance validation between
the applications by way of API calls. Accruals are checked using
Dimensions Accrual Policy Business Rules. This means, when an employee
submits a vacation request in this application, a call is made to
Dimensions for accrual balance validation. If the person fails an
accrual policy business rule in Dimensions, the static issue:
Exceeded Accrued Hours for this work status is overwritten by the This
edit cannot be made, <pay codename> balance on <date> is <hours>,
overdrawn by <hours>. Maximum overdrawn <hours>.
Dimensions accruals require work codes and pay code connections
between applications and accrual policy configuration in Dimensions.
Work Codes used for the purpose of accruals must ensure that the
work code property No Roster Impact is not selected.
The integration push does not include records with No Roster
Impact when included in the properties setup area of the work code.
Cascading accrual validations is only available for customers
using Dimensions. Additionally, applicable dynamic issues display
when activated if the time entry supplied by the person fails to meet
that dynamic issue’s criteria.