Module Navigation

Troubleshooting CMiC Integration Error: Union, Classification, Workers Comp, Occupation

Before Arcoro sends an employee to CMiC, it checks a set of employee fields against rules CMiC requires: occupation/trade, workers compensation code, and union or union local. All of these checks run for every employee, one after another, and every failure is recorded before Arcoro decides what to do. If any one of them fails, the entire employee record is withheld from CMiC for that sync run. Because every check runs regardless of earlier failures, one employee can show several of these messages at once in the sync log.

Two of these checks (occupation and union) compare the employee's value against a list CMiC itself already has on file, not against a fixed set of rules. If that list does not contain a matching value, or the matching value itself does not fit CMiC's field size, the record is withheld even though nothing changed on the Arcoro side.

Error Messages

Message textDirectionOccurs whenOutcomeFix
Employee Occupation/Trade is required. Employee will not be sent to CMiC.Write (Arcoro to CMiC)The employee's Occupation/Trade value is blank in Arcoro.Record skippedEnter an Occupation/Trade value for the employee in Arcoro.
The Employee Occupation '[occupation value]' could not be matched with any existing value in CMiC. This record will not be processed. Correct data in source system and run the sync again.Write (Arcoro to CMiC)The employee has an Occupation/Trade value in Arcoro, but its code does not match any trade code CMiC returned during setup.Record skippedConfirm the trade code exists in CMiC; if it does, correct the value in Arcoro to match it exactly, otherwise ask the CMiC administrator to add it.
Employee Workers Compensation Code is required. Employee will not be sent to CMiC.Write (Arcoro to CMiC)The Workers Compensation Code scope is turned on for this sync, and the employee's Workers Compensation Code in Arcoro has no digits (blank or non-numeric).Record skippedEnter a numeric Workers Compensation Code for the employee in Arcoro.
Workers compensation code [numeric code] exceeds the maximum length of 4 characters supported by the provider and will not be synced.Write (Arcoro to CMiC)The Workers Compensation Code scope is turned on, and the employee's Workers Compensation Code, after non-digit characters are stripped, is more than 4 digits long.Record skippedShorten the employee's Workers Compensation Code in Arcoro to 4 digits or fewer.
Employee's union and/or union local exceeds the maximum length of 4 characters supported by the provider and will not be synced.Write (Arcoro to CMiC)The Union or Union Local scope is turned on, and the CMiC union code that matches the employee's union (or, if union does not match, union local) is more than 4 characters long.Record skippedAsk the CMiC administrator to shorten that union's code in CMiC, or assign the employee to a union whose CMiC code fits 4 characters.

Confirming the Error

  1. In Sync History, open the sync execution for the run in question.
  2. Open the step that runs the CMiC connector.
  3. Find the Employees row for the People entity. Check the Errors column count for that row.
  4. Open the errors list for that entity row.
  5. Match each error to a message in the table above using the fixed part of the sentence, not the value in quotes or brackets, since the quoted value is specific to the employee.
  6. Read the entire errors list for the employee, not just the first entry. Because these checks all run together, the same employee can have more than one of these messages, plus messages from other families, in the same list.

Resolving the Error

Employee Occupation/Trade is Required

  1. In Arcoro, open the employee record and set the Occupation/Trade field to a value.
  2. Run the sync again and confirm the message no longer appears for that employee.

The Employee Occupation could not be matched with any existing value in CMiC

  1. Check the trade or occupation code lists in CMiC for the code the employee's Occupation/Trade value is supposed to represent. The comparison is on the code only, is case sensitive, and depends on the trade codes CMiC returned the last time the connector's setup ran.
  2. If the code already exists in CMiC, correct the Occupation/Trade value in Arcoro so it matches that code exactly, including letter case.
  3. If the code does not exist in CMiC, have the CMiC administrator to add it in CMiC.
  4. Run the sync again and confirm the message no longer appears for that employee.

Employee Workers Compensation Code Is Required

  1. In Arcoro, open the employee record and set the Workers Compensation Code field to a numeric value.
  2. Run the sync again and confirm the message no longer appears for that employee.

Workers Compensation Code Exceeds the Maximum Length

  1. In Arcoro, open the employee record and shorten the Workers Compensation Code to 4 digits or fewer.
  2. Run the sync again and confirm the message no longer appears for that employee.

Employee’s Union And/or Union Local Exceeds the Maximum Length

  1. In Arcoro, check which value is set on the employee, Union or Union Local, since either one alone can trigger this message.
  2. Ask your CMiC administrator to check the code CMiC has on file for that union. If the code is longer than 4 characters, the administrator needs to shorten it in CMiC, or the employee needs to be moved to a different union whose CMiC code fits.
  3. Run the sync again and confirm the message no longer appears for that employee.

When to Escalate

If any of the following occur, you may need to reach out to Arcoro support for additional assistance.

  • You confirm the trade code, union code, or workers compensation code already looks correct in both Arcoro and CMiC, and the message still occurs.
  • You cannot tell whether the Occupation/Trade or union values Arcoro is comparing against actually came from CMiC's current data, for example if CMiC data was recently changed but the connector has not run its setup step since.
  • The same employee keeps failing after you has made the correction described above and re-run the sync at least once.
Was this article helpful?
0 out of 0 found this helpful