Troubleshooting - FAQs

How do I fix invalid timebands created by missing/erroneous clock data

If Leave was not added to an Actual Pay for an employee that uses clocks, you need to check the timebands that were created when you ran Process Clock Data.

If the start or end time look incorrect...change them
If the timeband doesn't look like it should even be there....delete it

Once you've manually corrected the worked timebands re-run Process Clock Data.

How do I see where a timeband came from in Daily View?

Use Customise Columns and bring in the column called "TimeBand Source".

Roster Timeband Source

When viewing Rosters the following timeband source identifiers are applied

Roster Timeband Source	Details
M. Manual entry	This source is applied to timebands that are: Manually entered into Daily View Originally derived from a Tour, Shift override or Timeband override or import file and then manually edited.
I. Import	This source is applied to timebands that where created after running Import Employee Timebands
B. One-off timebands override	This source is applied to timebands that were derived from an Employee Timeband Override that has no Frequency specified (i.e. null or 0)
Y. Cyclic timebands override	This source is applied to timebands that were derived from an Employee Timeband Override that has a Frequency specified (i.e. not null or 0)
S. One-off shift override	This source is applied to timebands that were derived from an Employee Shift Override that has no Frequency specified (i.e. null or 0)
C. Cyclic shift override	This source is applied to timebands that were derived from an Employee Shift Override that has no Frequency specified (i.e. not null or 0)
T. Tour shift	This source is applied to timebands that were derived from an Employee Tours.
L. Leave request	This source is applied to timebands that were derived from a ESS Leave request and is the only timeband for the day. Note: This timeband source is overriden if the leave timeband was present before you run Import Roster Timebands and as a result of running that process further timebands were created for the employee on that day.
<blank>	For any timeband created before LOP is enabled there will be no source value.

Actual Timeband Source

When viewing Actuals the following timeband source identifiers are applied

Actuals Timeband Source	Details
M. Manual entry	This source is applied to timebands that are: Manually entered into Daily View Originally derived from one of the timeband generation processes and then manually edited. (i.e. edited after running: Import Actual Timebands, Import Employee Timebands, Import Clock Data &/or Process Clock Data, Generate Non-Clock Data)
I. Import	This source is applied to timebands that were derived from the processes Import Actual Timebands or Import Employee Timebands.
C. Clock processing	This source is applied to timebands that were derived from the processes Import Clock Data &/or Process Clock Data.
A. Auto-generated on open	This source is applied immediately after opening the Actual pay for employees that do not use clocks. If Rostering is used - these timebands are copied directly from the Roster. If Rostering is not used - these timebands are derived from a Tour, Shift override or Timeband overrides.
N. Generate non-clocked data	This source is applied to timebands that were derived from the process Generate Non-Clocked Data.
L. Leave request	This source is applied to timebands that were derived from a ESS Leave request and is the only timeband for the day. Note: This timeband source is overriden if the leave timeband was present before you run one of the T&A processes for example Generate non-clocked data and as a result of running that process further timebands were created for the employee on that day.
<blank>	For any timeband created before LOP is enabled there will be no source value.

What happens to existing Leave requests that get changed in ESS after the cut-off date

Any changes required after the cut-off time must be performed manually through Daily View (or through Transaction View if the Roster/Actuals have already been exported to Payroll).

What happens to leave requests for employees using Group 2 TimeSheets

Prior to Timesheet generation,
- LOP will add the leave to both open roster and open actuals
On Timesheet generation,
- Any approved leave in the roster will be pulled through to the timesheet and be visible in the timesheet in the information section at the bottom of each timesheet day.
- Full day leave will replace any worked timebands for the day in the timesheet.
- Partial day leave will not appear as timesheet timebands - worked timebands will not be present during the partial leave period away for.
- Unapproved leave will not affect worked timebands, but will be visible in the timesheet in the information section at the bottom of each timesheet day.
If the Timesheet has not yet been exported,
- LOP will add the leave to both the open roster and open actuals.
- Any approved leave in the roster will be shown in the timesheet in the information section at the bottom of each timesheet day.
- Approved full day leave will replace any worked timebands in the timesheet.
- Approved partial day leave will not appear as timesheet timebands - worked timebands will not be affected by the process of partial leave approval.
- Unapproved leave will not affect worked timebands, but will be visible in the timesheet in the information section at the bottom of each timesheet day.
On Timesheet export,
- Any leave present in the roster and actuals during the timesheet period will not be exported as rows in the export file - LOP has ensured that approved leave is already present in the actuals, so it is not necessary to transfer the leave back into the actuals on import.
If the Timesheet has already been exported, ESS does not allow you to apply for leave in this period. Therefore, enabling LOP makes no change to how timesheet adjustments are managed by your organisation.

What happens if I close a Roster or Actual Pay before the cut-off and a leave request for that period is approved

An Employee Leave Request record is created with Module "T" but no timeband will be created. Because it is flagged as module "T" you wont be able to process this in Payroll either. This means you will need to manually add a Leave transaction to Payroll.

What is the difference between "Roster" and "Derived Roster"

"Roster" is what is visible in Daily View for the open Roster pay sequence also called the "current roster"

"Derived Roster" is what comes from the Employee's Tour, Shift-Override, Timeband Override or in other words the roster that applies immediately on opening the Roster pay sequence and before running Import Roster Timebands or manually editing timebands in Daily View

Why has leave not gone into an open Roster/Actual pay?

This may be caused by the following:

The employee doesn't have an Employee Leave Request record for the period relating to the leave request.
The employee doesn't have a valid Leave Request Settings record linked to their Employee Leave Request record.
The employee doesn't have a valid Leave Approval Settings record linked to their Employee Leave Request record.
The employee doesn't have a roster (i.e. nothing in either Tours, Shift Override or Time Override (be it cyclic or one-off))

Topic: 43735