Sage 100

Client has error 26 MPWRAB 4150. Sage says to rebuild files, which we have done twice. I've done a dump from the error, but the dump lists 3 different sales orders in various places and 2 different items. We have looked at all of them in Sales Order, checking the Qty, Whs, U of M Conversion, and Promise Date fields, which all look OK. Can someone tell me how to determine EXACTLY which item is giving us the issue? We even deleted one of the orders and now have the error on a brand new item - oh, yay.

@BethBowers you should be looking for an invalid Promise date on a Sales Order Line.

And who wants to take bets we have to look at it in DFDM because it's displaying correctly on the screen....

@DougJenkins - THANK YOU! We'll see how far that gets us!

Beth, when the error occurs, you should be able to go to Debug mode and type ?SO2.ItemCode$ and <ENTER> to see what the item code is that causing the problem. The sales order number can be seen by typing ?SO1.SalesOrderNo$ and <ENTER>. The issue, as Doug has indicated, is that it's trying pack the four-digit year of the PromiseDate$ field, but that is apparently not numeric. The code appears to be the same for 4.50, 5.00 and 5.10 versions. Are you on one of those?

@PhilipWhirley - thanks for the additional info. Client is on 5.0 or 5.1.

In this case, VI is useful in that any Crystal or Excel query will blow up. VI Export to CSV, then open in Excel to find the crap date.