We had an invoice batch that was posted that had duplicate invoice numbers so we received a posting errors report indicating that they had been rejected by the posting batch. The rejected entries were written to another invoice batch as expected. A strange thing happened when we tried to print the original posting journal. For some reason "phantom" posting journals are being "created" for each of the errors in the invoice. We know they are there because of the from/to offering in the print posting journal option. We know they are phantom because they are empty and we receive the appropriate message when we try to print. This has happened everytime we have had rejected invoices since we installed the upgrade and Service Packs. Suggestions ?

Hi Sandra,

Are the 'phantom' posting journals you are referring to the 'error' posting journals? These are written to every time there are posting errors of some sort, resulting in some entries being written to an error batch. When you begin to print the posting journal, there may be a checkbox selection to print the error posting journal - if you de-select this choice, does this resolve the problem?

When it comes time to purging the posting journal, this error posting journal will be purged along with it.

The phantom batches do not exist, but Payables thinks that they do. When we try to print them we receive a message stating "There is no invoice posting journal to print in the specified posting sequence range". The sequence numbers have been recorded by Payables as used, but we have no printout to support that usage.

Hi Sandra,

Thanks for the update; this makes more sense as to what's happening.

Information is stored within Adagio Payables for the most recently used posting sequence and also the most recently purged posting sequence. If these values are equal, that means all the posting sequences have been purged and there is nothing to print. If they are not equal, this means that one or more posting sequences are expected to be found in the posting journal file, and this range will be displayed when you select to print the posting journal report.

However, if the data file does not contain these posting sequences, then the program will give a message that there is nothing to print because it couldn't find them. The typical cause for this is that the posting journal file was deleted when it shouldn't have been, getting out of synch with other internal settings.

The only way to get this back into synch is when you next post a batch. At this time, do not print and purge the posting journal for only that sequence. Instead, you need to print and purge for all sequences it displays as it's default. Then the most recently purged posting sequence will get back in synch.

As an aside, when you post batches and get the error batch, are all entries considered invalid, or do some get posted and others sent to an error batch?