You’re offline. This is a read only version of the page.
5
We noticed what appears to be a bug in the BOM Copy Tool in Dynamics GP Manufacturing. When the Source BOM has a note in the BOM Note Entry window, the note is copied to the New BOM. This is ok, but the problem is the MFGNOTEINDEX3_I in SQL table BM010415 is also copied, which ties both BOMs to the same note. When the note is edited or deleted on one BOM, the same change happens to the other BOM.
The only way I have found to correct this situation is to change the BM010415 - MFGNOTEINDEX3_I value to 0 with a SQL Update.
An identical problem can occur when you edit a BOM Note, close the BOM Note Entry window, and select another BOM before saving the first one. (That is possible by typing the next BOM Number, hitting enter, and then clicking Save in the dialog that pops up).
I did some online research, but so far was unable to find record of anyone else experiencing a similar issue. Hoping someone can provide a fix for this!
Thanks!
We have the exact same problem. I have had it for years. It occurs also on Router edits. Typically I will have 1 user take a while to compose their note and another user will make a quick change or a complete different MO and sequence and get the same MFG Note ID and the last person who saves wins.
Only solution zero out one Router note and recreate. I actually have a SQL job that looks for duplicate notes in the Primary Router and the working Routers. It runs every hour and emails if a dup is found, then I can can zero out the wrong once and re-create.
Share
Report
All responses (
Answers (
