Sage 100

In Need of a Script I have a handful of clients that run into the same problem repeatedly. CI_item and IM_ItemWarehouse get updated with crazy huge positive and negative numbers for average cost and total value. Pretty sure this has to do with doing bill of materials production entry when the raw materials are not in stock. But nonetheless I'm asked on a regular basis to fix these things and the only way I know how is to export to Excel, search for the wayward numbers and use DFDM to fix them manually. Back in the day when you could get into the interpreter and write code, I would've written a quickie program to do this. Is there a way that a script can be written In versions 4.3, 4.4 or 4.5 to make the corrections? I hope you can understand my pseudocode, this is what I would want to do. SCRIPT ONE Open CI_Item :LOOP read record from CI_item if CI_Item:Valuation = 1 and CI_Item:ItemType = 1 {item is standard cost and regular item} then Let CI_Item:AverageUnitCost = CI_Item:StandardUnitCost Let CI_Item:TotalInventoryValue = CI_Item:StandardUnitCost *CI_Item:TotalQuantityOnHand write record else goto LOOP SCRIPT TWO Open CI_Item open IM_ItemWarehouse :LOOP read record from IM_item warehouse lookup IM_Warehouse:ItemCode from CI_Item if CI_Item:Valuation = 1 and CI_Item:ItemType = 1 then let IM_ItemWarehouse:AverageCost = CI_Item:StandardUnitCost let IM_ItemWarehouse:TotalWarehouseValue = IM_ItemWarehouse:AverageCost * IM_ItemWarehouse:QuantityOnHand write record else goto LOOP

If you write Providex, you could do it as a button script in PVX.

Anyone willing to give me a price on creating such a script and button as @RobertWood suggested?

Greg have you tested this first manually to see what impact (if any) the changes have on valuation reports, on the integration to GL (tieing valuation to GL control account)?

We wrote a short program to do this. We use a batch file to invoke it automatically once an hour.

Yes, the items are Standard Cost, so the average cost values in the files are reference only with no impact to the GL. If it were not for the fact that the clients are downloading the data files to Access they would never know they had an issue. BUT when Access encounters the giant numbers it throws up a decimal precision is too small error and does not download the table. Two are using @DanBurleson 's Shadow Access and another has written their own queries/table mirrors. Dan and I have talked about this and the only resolution we could come up with is fix the data in MAS. I'm just tired of doing it manually, I always take the same steps so it it should be able to be scripted.

Excellent, @LeeGraham can I purchase it from you?