Sage 100

Error SO-5007 (Qty packed does not equal qty shipped) appears to be back in 2016.1. AWESOME. I copied over the 2 hot fix files from 2015 and it seems to be working in 2016, but JEEZ I hate doing that. (Files are SO_Shipping_bus.pvc and SO_PackageTrackingByItem_SVC.pvc)

Link to [Sage KB article](https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=59494&sliceId=1&cmd=displayKC&dialogID=372888&docType=kc&isLoadPublishedVer=&stateId=372890&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl)

Does that link actually work for anyone? I get the OOPS screen even if I have logged into the portal.

Attached is a pdf of the article Beth. I saw this message yesterday for the first time.

What worked for me: Log in. Click on the link here again and get the oops screen. GO back to the tab where I logged in and click on the Knowledgebase link, which then brings up the KB page in the link. And after that if you need the KB search feature for anything else you have to close the browser and reopen it - log out and log back in again doesn't do it...

I changed the qty packed to 0 to resolve. DOn't want to be doing that all the time but that is the first time I have seen this.

@BethBowers the link works for me but I think there's something screwy with the portal. I find that it will sometimes remember prior pages I've visited so that if I go to try and login/click a link I get taken elsewhere. So if you error out the first time, then login to the portal, then go click the link ---- I'm not sure but it may remember that prior error and try taking you there. There's definitely some very (very) odd behavior in the portal.

@DougHiggs - my client has multiple items that look ""similar"" and so are getting this error on 5+ lines per order. The error itself just baffles me - who programmed it to look at SIMILAR????? What is wrong with using EQUAL, for Pete's sake? Ranks up there with having issues in a Payroll update if someone is in PO updating (because the first letter of the module is the same, I've always assumed).

Update on this - I sent an email to Sage support (instead of creating a case because I didn't trust them to no charge it - how sad is that?) (and it was easier). Linda Raby got back to me very quickly and we were able to duplicate - the issue is actually kit items, not similar items. It is also an issue on 2015.4. They are working on a hot fix as I type.