Module Navigation

Troubleshooting Sage 300 Integration Error: Compensation, Pay Rate, Pay Group, Pay Frequency

This family covers two different parts of the Sage 300 CRE sync. The first part is employee compensation, where the employee's pay rate and pay type are sent from Arcoro out to Sage 300 CRE through HH2. The second part is Pay Group and Pay Frequency, which are lookup lists read in from Sage 300 CRE through HH2 and used to populate pay group and pay frequency options. A problem in either direction can stop the affected record, or in two cases, the entire sync run, from completing.

Error Messages

Message textDirectionOccurs whenOutcomeFix
A compensation record was found with a pay rate of 0 or less. Please review and ensure the pay rate is correctly entered before proceeding.Write (Arcoro to Sage 300 CRE)The employee is not terminated, the Compensations scope is enabled, and at least one of the employee's compensation records in Arcoro has a pay rate of 0 or less.Collection item skipped. The compensation record with the 0 or negative rate is left out of the sync. Other valid compensation records for the same employee, and the rest of the employee record, still sync.Correct the pay rate on the compensation record in the source system so it is greater than 0, then re-run the sync.
Compensation/PayType '[pay rate code]' could not be matched within HH2. The record will not be synced.Write (Arcoro to Sage 300 CRE)The employee is not terminated, the Compensations scope is enabled, and the compensation record's pay rate code passed the earlier pay type checks but the specific compensation record still ends up with no Pay Type ID to send to HH2.Collection item skipped. Only that compensation record is left out. Other compensation records for the same employee, and the rest of the employee record, still sync.Confirm the pay rate code on the compensation record is mapped to an active, non-archived Pay Type in Sage 300 CRE and let that mapping sync to HH2, then re-run the sync. If the record already existed before this error appeared, escalate, since the Pay Type ID may need to be corrected directly on the record in HH2.
HH2 did not return any PayGroup objects. Correct your data in Sage 300 CRE, wait for that data to sync with HH2 and run your Sync again.Read (Sage 300 CRE into Arcoro)HH2 returns zero Pay Group records for the connector when the Pay Group entity is read, before any Pay Group row is processed.Sync stopped. The entire sync run fails, not just the Pay Group step.Confirm Pay Groups exist in Sage 300 CRE, wait for that data to sync with HH2, then re-run the sync.
PayFrequency is not set in HH2's PayGroup object. Contact support for assistance in correcting your data and run your Sync again.Read (Sage 300 CRE into Arcoro)At least one Pay Group record returned by HH2 has no Pay Frequency value set, checked before any Pay Frequency row is processed.Sync stopped. The entire sync run fails, not just the Pay Frequency step.Contact support so the Pay Frequency value can be corrected on the affected Pay Group record in HH2, then re-run the sync.
'[pay frequency name]' does not have a valid pay period count in HH2. Contact support to correct the issue.Read (Sage 300 CRE into Arcoro)The connector is reading its fixed list of pay frequency values (for example Weekly, BiWeekly, Monthly) and the named value has no pay period count configured for it.Whole record skipped. Only that one pay frequency value is left out of the sync. The other pay frequency values still sync.Contact support to correct the pay period count configuration for the named pay frequency, then re-run the sync.

Confirming the Error

  1. Open the sync execution in Sync History for the affected company.
  2. Open the step for the Sage 300 CRE connector.
  3. For the compensation messages, find the Employee entity row and open its Errors list. For the pay group and pay frequency messages, find the Pay Group or Pay Frequency entity row instead.
  4. Match the fixed part of the sentence against the Message text column above. Ignore the value inside the quotes, since that is specific to your data.
  5. Check the Failures column for the step. A non-zero Failures count only applies to the two Pay Group and Pay Frequency messages in this article. When either of those occur, the whole sync run stops, and the step shows a Failure instead of continuing to process Added, Updated, and Unchanged counts for other entities.
  6. For the compensation messages, the sync does not stop. The employee entity row still shows normal Added, Updated, or Unchanged counts, and the Errors column reflects the skipped compensation record.

Resolving the Error

Compensation Pay Rate of 0 or Less

  1. In the source system, open the affected employee's compensation record.
  2. Correct the pay rate so it is greater than 0.
  3. Re-run the sync and confirm the employee's Errors count for this message is gone.

Compensation Pay Type Could Not Be Matched

  1. In Sage 300 CRE, confirm the employee's pay rate code is mapped to an active Pay Type that is not archived.
  2. Wait for that mapping to sync to HH2, or confirm it is already reflected there.
  3. Re-run the sync and confirm the employee's Errors count for this message is gone.
  4. If the pay rate code was already correctly mapped and the message still appears, escalate. The Pay Type ID on the existing compensation record in HH2 may need to be corrected directly.

HH2 Did Not Return Any Pay Group Objects

  1. In Sage 300 CRE, confirm Pay Groups are set up and active.
  2. Wait for that Pay Group data to sync from Sage 300 CRE to HH2.
  3. Re-run the sync and confirm the Pay Group step no longer shows a Failure.

Payfrequency Is Not Set in HH2’s Paygroup Object

  1. Contact support and identify the affected company and connector.
  2. Support corrects the Pay Frequency value on the affected Pay Group record in HH2.
  3. Re-run the sync and confirm the Pay Frequency step no longer shows a Failure.

Pay Frequency Does Not Have a Valid Pay Period Count

  1. Contact support and provide the exact pay frequency name from the message.
  2. Support corrects the pay period count configuration for that pay frequency.
  3. Re-run the sync and confirm that the pay frequency value now appears with an Added, Updated, or Unchanged result instead of an error.

When to Escalate

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

  • The message says to contact support. This applies to the PayFrequency is not set message and the pay period count message. Gather the company name, the connector, the sync execution date and time, and for the pay period count message, the exact pay frequency name from the log before escalating.
  • The Compensation Pay Type message keeps appearing on the same existing compensation record after the pay rate code mapping in Sage 300 CRE and HH2 has been confirmed correct.
  • The Pay Group step keeps failing with no Pay Group objects after you confirm Pay Groups exist and have synced to HH2.
  • The outcome is a sync stopped Failure and you have no ability to correct the underlying HH2 data yourself.
  • The log text does not match the fixed wording in the table above. That is a sign the message is coming from Sage 300 CRE or HH2 directly rather than from this list.
Was this article helpful?
0 out of 0 found this helpful