Sage 100 SO Invoice Update - One batch selected for update, second batch got updated as well. No DTR or GL entries for second batch

This situation happens occasionally (once every few months) and I can't find an explanation.

  • SO Invoice batch entry is enabled
  • Multiple invoice batches are in process at the same time
  • One user selects a batch to update, prints the sales journal, updates, prints the DTR, updates.  The journal and DTR are in paperless and agree with each other and the selected batch total.
  • It is discovered that the invoices from a second batch, not selected, are also updated at the same time.
  • The invoices from both batches are in AR history, and IM history, with the same timestamp, SourceJournal, and JournalNoGLBatchNo.
  • ONLY the lines from the first (selected) batch are in GL history, nothing remaining in GL_DailyPosting.
  • The second (not selected) batch is updated to the sub-ledger, but not to the GL
    Other info:
  • The system is 2021 Premium
  • They have a couple of extended solutions and some scripts, none of which, as far as I can tell, are active during SO Invoice posting.

Has anyone seen this before or have any suggestions where to look next?

Any help is appreciated.

Thanks,

Louis

Parents
  • 0

    Did someone transfer invoices into the first batch, after the journal was printed?  (That should not be allowed... but might explain what happened).

    You can look in the server's ...\MAS90\Links\ folder to see if installed enhancements modify the invoicing / sales journal programs.

  • 0 in reply to Kevin M

    Thanks for the reply.  As far as I can tell the journal was printed (paperless) and updated without interruption. There were 30 invoices updated from the second batch.  It would take some impressive data entry to move those in the time needed to print and update the first batch. I tried to merge batch A into batch B on their system while batch B was being updated and, thankfully, Sage would not let me - message "batch B is in use"

    There is a link version of SO_SALESJOURNAL_UPD.pvc which is being used by 2 different enhancements, thanks for that suggestion.  I guess I will have to start reaching out to developers now.

Reply
  • 0 in reply to Kevin M

    Thanks for the reply.  As far as I can tell the journal was printed (paperless) and updated without interruption. There were 30 invoices updated from the second batch.  It would take some impressive data entry to move those in the time needed to print and update the first batch. I tried to merge batch A into batch B on their system while batch B was being updated and, thankfully, Sage would not let me - message "batch B is in use"

    There is a link version of SO_SALESJOURNAL_UPD.pvc which is being used by 2 different enhancements, thanks for that suggestion.  I guess I will have to start reaching out to developers now.

Children
No Data