Sage 100

End user on Sage 100 ERP 2013 PU 3 - having issues with QuantityCommitted in the IM_ItemCost for Lot/Serial items. They're asking how they can correct the field QuantityCommitted in the IM_ItemCost. It does not appear that you can use VI for this. Is there an alternate approach?

Wasn't there a utility published for this? Not sure, just in the back of my mind....

I think we tried the utilities and for some reason they did not make any change in their specific instance.

Am attaching the pdf of what I've used. I'd like to hear more about what happens for them, though, because i have an open issue with Sage on blank Tier fields and QtyCommitted issues.

I spotted a pu for 2013 that's supposed to fix an issue with blank tiers occurring during physical count variance.

Thanks @BethBowers, I knew it was in the back of my head somewhere....

@WayneSchulz - mine appears to be happening during Bill Production.

I'm seeing a lot more of these types of issues where there appears to be no clear resolution. Therefore I've started calling Sage much earlier in the process than I ever have. I take a support case and from that point on leave it in Sage's hands. I'm done with 6-8 hour head scratching then call Sage for another 2 hours of fun which invariably ends with some variation of ""send us your data and sit on your hands"". I am entering an age where many of the remaining Sage 100 customers are dealing with existing Sage product defects where Sage does not appear to know how to correct them. - Lot/Serial costing - Paperless office move for large numbers of documents - Sage 100 Advanced as a service defect requiring registry entry - Sage 100 integrations stranding customers at whatever version they are using (this is going to be bigger as customers age)

Geez, @WayneSchulz - how did you guess I had sent off my client's data to Sage and was awaiting their response? It took me a day to get everything because they didn't just want the data files (and I didn't feel like kicking my client off to get the files that were in use), and I got a warning from Sage that they couldn't start working on this until they got all of the files. Geez, we've been dicking around with this for 2 months, I think I can hold out til the end of the day. It's not like you're gonna miraculously solve it 10 minutes after you start testing. Or 10 days, either. Or ever. SADS.