Sage 100

Has anyone else come across a multitude of issues with quantities on order NOT agreeing with what is actually on order? I know the solution is to rebuild PO/SO sort files and recalculate quantities on order but just in the last 24 hours, we have had four customers with issues. I believe they are all on v2015 but I couldn't tell you off the top of my head what PU. One customer in particular said, ""It is getting frustrating to keep having them come to me with the on hand vs available issue weekly and now almost daily."" Anyone else??

Yes, and I have opened a case with Sage and sent data files. They said they are collecting as much data as they can to figure out the cause (multiple complaints). If you issue is the same as mine, it appears to be the IM_ItemWarehouse file for specific parts only, with no rhyme or reason. The quantity on file goes into the negative, which of course causes the items to be calculated incorrectly as you add SO's and Po's. Check out the parts that are off and see if when you clear out all the orders the item quantity is negative. Let me know if that is the case with you and i can forward you over the details from Sage and maybe we can get to the bottom of it.

Thanks @MichelleNichols seems like a lot of tracking for FOUR customers but it may be worth a look. Will let you know.

The big issue on our end, is that my customer has Sage Inventory Advisor. So for several parts its trying to over-order, which makes SIA completely pointless, it is happening with so many different parts, I am in the process of developing a script to rebuild the SO and PO files automatically every night :(

If you find a common thread I'd be interested in an update. I think many of our customers are conditioned to rebuild sort files so they may not even report this to us.

I have several customer that run the rebuild sort files when they do period end because these are off so often. Sage needs to fix this.

Sage is too busy reinventing payroll tiers.

Sage is about squeezing blood out of turnips tomorrow, yesterday is old news...

I typically tell them the file is updated with each invoice/receipt of goods but that it sometimes gets out of whack. Why, I do not know. Is the file locked? Does something happen with the update process? Kind of hard to explain to them.

hope it gets fixed soon...

I'm not going to hold my breath @LourdesSobrino ...

We think it's caused by deleting PO's or SO's that have been partially received or partially invoiced. The problem has existing for years. Possibly since 4.4. We have talked to Sage about it and they recommend rebuilding sort files.

I've been seeing this for the past 10 months at one client. Unable to reproduce at will, so the solution has been regular rebuilding of sort files.

Would it be possible to 'schedule' this, as mentioned in this thread? https://90minds-com.socialcast.com/messages/26479624?ref=stream

@ThereseLogeais, the program to rebuild sort files has a user interface. Maybe a PVX guru can tell us how to pass a company code and module code so rebuild sorts can run silently. Or, it may be easier to write a VB script to update the onPO and onSO fields in Inventory. This is a short term solution. Sage really needs to fix the problem. We have done some limited testing to see if we can screw up the onPO and onSO counts but haven't found it yet. Some customers are affected more than others. Like i said, it may have something to do with the way they go about closing unfilled PO's and SO's.

There is a Sage KB article (10/8/15) mentioning that the SOZUZA incorrectly calculates - This may or may not be relate to the issue you describe. I have a client on v2015 also reporting issues with quantities. Rebuild sorts program for S/O (SOZUZA) incorrectly recalculates sales order quantities. Sage KB : Last Modified Date:10-8-2015ID:69390

Great, so you can't automate it AND even if you do rebuild sorts, it might not solve the problem??

That is a correct assessment. Almost feel like handling out dice to clients.

The few customers who actually pay attention to their data make me wonder how screwed up the data is for the majority that don't.

@MichelleNichols has Sage gotten back to you on this or is there a documented KB article?

Nothing yet @NicoleRonchetti. They are overdue for a follow up call. I will report back with anything new.

Actuallly.... Logged onto the portal and low and behold! KB: 104511 Michelle, Unfortunately, we could not get the program fixed in the 2016 or the product updates next scheduled for release due to the risk it would present. To add this program fix at this late stage could cause problems in many areas which could make this problem into something more impacting. The coding for the next release is done and testing has already been in process. Therefore we are going to take another look at this after the 2016 release to see how to best implement the fix without causing risk. This will also give the appropriate time for testing to minimize any risk.

So that means there won't be anything in PU3 then.... boo.

Are we talking about two different problems? Sage is trying to fix the ""Rebuild Sort Utility"". I am trying to discover the problem that causes the On Order quantities to be incorrect in the first place.

That is what my issue is @DougJenkins, the SO and PO quantities are just randomly off (Stemming from the IM_ItemWarehouse file it appears). Who knows how Sage relates everything together. The KB Article I listed above refers to the same PO number being used in multiple batches, which is not related to mine at all... but several customers are having the same issues with quantities. I know I was not the first to relay the problem, so maybe that is what the KB article is referring to, the first case engineering got? I didn't see anything in the article about fixing the sort utility, did I miss that?

Some customers have variances more often than other customers. It has to be related to conditions that occur and how the customer chooses to resolve them. Something like, a purchase order is partially received and the remainder is backordered, then the customer deletes the PO. We know this isn't the cause, but we are looking for exceptions like this that can skew the onSO and oPO totals.

Has there been any movement on this issue? Actually multiple issues, if I understand this thread correctly.... 1) Whatever is broken to get the quantities off - 2) Correction of rebuild utility so it can be used to correct the symptom of the problem.

Add me to the list of customers experiencing this issue. Weirdly the rebuild sort files did NOT fix the ON SO which appears to be off. The challenge is the customer says ""Well I think other items might not be right either --- how do I check them / fix them"".

As far as checking them... why wouldn't dumping the SO detail lines to a spreadsheet, sorting by item code and subtotaling the amounts on order. Could get cute and pull in the number of SO from inventory and instead of subtotaling that one, isn't there a MIN function?

I checked the one that was reported inaccurate and there was no item in SO. With respect to reviewing the remaining items - who pays for this and what happens if a week later they spot an item that is out of balance? At best we're applying bandaids to a system that is aimed squarely at the wholesale market which expects inventory accuracy.

I agree whole heartedly... accuracy shouldn't even be a question. Any idea which version/update broke this?