Today, we used A/P 6.8A (0201618-database version 1.6.36.1915)to reverse some cheques. Fine. We then put through an adjustment batch to properly clear the vendor's account (the cheques are not to be reissued). Batch went OK, but the batch printout (screen or paper) does not balance!! The second line of distribution gets pushed down to the second vendor and the second vendor's distributions either get omitted (or the second line of the second vendor's distribution gets omitted), causing the batch listing to be out of balance. Tried for different companies and from different machines. No difference. Finally just decided to post anyway (Angela's idea!). Normally I don't listen to Angela, but what the Heck! Surprise, it posts OK, all amounts to proper vendors, posting journal is complete and accurate. All info prints correctly in G/L transactions, and vendors' accounts are OK. Is this just a problem with the report for the adjustment batch, or is there something more serious? Data integrity check is A-OK. Thanks!!

Dear KJ

There are no known issues with the Adjustment batch listing report. Often, when report problems like this occur they will not affect the actual postings, but the report itself has become unstable for some reason.

If this happens again, the suggestion would be to redo the workstation setup, and if this does not resolve it, then try reinstalling Adagio Payables to the Server. (You may want to rename the APWIN program folder first, thus ensuring that all files are installed fresh.)

Glad to hear Angela's advice worked out! (Maybe you'll listen more often?!) <G>

Regards

We have experienced the same problem exactly on more than once occasion. When generating an adjustement batch in AP the entries are entered correctly but the batch listing does not balance or show all the entries. This has happened when posting more than one adjustment to the same vendor and when we post serveral adjustments to different vendors. I didn't attempt to post the batch so we entered the adjustments one at a time and posted them that way.

Hi Vicki (and KJ):

Sounds like we might have a problem with that report under some circumstances. If either of you would be willing to send us your data with an adjustment batch that demonstrates this problem, I'd be happy to have someone track it down.

E-mail directly if you need instructions about how to get the data to us.

Thanks

Dear Vicki (and KJ)

Upon further investigation, this has already been reported and resolved, however, it did not make it into the currently shipping version, as it was reported after that release had already shipped.

It will be in the next version/release. In the interim, limiting your Adjustment Batches to a single transaction each will bypass the problem. It is only a problem on batches with multiple transactions.

Thank you for reporting this - and sorry I missed it the first time!

Regards,