Sage 100

Happy Sunday! Client doing physical count in 4.4.7 - trying to print physical register. It errors on the first item in the list. Most of their Items are LOT. Knowledgebase does not have anything on this. Anyone know what this line of code is looking for? TIA Error #11: Record not found or Duplicate key on write Program CI_TierCostCalc.pvc Line 804

What's the info button say?

I do not know that it is that helpful - see attached. The first warehouse(000) we froze has nothing in it and the item number 00101 we did not count any - so it should be a perfect physical count for this item.

What if you enter a count on the first item? Is this the first time they have done a physical in v4.4? Did they import or key the items?

Jeff asks good questions. When you print the register it goes through a cost calc routine which writes the committed cost tiers to a data file called IM_DataEntryCostCalcCommit (deccc file). The error means it cannot find a key in the IM_ItemCost file (IM3). However this key (which may not be the one on Info screen) is coming from deccc. To find the key, you can click on Debug from Info window and type this command at the prompt verbatim: dmp deccc. The key comes from these values: deccc.ItemCode$ deccc.WarehouseCode$ deccc.TierType$ deccc.GroupSort$ The last 2 above will return ""3"" (meaning Lot) and the Lot Number, respectively. The question is why is this key not in IM_ItemCost. If the combined key is in fact just ""00101"" as the screen shows then it is missing the Whse Code, the ""3"" and the Lot Number after it (clearly bogus). I too would ask if the physical count was imported. Hope that helps.

I am almost on site. Been driving 5 hours. Company being sold. New MAS company will be created tonight after we post inventory. Alnoor may need u if u r available tonight

Should the IM_DataEntryCostCalcCommit be clear? It has data in it from 01/10/2011 since the last physical count.

i would have thought that when they froze the inventory, this file would be reset. Did they freeze the inventory?

I think if I reinitialize IM_DataEntryCostCalcCommit it fixes the issue and populates when we run the register.

That was my next thought.

I am the one who froze their inventory - I actually went through several steps - ran balancing utility first, ran negative tier adjustment - rebuilt files and sorts - cleared frozen(In case someone had frozen before) - then finally froze - they have been entering all day in physical count entry - not count cards.

What happened when you reinitialized?

Sure hope driving to client was in the plans.................

looks like if fixes it. I think since data was already in the file - it was confused. If I preview the report now and look at the file there 6,000 entries in the file. As soon as I close the report - the record count drops to 0. Thanks for pointing me in the right direction.

It will be interesting to see if that file is purged once you update.

Trying to update physical inventory with client on v4.4.8. Getting the same error. Will try to follow Johnny's steps.

Reinitialized the IM_DataEntryCostCalcCommit table and register is generated. Phyical inventory was imported via VI. Starting to think this is a bug.............

Driving 5 hours on New Year's Day, good lord.

BL - Johnny was driving on 12/11! Has anyone else experienced this issue printing the physical update register. Just way too coincidental that we have had two occurances. Beth Bowers?

My observation is probably in early builds of 4.4 it was still very buggy and not doing all that it should have done back then and we had orphaned records in that file which is causing an uglier error when a physical count register is being printed.

I did an import into Physical on 4.50 with no problems.

Just fielded another support call (4.5.2 this time) with this issue. Reinitializing the IM_DataEntryCostCalcCommit.M4T was the answer once again.

Probably just copied over from 4.4 version during upgrade Look at the file in the 4.4 version and browse through the records to see when it was done.

I just got this error reported to me on 4.4 PU8 just after updating from PU4. One day we will nail down the root cause of this.

Has anyone looked at the KB for this yet? I wonder if anyone has reported it yet? @AlnoorCassim - What I would really like someone to figure out is why the ALE ship to's go south when installing PU7 or higher.................

I wonder if the newer code just clears the file properly After the update or printing - whatever step it is. But not before records start get inserted. I have looked at the records through DFM and noticed they were old physical counts etc. still lingering in there.

Just had this happen. Client was doing a physical for only 3 items, but the error was complaining about an item that wasn't one of the three. We renamed the IM_DataEntryCostCalcCommit file and recreated it and the physical went through. Seems to be an issue with that file clearing once a physical update is run. This client is on 4.5, but would have done their last prior physical on 4.4.