Acumatica will not create or update an Organizational Employee record unless it has both an Occupation and an Employee Class. These two fields are checked on every employee write, no matter which sync scopes are turned on. The Employee Class value also has to match a class that is already configured in Acumatica; a code that is only spelled correctly in the source system is not enough. When either field is blank in the source data, or the Employee Class value does not match anything Acumatica has on file, the sync leaves the entire employee record out of that run rather than send Acumatica incomplete or unrecognized data.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Occupation is required. | Write (Arcoro to Acumatica) | Checked on every employee write, regardless of which scopes are enabled. The employee's Occupation field is blank in the source data. This check shares a single pass or fail result with several other required-field checks (Social Security Number, Employee Id, First Name, Last Name, Birth Date, and address); if any one of them fails, the whole employee is skipped, and more than one message may appear together. | The entire employee record is skipped for this run. Nothing for that employee is written. | Add an Occupation value to the employee record in the source system. |
| Employee Class is Required. | Write (Arcoro to Acumatica) | Checked on every employee write, regardless of which scopes are enabled. The employee's Employee Class (Certified Class) field is blank in the source data. This check shares the same pass or fail result described above, alongside the other required-field checks. | The entire employee record is skipped for this run. Nothing for that employee is written. | Add an Employee Class value to the employee record in the source system. |
| Employee Class '[employee class code]' not found. Acumatica requires a valid Employee Class to create or update an Organizational Employee. Please ensure an Employee Class has been assigned and run the Sync again. | Write (Arcoro to Acumatica) | Checked after the required-field validation above has already passed (so the Employee Class value is not blank), before the employee is matched or created in Acumatica. The employee's Employee Class value does not match the code of any Employee Class Acumatica returned during preload. The comparison is case sensitive, and it does not exclude inactive classes; whatever Acumatica returns for Employee Classes is what gets compared, with no active-only filter applied. | The entire employee record is skipped, before any organizational or payroll data is written for that employee. | In Acumatica, confirm an Employee Class exists with that exact code and case, or correct the value in the source system to match an existing Acumatica Employee Class exactly. |
Confirming the Error
- Confirm the connector for this sync execution is Acumatica before matching on message text. "Occupation is required." and "Employee Class is Required." are short, generic sentences that could also appear in another provider's error list.
- Open the Sync History screen and locate the sync execution in question.
- Find the step for the Acumatica connector, then the Employees entity row within that step.
- Check the Employees row's Errors, Warnings, Information, Failures, Added, Updated, and Unchanged columns to see whether any records were flagged as Errors.
- Open the entity's error list and match on the fixed wording of the sentence, for example "is required" or "not found", not on the value shown in quotes, since that value is the employee class code specific to one employee.
- Note the employee identifier shown alongside the message, and for the not-found message, the Employee Class code quoted in it, so the fix can be applied to the correct record.
- If the not-found message appears against many or all employees in the same run rather than a single employee, note that as well. It points to a problem with the Employee Class data Acumatica returned, not to one employee's record, and belongs under escalation below.
Resolving the Error
Occupation is Required
- In the source system, open the employee record and check the Occupation field.
- Add a value to the Occupation field.
- Save the change in the source system and run the sync again.
- Confirm the fix worked by checking that the employee no longer appears in the Employees row's Errors list for this message.
Employee Class is Required
- In the source system, open the employee record and check the field that supplies Acumatica's Employee Class (the employee's certified class).
- Add a value to that field.
- Save the change in the source system and run the sync again.
- Confirm the fix worked by checking that the employee no longer appears in the Employees row's Errors list for this message.
Employee Class Not Found in Acumatica
This is a different problem from the blank-field message above. Here, the employee record already has a value; that value just does not match anything Acumatica has configured. Deciding the fix means checking Acumatica, not just the source record.
- Note the Employee Class code quoted in the message.
- In Acumatica, check whether an Employee Class already exists with that exact code, matching case.
- If no matching Employee Class exists in Acumatica, either add one there, or correct the value in the source system so it matches an existing Acumatica Employee Class exactly, including case.
- If an Employee Class with that exact code does already exist in Acumatica and the message still occurs after a new sync, escalate rather than continuing to edit source data.
- Run the sync again and confirm the employee no longer appears in the Employees row's Errors list for this message.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The Employee Class not-found message appears against many or all employees in the same sync run, rather than one. This points to a problem with the Employee Class data returned from Acumatica during setup, not to any single employee's record, and is outside what Tier 1 can correct in the source system.
- You confirm an Employee Class with the exact quoted code, matching case, already exists in Acumatica, yet the message still occurs after a new sync.
- You cannot edit the Occupation or Employee Class field in the source system itself.