Dimensions: Scheduled Lock...

The static issue, Scheduled locked and cannot be synchronized, appears when an employee submits a work code exception for a pay period that is locked or signed off in Dimensions. Schedules in Dimensions can not be updated via synchronization when a pay period in Dimensions has been locked or signed off.

A static issue is a system user alert that derives from a work code rule in this application. A static issue appears when the rule is triggered by the user. Once the period has been signed off or locked in Dimensions the static issue, Scheduled locked and cannot be synchronized, displays in this application if the user submits an exception during this period.

Severity Level controls in Setup define static issue behavior in this application, such as whether or not the issue triggers as a warning, or denies the transaction, or requires approval. Simply put, defining the static issue’s severity levels in this application will tell this system how to proceed when the issue appears. Static Issue severity levels are managed in the Static Issues area of the Codes section in Setup.

Once the schedule is locked in Dimensions, schedule updates are restricted. Changes must be made as a historical correction and managed using manual standard operating procedures.

USE CASE EXAMPLE:

Suppose an employee, David Abundiz, forgot to submit his overtime slip last week and the pay period is now locked. However, the overtime hours David earned must be logged in this application to qualify David when using the “Overtime Rule” to fill job vacancy opportunities. Sample scenarios are...

David handles the transaction with his manager. The severity level for the static issue is set to Warning in order to allow David to submit the time entry in this application. The time entry exists in this application for rule purposes only. To get paid David must square the process with his manager who will then proceed with David’s time entry from a historical correction standpoint in Dimensions. Essentially, David handles the time off for actual pay purposes with his manager.
David’s manager handles the missed time entry for pay purposes when David, the employee, attempts to submit the time entry in this application. David’s manager must approve the request and carry the historical corrections process in Dimensions. Severity level configuration options are:
- Deny Level One/Deny Level Two - the time entry is denied by this application when David submits the time entry request. David cannot submit this type of transaction on his own in this application and will need to contact his manager for support. The manager handles the request for David in this application for rule purposes and then handles the hours for pay in Dimensions.
- Convert to a Request if Denied - the time entry is denied but converted to a request for further review. David submits the request through this application. The manager sees and approves the request. The hours are logged upon approval. The manager completes the transaction for pay in Dimensions.

Static Issues display with work codes when activated using the following functions:

Add
Edit
Remove¹
Request Approval
Bidding
Switch with Rules:

Note: The static issue, Scheduled locked and cannot be synchronized, does not activate when using Fill By Rules, or using tasks, such as Auto-Assign, Auto-Hire, and Fix/Finalize. These components do not check for locked periods. Simply put, filling vacancies via Auto-Assign, Auto-Hire and so on are forward looking in time on non-locked periods. Auto Fix/Finalize tasks are typically in support of payroll preparation and would also occur in advance of sign-offs.