SO Shipping Batch No. missing on Invoice

Occasionally we get an Invoice that is missing the Batch No. from when it was created via Shipping Data Entry.  We have multiple batches a day, usually separated out between EDI and Non-EDI orders and/or AM vs. PM shipments; totally anywhere between 2 - 5 batches.  Shippers will enter their orders as they do every day and then once every 2-3 weeks or so, 1 invoice will not have a batch no. associated with that record in SO_InvoiceHeader.  The Invoice can be for either an EDI shipment or a Non-EDI shipment.  The shippers process the shipment without any errors, pop-ups, warnings, etc. so they aren't aware of any issues.  The issue is found at the end of the day when the accounting department goes to post the batches, both EDI and Non-EDI.  Sometimes they'll get an error that there is an issue with one invoice and I'll go into DFDM to enter the Batch No.  Other times, they don't get any errors and we'll find the invoice that isn't assigned to a batch a day or two later when comparing to EDI and I'll go into DFDM under SO_InvoiceHeader and enter a Batch No.

I created an alert via Sage Alerts to email me when the Batch No. field is empty so I can try to quickly figure out what is happening at that time.  Unfortunately nothing has come up as the reason 1 particular Invoice isn't assigned the Batch No.  Users have PCs, no laptop, hardwired, no wi-fi, no performance issues, IT department has guaranteed me nothing is wrong with their network connections.

I'm at my wits end of trying to figure out what is causing this sporadic behavior.

We are on Sage 100c Advanced v2019.2 with True Commerce EDI and Scanco's Manufacturing module (I include this because our finished Work Tickets create their own SO Invoice Batches).

Anyone experience this and/or have any ideas of what is causing this?

  • 0

    Were you able to resolve this? 

    In the last two weeks, we have had two invoices that have ended up with an empty Batch No. field in Sales Order, Invoice Date Entry.  We are on Sage 100 Advance v2022.4 and use Century Business Business Solutions for our credit card processing in Sage.  So like you, I am also at wits end trying to figure this out.

  • 0 in reply to Hobie16

    This hasn't happened to us for over a year now (knock on wood).  We upgraded from v2019.2 to v2022.1 in Jan 2023.  They may have fixed this issue, but can't say for sure and since it wasn't documented, I don't believe that is what fixed it. 

    I do know we now have one shipper working with Sage 100 through Citrix and the other local to their PC.  Plus, the two users are no longer in the same warehouse office space.  One is a different part of the warehouse.  This may have fixed it, as I have a funny feeling the wiring in the main warehouse office was suspect due to sporadic issues that couldn't be explained logically.  Also, both staff members would go in and out of the same batches and could have "stepped on one others toes" doing so, causing Sage issues.

    With that said, see if your issue might be similar to how the PC's are connected and like us, move a user to a different location to process or have one user run Sage local to the PC and the other via RDC, if you don't have Citrix.  My gut feeling is it was how the two PC's connected into the wall.