Dimensions: Scheduled Lock...

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

A static issue is a system user alert that derives from a wok code rule in this application. The static issue is shown when the rule is triggered by the user. In this case, the application checks whether the period has been signed off or locked in Dimensions, if True, then the static issue displays in this application and handled via Severity level controls set in Setup > Codes > Static Issues.

Severity controls allow users to define how to process a static issue when triggered, in this case how to process exceptions in this application when the period has been locked or signed off in Dimensions. In Dimensions once the schedule is locked, schedule updates are restricted and changes must be made as a historical correction and managed via manual standard operating procedures.

For example, suppose an employee, David Abundiz, forgot to submit an overtime slip last week and the pay period is now locked. However, the overtime hours David earned must be reflected in this application because it affects his standing in the ‘Overtime Staffing Rules’ used to fill job vacancies. Using severity levels in this application you can best define how to proceed. For instance:

Scenario 1:The employee handles the time off for pay with his manager. In this case configure severity levels for the static issue to allow David to submit the time entry, receive a static issue severity level of type Warning which means the time entry is in this application for rule purposes only. To get paid David must square the process with his manager who then proceeds with David’s time entry from a historical correction standpoint through Dimensions.
Scenario 2: The employee’s manager handles the missed time entry for pay when the employee submits the time entry in this application. In this case configure severity levels for the static issue to prevent David from submitting the time entry or configure to submit the time entry in request mode. In either case, the manager must approve the request and carry the historical corrections process through Dimensions.

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

Add
Edit
Remove¹
Request Approval
Bidding
Switch with Rules:

For reference, 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. Filling vacancies via Auto-Assign, Auto-Hire and so on are forward looking on non-locked periods. Auto fix/Finalize tasks are typically in support of payroll preparation and would also occur in advance of sign-offs.