...
Error Code
...
Description
...
These are some of the common Labor Sync Error messages that your technicians may receive when syncing their devices.
| Error Message | Description | Fix |
|---|
| A valid labor rate does not exist for this position/pay code or department/position/pay code combination. | This |
particular is saying that | displays when the labor rate group combination assigned to the Customer is not set up with the pay code the |
Tech | technician was using. Labor Rate Groups must be configured with the proper combination of position, department, and pay code |
on | in order for Labor to be transacted successfully. If the |
Tech | technician uses one of these pay codes that has not been configured correctly they may see this particular error message preventing them from syncing. |
| Adding the appropriate Labor Rate Group combination will resolve this sync error. |
LaborExpense transaction XXXXXX failed with error: | The service call entered is either missing or closed. Enter another service call ID. | This |
particular labor | error displays when there is |
due to | stale data on the device. If a |
Technician | technician is getting this error, the back office has likely deleted or closed the |
Service Call Technician | technician is trying to enter labor towards. |
| A DELETE DATA from the device should clear this old data from the device and resolve this sync error. |
LaborExpense transaction XXXXXX failed with error: | This batch is marked to be committed and cannot be edited. | This |
particular is due to being | is marked for processing Payroll Posting. |
| The TimeTrack or Payroll batch will need to be unmarked in order for the |
Technician | technician to be able to sync successfully. |
LaborExpense transaction XXXXXX failed with error: | The fiscal period for this date is not part of a fiscal year. Enter a new date. | This |
particular Technician | technician entering a Labor transaction that has a “week-ending” day in a fiscal year that is not currently open. This is a common error that occurs for technicians in the last week of the year that is due to the upcoming Fiscal Year not being open yet. |
| To check if the current or next fiscal year is open, go to Microsoft Dynamics GP > Tools > Setup > Company > Fiscal Periods to open the Fiscal Period Setup window.l Opening the Fiscal Period will allow the Technicians to sync this Labor successfully. |
LaborExpense transaction XXXXXX failed with error: | This cost code does not exist. Enter another code. | This |
particular | error is stating the Cost Code used in the transaction does not exist or |
isn’t matching up with | does not match the system data. This could translate to data mismatches or stale middle-tier data. |
| Adding, updating, or re-Loading (Load Data) the Cost Code data for the transaction will resolve this issue. |
LaborExpense transaction XXXXXX failed with error: | Unknown error number XXXXX. | This particular error is due to the system ERROR tables (SVERRORS, WSERRORS, JCERRORS) being empty in the company database. |
TimeTrack | TimeTrack requires these tables to be populated. This can sometimes happen after a Signature upgrade where the Signature Utilities program was not launched as an Administrator. |
Re| | Re-populating these tables should resolve this issue and Technicians can resync to push the transactions through to the host system. |
