"An attendance transaction does not exist in Human Resources" warning message during payrun build in Microsoft Dynamics GP

Symptoms
The following warning message appears during the payrun build process in Microsoft Dynamics GP:

An attendance transaction does not exist in Human Resources *****WARNING*****



Cause
This warning message means that the system has found a transaction(s) in the payroll batch that does not exist on the HR side. If the paycode is linked to a timecode, the transaction should exist in both the HR and payroll tables, and will happen automatically if you hand-key the transactions with a linked timecode/paycode. However, only the payroll table will be updated if the following happens:

  • The transactions were imported directly into the payroll batch. This process may update the Payroll table only and not HR. 
  • The payroll batch was keyed first, and then the paycode was linked to a timecode in HR after the fact. 

Resolution
If you need to update the Human Resources table with the transactions in the unposted payroll batch, there is a reconcile process in Human Resources that will do this:


1. Under Microsoft Dynamics GP, click on Tools, point to Utilities, point to Human Resources and click Reconcile.

2. Mark the checkbox for Reconcile Attendance Transactions.

3. Click Process.

4. Rebuild the payrun batch and verify that the warning message is now gone. 


NOTE: If you are importing in transactions directly to a payroll batch, you will need to run this reconcile utility each time before you build the payrun. There steps should be added to your payrun procedures if you import in payroll transactions on a regular basis. 

NOTE: This reconcile option will only look at unposted batches in payroll. It will update the HR transaction table (TATX1030) with the corresponding transaction(s) from the Payroll Work table (UPR10302) where the paycode is linked to a timecode. It will not update the HR table with transactions that were already posted and in payroll history.  So once the batch is posted in payroll, it is too late to run this reconcile utility. 

NOTE: You can run this reconcile option as many times as you wish (before the batch is posted in payroll). It will skip over transactions that already exist on both the HR and Payroll tables, and update the HR table only for transactions where a matching record is not found. For example, if you import in 3 payroll batches to be included in the same checkrun, you can run this reconcile utility after each import for a total of 3 times, or you can import in all 3 batches and just run it one time after the last import, and before you build the payrun.
 
 

More information
error message HR PR pay-code pay code time-code time code timecode check batch

"transaction doesn't exist in human resources"

"Transaction does not exist in human resources"
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.
Properties

Article ID: 2892399 - Last Review: 09/11/2015 15:04:00 - Revision: 4.0

Microsoft Dynamics GP 2015, Microsoft Dynamics GP 2013, Microsoft Dynamics GP 2010, Microsoft Dynamics GP 10.0

  • kbmbsmigrate kbsurveynew KB2892399
Feedback