I am working with a client who is not getting the correct AP Check number when running AP Print Checks. It appears that several years ago a check with a number of 990100 was used as a CK type check, recently they are having trouble getting the real number to go into the system. The check should be 039609 and it proceeded to pick the 990772 check number and fill in where it could with the next highest check number (becasue they do have 99000 numbers out there the numbers bounced around to the next highest) (I think). They do use 99000 series for Hand Checks, but I am under the impression that it will not look at HC type for the next reference number. How can we get the system to recognize 039609 - I did verify that 039609 has not been used in the past but they do have some Alpha check numbers in the system as well. I have no idea why it would all of a sudden cause issues when the CK types are several years old with the 99XXXX values. Do I need to change the Check Type to HC for thos CK types numbered as 99xxxx values so the system will increment properly?
Dawn
*This post is locked for comments
it is my understanding that this is determined by a query on the refnbr field of APDoc filtering out hand check documents. I think I would start by running a sql query against APDoc where refnbr = '990771' as it appears it is finding that as the last used reference number. Look at the doctype field if it finds it but also look at the rlsed field because you could have an un-released batch using that check number. If it finds something, look at the BATNBR field and the crtd_prog field to determine where this reference number came from. Once such a document is found, we can then figure out what to do about it.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156