Module Navigation

Troubleshooting Sage 100 Integration Error: Org Structure

Every employee sent to Sage 100 must have a Position value that Arcoro can match to a Position already set up in Sage 100. Arcoro checks the employee's Position value against the list of Positions it read from Sage 100 before the sync started. When there is no exact match, Arcoro cannot tell Sage 100 which Position to assign, so it stops processing that one employee and moves on to the next. Nothing else about the employee is sent until this is fixed.

Error Messages

Message textDirectionOccurs whenOutcomeFix
A match for the position '[employee's Position value]' was not found in HH2. The employee will not be processed. Correct the data and run the sync again.Write (Arcoro to Sage 100)The employee has a Position value in Arcoro, and that value does not exactly match the Name (or Code, if a Position has no Name) of any active Position that Arcoro read from Sage 100 before the write started.Record skipped. The employee is not created or updated in Sage 100 at all.Make the employee's Position in Arcoro match an existing Sage 100 Position exactly, or create the missing Position in Sage 100.

A blank Position value on the employee produces a different message (an empty-field error) earlier in the same write and is not covered by this article. This message only fires when the employee has a Position value that fails to match.

Confirming the Error

  1. Open the sync execution in question in Sync History.
  2. Open the step for the Sage 100 connector.
  3. Find the Employees entity row for that step.
  4. Check the Errors column for that row. If it is non-zero, open the errors list for the Employees entity.
  5. Match on the fixed part of the sentence: "was not found in HH2. The employee will not be processed." Do not match on the quoted Position value, since that value is different for every account and every Position.
  6. If you are looking for a missing Department instead of a missing Position, check the Warnings column, not Errors. A separate warning reports when a Pay Group, Skill, or Union value on the employee does not match Sage 100, and department name issues are reported on the Department entity itself, not on the Employee entity. Neither of those uses this Errors-list message, so if the issue is about a Department, this article does not apply.
  7. A non-zero Failures count for this entity is a different problem. This message is logged as an Error, not a Failure, so Failures being non-zero points to something else (for example, a connection or configuration problem) and is not explained by this article.

Resolving the Error

The Position Exists in Sage 100, but the Employee’s Value Does Not Match It

  1. In Arcoro, open the employee record and note the exact Position value on file, including spelling, spacing, and capitalization. The match against Sage 100 is exact, so extra spaces or a different capitalization will cause this error even if the Position looks the same to a person.
  2. Compare that value to the Position list in Sage 100. Confirm the exact Name of the Position record in Sage 100. If the Position has no Name set in Sage 100, its Code is used instead.
  3. Correct the Position value on the employee in Arcoro, so it is character-for-character identical to the Sage 100 Position's Name (or Code, if it has no Name).

The Position Does Not Exist in Sage 100 at All

  1. Create the missing Position record in Sage 100.
  2. Confirm the new Position is active (not archived) in Sage 100, since archived Positions are not eligible for matching.

After either fix, re-run the sync and confirm the employee no longer appears in the Employees entity's Errors list, and that the employee row shows Added or Updated instead.

When to Escalate

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

  • The Position in Sage 100 visibly exists with a Name (or Code) that matches the employee's value exactly, character for character, and the error still fires. This points at a Position that failed to load during preload, most likely because Sage 100 has two Position records that collide on the same Name or Code. See Sage 100: Preload or lookup data setup failure and ask a developer to check for a duplicate Position preload error on the same sync run.
  • The error text in the log does not match the fixed sentence in the table above.
  • The Employees entity shows a non-zero Failures count instead of, or alongside, Errors.
  • The error persists after you confirm the Position values match exactly on both sides.
Was this article helpful?
0 out of 0 found this helpful