Sage 100

Customer is trying to update a Bill of Materials Production Register. It hangs and does nothing. Rebuilt BM_ProductionHeader, BM_ProductionDetail and BM sorts. No errors, same thing. Nothing in the activity log. Thoughts?

Permissions (?)

I'm on the server with admin rights so no, I don't think so. The same person does this everyday.

Maybe it's hitting a corrupt item record? Try rebuilding inventory and CI files.

What's the BM_ProductionTierDIstribution table? It is HUGE. Is that a data entry file that is reinitialized or a history file?

Sounds like a data entry table to me, but best way to find out would be to make a production entry of a lotted or serial number to see if a record writes out there before updating.

I'd also look at the data entry files for bad dates, missing UOM and missing IM Product Line.

@ThereseLogeais, I think it is a data entry file. There is both a BM_ProductionTierDistribution file and a BM_ProductionHIstoryTierDist file. The only sage article I found to reinitialize production data entry was for the legacy version but included a Production Entry Tier Distribution File and also a Inv Entry Tier Cost Distribution file. If so, it should not be huge although the history version likely is. The BM_TierCostCalcWork file may correspond to the Temporary Inv Entry Tier Cost Distribution file. A look at the ProductionRestart file might yield a clue. Old Sage Article. Possible Resolution: Note: Reinitializing or recreating data files deletes all records in the selected files and is irreversible. Always make a backup before performing this procedure. If necessary, seek the assistance of a qualified Sage Software business partner or Sage Software Customer Support analyst. Never reinitialize data files to ""fix"" interrupted updates. Have all users exit Bill of Materials, and reinitialize the following files: BMA - B/M Production Entry Header File BMB - B/M Production Entry Detail File BMC - B/M Production Entry Tier Distribution File BMD - Temporary Inv Entry Tier Cost Distribution BM_01 - Batch Masterfile (if using batch entry) Delete the batch files (if batch entry is used). In Windows Explorer, go to ..\Mas90\BMxxx (xxx = company code). Delete all BMAyyyyy.soa files (yyyyy = the 5-digit batch number. For example, BMA00123.soa represents batch 123). Rebuild the Bill of Materials sort files. The following should be true before reinitializing: The previous Bill of Materials Production Entry update was successful for all entries, and no attempt was made to update Disassembly Entry since then. Note: Printing is generally OK, but do not reinitialize if 'Yes' was selected when prompted to update. Loss of existing data entry is acceptable, and the cleared entries can be reentered. Data entry is empty (Disassembly Entry has been updated and no entries exist). This is typically performed to clear ""ghost"" batches or entries, or to fix files that were damaged after the update.

Any resolution here?

Yes. It was the IM_DataEntryCostCalcCommit.M4T file in addition to the BM_ProductionTierDistribution.M4t file. I had reinitialized the BM file but then got a new error. This was close to 6PM last Friday so I told him to restore his BMXXX file and I would look at it today. Once I copied it over, I reentered one entry and got the same error. This time, upon closer inspection, it referenced CI_TierCostCalc.pvc and the above IM calc file. Once I reinitialized the IM file, it let me print the register. I'm letting them re-enter the entries however. And I have no idea WHY there were 800,000+ records in the above files.

The IM_DataEntryCostCalcCommitt file has caused me issues not just in BoM but WO and IM Transaction Entry too when the customer is using serialized valuations. It seems that records do not always clear during updates, and it takes a while for it to show up. What version is this customer on?

it has been my experience that once some kind of error causes an entry file to not get cleared, it just keeps growing until it impacts performance enough for someone to call us and have it reinitialized.

4.50.4 I believe. This was odd in that ALL of the records were referencing the first BM production entry transaction. The records all started with ""32 003862"" or something similar. The 32 references a BM production entry and the 3862 was the production entry number. I opened it through DFDM and when I did a lookup, it took about five minutes for all of the records to come up. When I scrolled to the bottom, it was the same entry number thus I knew I could reinitialize it.

He emailed me saying it wouldn't update, that the status bar was just hanging. I experienced the same. Scroll bar moved about a quarter inch and just sat there.

Besides clearing the data entry files, I suggest you rebuild keys and sorts IM and answer yes to clear committed lot/serial numbers. Is the serial number for the bill or a component?

The bill. He just emailed and said the entries all updated correctly. The only thing with clearing the committed quantities is that you can't have anything in invoice data entry. Sucks when they use batch entry and always have overlapping batches, i.e. they start a new batch before yesterday's is posted. Maybe someday.....

Yeah, I know getting everything updated that relates to serial items AND getting users out of the system can be a pain although their not being able to update means eventually they won't be able to invoice.

Therese, Are there any third party enhancements installed? There is no reason for a customer with a third party modification to be dealing with the CostCalcCommit issue. IF there is a mod installed contact me for directions on how to get the resolution/fix from Sage.

No, no third party enhancements.