Sage 100

MAS 200 version 4.4, custom office button in shipping data entry lines panel calls a Crystal report to print labels. Has been working for years. Recently, it will periodically start to print incorrect quantities for some lines. Report has SO_InvoiceDetail and SO_TierDistribution, and uses the qty from the tier distribution table, keyed by invoice number and line number passed from the screen via the script. At the point where it prints incorrect quantities on the shipping workstation, I can open the Crystal report on the server and get correct quantities. When the quantities are incorrect, they are consistent - the same incorrect qty appears on repeated prints. Any ideas?

Check the WRK file and clear it out. I have seen sometimes where the WRK has some old records that didn't get cleared and it gets into the new WRK files created when crystal prints. Depending on how you test on the server you may never see it.

There is no work file - completely custom label form. I have added the parameter fields in small type to the label so we can see if it is MAS passing incorrect parameters to Crystal.

Sounds like you are on the right track then. Check the line number to make sure they are the same on the form as it is for your test.

What technique does the report use to drive the number of label printed. Since normal reports print records based on the record count of the source dataset, label reports use a technique such as a pseudo table or subreport to generate the labels. Is the technique in use still valid?

It just prints one label per lot number, with the qty being the number of feet on the roll (lot).

Might try rebuild key files at some point.

check the IM2 and IM3 (IM_itemWarehouse & IM_ItemCost) files - fields DECostcalcxxxxx for values. This 440 bug affects PU2-8 for Average, & Lifo/Fifo valuations. These fields should only be populated when the update is physically running. If not in an update then these fields should be empty. Affects costing and Avail qty's. (That is the first check, Second check would be reapplying Embedded IO (run replacement script). I'm thinking #1 is the cause. Also these fields will clear - fluxuate so the problem should be investigated when it occurs or run a query on these fields - often. Fix is in PU10. (my best guestimate)

Almost forgot about this situation - check for 'alternate' data source seen within share point. Files renamed by appending the file name has the potential to still be read. ARABC.old = bad; OldAR4ABC = better, best practice is to move the file/folder outside the share point or stored in compressed - ZIP format. Last week had client reporting various issues in MAS, mainly performance. Ended up being a file renamed in 2012 that started to affect the software performance for one users and then gradually spread to affect others (SY_Console_old.m4p) - just some input