Questions and Answers

Q: The following will occur if there are duplicate prseqno values in the PRYCHK table:

• Duplicate Pay Types, Deduction, and Tax values
• Overstates the Pay Type, Deduction and Tax total amounts.
• If there are two check numbers found using the same preseqno value, the payroll register will only display the first record using the same prseqno.

The maximum prseqno value that Sage Pro can generate is 99999999 before it can be reset to 1. In rare circumstances if a client decides to not purge their archive transactions, they will have duplicate prseqno values. This will cause the payroll register to incorrectly display check postings that are using a prseqno that is being used by another check number

Build Info
———–
Sage Pro 7.5 with SP2

Steps to Recreate
—————–
Due to the nature of this PTR, it is difficult to generate prseqno values reaching 99999999 to reset the prseqno values without making data edits to emulate scenario.

1. Open Payroll, the current payroll year is 2008
2. Open SM and close the 2008 payroll year to move the 2008 transactions from prchk to prychk so there are payroll transactions from more than one payroll year.
3. Under the Print menu, point to Transaction Report and click Payroll Register
4. In the option grid filter report set the report for history and date range to 01/01/07 to 03/31/08 for employees CD1 and TK1
5. Generate and Preview the report
6. Note the check postings on the report displays check number 1 and 290 with sequence numbers 2 and 291 respectively.
7. Exit the report
8. Open PRYCHK
9. Edit the prseqno to 2 for the record where Prempl TK1 and Checkno is 290.
   10 .Generate the Payroll Register report using the same filter settings

You will see that check posting for check number 1 will display duplicate pay types, deduction and tax amounts which doubles the total for each amount. Also check number 290 does not appear on the report even though the check falls within the data range of the report.

A: This issue has been documented in PTR 91056 and will be evaluated by Development for future build. To check the status of this PTR please contact Sage Customer Support.

 

Important
The following should only be done by a Sage Certified Consultant or Business Partner. Create a full and verified backup before proceeding. This should first be attempted in a test installation and the results should be fully verified before implementing in a live system.

To resolve the issue for versions prior to Sage Pro  7.4, manually purge the archived transactions with the duplicate  prseqno values found in PRYCHK. This would require the assistance of a Sage Business Partner, Certified Consultant or Reseller. Introduced in Sage Pro 7.4 purging archived transactions can be done in System Manager, found under the Transaction menu. For more information please refer to the System Manger user guide.

As mentioned above, duplicate prseqno values generated by Sage Pro is extremely rare and should not occur since it resets to 1 after it reaches a value or 99,999.999; allowing users to archive transactions for many years before purging the transaction from history. If this does occur check in PRYCHK and PRCHCK to see if there are any records where PRSEQNO equals 99,999,999. If there are no records anywhere near that value, then the duplicate preseqno values is caused by corruption or manual data edits to the PRKEYS table. The table contains the last generated prseqno value which determines the next prseqno value that should be generated.

© Copyright Sage Software