The employee write step needs to match every incoming employee to exactly one employee record in Sage 300 CRE, using either the Social Security Number or the Employee ID. Both messages in this article fire during that matching step, before any employee data is written. One message means Sage 300 CRE already has two active employees that share the same Social Security Number. The other means the source system sent two updates in the same sync run for the same Sage 300 CRE employee. The affected employee is not synced in either case, but the fix happens in different systems, so it is important to tell the two apart.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Duplicate employees found in Sage 300 CRE matching on [match type]. The Sync requires that Sage 300 CRE contain a single employee matching and the employee will not be synced. | Arcoro to Sage 300 CRE (write) | Sage 300 CRE already contains more than one active employee with the same Social Security Number as the incoming record. This check always resolves to Social Security Number, so [match type] reads "SSN". | Record skipped | Correct the duplicate Social Security Number in Sage 300 CRE. |
| Duplicate Employee updates sent from source system matched by [match type] in Sage 300 CRE. Only the first source record will be synced. Source Employee: "[employee identifier]" will not be used. | Arcoro to Sage 300 CRE (write) | The same sync run sent more than one update for the same Sage 300 CRE employee. This check always resolves to Employee ID, so [match type] reads "Employee Identifier". | Record skipped | Remove the duplicate employee update from the source data in Arcoro. |
Match Type Values
- SSN: the employee's Social Security Number.
- Employee Identifier: the Employee ID field used to match employees between Arcoro and Sage 300 CRE.
Confirming the Error
- Open the sync execution and go to the Employees step for the Sage 300 CRE connector.
- Check the Errors column for the Employees entity. Both messages in this article log at Error severity, even though their names suggest a warning, so they always show up in Errors, not Warnings.
- Open the errors list for Employees and match on the fixed part of the sentence, not the quoted values. Both messages start with the word "Duplicate," so read past that word before deciding which one applies.
- If the sentence continues "employees found in Sage 300 CRE matching on," this is the Sage 300 CRE duplicate match message. The problem is already inside Sage 300 CRE.
- If the sentence continues "Employee updates sent from source system matched by," this is the duplicate source send message. The problem is in the batch of records sent from Arcoro during this run.
- Confirm the Added and Updated counts for Employees are lower than expected. Each occurrence of either message means one fewer employee was added or updated in that run.
Resolving the Error
Duplicate Employees Found in Sage 300 CRE Matching on [Match Type]
- Identify the employee's Social Security Number from the error, or from the Arcoro employee record if the message does not show it.
- In Sage 300 CRE, find all employees carrying that Social Security Number.
- Confirm which employee record is the one that should stay active. Correct or deactivate the other employee record in Sage 300 CRE so only one active employee carries that Social Security Number.
- Re-run the sync and confirm the employee no longer appears in the Errors list, and that Added or Updated increases for that employee.
Duplicate Employee Updates Sent From Source System Matched by [Match Type]
- Open the Arcoro source data (the sending system feeding this sync) and find every employee record mapped to the Employee ID named in the message.
- Confirm whether two separate source employees are incorrectly sharing the same Employee ID, or whether the same employee was submitted twice in the same batch.
- Correct the Employee ID mapping in the source so only one record targets that Sage 300 CRE employee per run.
- Re-run the sync and confirm the employee no longer appears in the Errors list, and that Added or Updated increases for that employee.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The error persists after only one active employee remains with that Social Security Number or Employee ID in the correct system.
- The message text in the log does not match either sentence in the table above.
- You see s that only one source employee exists for that Employee ID, so the duplicate send cannot be explained by the source data alone.
- Several employees show this error at once after a run that otherwise looked healthy, which can point to a matching or preload issue rather than genuine duplicate data.