Arcoro syncs the employee's Facility value to HCSS, where it must match an existing Business Unit Code. If the Facility value on the employee does not match any Business Unit Code currently set up in HCSS, that employee cannot be synced. This check runs whenever the sync writes employee data, even if the connector's Facility scope is turned off for that run. The check only compares against Business Units that HCSS returned to Arcoro during that sync run, so it always reflects what exists in HCSS right now.

Error Message

Special Consideration

If the employee has no Facility value at all, this error will not trigger. An employee with a blank Facility value never triggers this error. Instead, the sync logs an informational message stating that no Business Unit was provided and that the default Business Unit of Manager was used for that employee. 

Confirming the Error

1. Click "Sync History" and open the sync record with the sync error from the Arcoro sync history screen.
2. Find the step for the HCSS connector and open the row for the Employees entity.
3. Check the Errors column for that row. A non-zero count means one or more employees failed validation, including possibly this check.
4. Open the errors list for that entity and match on the fixed part of the sentence, "No Business Unit was found on HCSS with a matching Code", not on the value inside the quotes.
5. Read the value inside the quotes as the exact Facility value that failed to match, already trimmed of leading and trailing spaces by the sync engine. Casing differences also do not cause this error, because the comparison ignores case. If this value is inside the quotes at all, the code genuinely does not exist in HCSS as a Business Unit for this connector, right now.

Resolving the Error

Confirm which system needs to change. Two valid paths exist:

Resolving in Core HR

1. In Core HR, search for and open the affected employee's profile.
2. Go to the employee's Demographic Information and change the employee's Facility value to a Facility name that matches an existing HCSS Business Unit Code exactly, ignoring case and ignoring leading or trailing spaces.
3. Re-run the sync after either change. Preload runs fresh on every sync execution, so a newly created Business Unit in HCSS or a newly corrected Facility value in Arcoro will be picked up on the next run with no additional wait.
4. Confirm the fix by repeating the steps in How to confirm. The employee's row should no longer show this error, and the entity row's Added or Updated count should include that employee.

Resolving in HCSS

1. In HCSS, create a Business Unit whose Code matches the Facility value already in the employee in Core HR.
2. Re-run the sync after either change. Preload runs fresh on every sync execution, so a newly created Business Unit in HCSS or a newly corrected Facility value in Arcoro will be picked up on the next run with no additional wait.
3. Confirm the fix by repeating the steps in How to confirm. The employee's row should no longer show this error, and the entity row's Added or Updated count should include that employee.

When to escalate

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

• If the Business Unit Code already exists in HCSS exactly as shown in the error, and the error still occurs after a fresh sync run.
• The error appears for a large number of employees at once immediately after a change on the HCSS side, which may point to a broader Business Unit setup issue in HCSS rather than a single employee's data.