Offsets and Other MVS Operations

When shift offsets exist, they can affect the following MVS operations as indicated:

  • If the source shift of a copy has offsets and the start time, end time, and shift details are flagged to be copied, the offsets are also copied. If the copy would extend a staffed shift beyond its existing start or end, and any existing offsets would wind up not at the start or end of the resized staffed shift, the copy operation will fail. For more information on the copy operation, see Copying Shift Details.
  • When a swap is performed, offsets are also swapped. For more information on the swap operation, see Swapping Shifts.
  • When an assigned employee is removed from a shift with offsets, the resulting unstaffed shift inherits the offsets from the original staffed shift. If offsets are defined, but weren’t configured for the original shift, a warning is issued (before the Remove operation completes) to ask you if you want to create offsets for the resulting shift.
  • If an auto-assign operation (using partial shift assignment) would create offsets in the middle of productive shift time (not the start or end of the shift), the operation will fail. For more information on the auto-assign operation, see Auto-Assignments.
  • When manually creating/editing shift assignments in the Schedule Details panel, the same rules for offsets as noted above apply:
    • Shift offset transition activities must be at the start or end of a shift.
    • If offsets are defined, but not configured for the original shift, a warning is issued before an operation completes to ask if you want to configure offsets for the resulting shift.
  • Offsets are only created for an the unstaffed shift resulting from a Book Off operation if offsets already existed in the staffed shift. If the IS_ENABLED parameter is set to TRUE, and the resulting unstaffed shift has no offsets (even though offsets are defined for the applicable Job/Team), a warning results. If only a portion of a staffed shift with offsets defined but unconfigured is being booked off and the portion (middle) doesn’t have any offsets, no offsets are created in the resulting unstaffed shift and no warning is issued. For information about the IS_ENABLED parameter, see the Registry Parameter Reference Guide.