You’re offline. This is a read only version of the page.
2,395
Hi all, today we started with problem either opening some BOM's or just make an inquiry, when we put the item number for the bill of materials, either finished good or phantom, it displays the first and second level items and just hangs, some other BOMs we can open with out any problem, this just started happening today, I even restarted the server.
What I could see on the server is that when we try to open a BOM cpu % goes all the way to 100%, but as I said, this just started today, and no changes where made to the server.
Any one has an idea of why is this happening?
Regards
*This post is locked for comments
The 2 main BOM tables are BM010115 (work detail ) & BM010145 (work header).
check out this KB from Microsoft.. it may help:
support.microsoft.com/.../the-mrp-regeneration-process-in-manufacturing-stops-responding--locks
Thank you for the reply.
Which tables should I update?
Yes this was definitely a problem in 2010, but still there in other releases.. I don't have access right now to my script collection, but it's definitely a child component that points to a parent with the same item number..
Check your BOM work tables and look for identical names in the component fields
I am having this exact problem with a BOM referencing itself. We are running 2010.
If I try to delete from within GP, the session locks up.
How do I clean this up?
Any help is greatly appreciated.
Will
Hi Brenner,
Thanks a lot for the reply.. this is pretty much the conclusion I came to also. I've not seen yet a mix-up of MFG & ENG BOMs, but mostly what happens is a child component points to a parent item.. I'm often able to 'fix' the issue by removing the faulty line in the table and that does the job. Sometimes the BOM is so complex that we just delete it and take a copy from a previous release.
Best regards,
Hi Beat-
I've seen a system lock-up like that when attempting to view a BOM. It only happened with some of their BOMs.
They were using a combination of Engineering BOMs and MFG BOMs. The manufacturing code that checks for circular BOM references does not take into consideration the BOM Type (it treats all BOMs and MFG BOMs). As a result, the procedure goes from the parent MFG-BOM into the 'child' MFG-BOM (instead of using the ENG BOM) ..which takes it back into the parent...and so on.
So, check to see if you have some BOMs containing the Parent Item as a child, but using a different BOM Type.
Regards,
Brenner
I have the same problem, can't use payroll here, we are in México and payroll is not supported by GP, we have very specific rules here.
Best of luck in the upgrade!
I'm already full in :-)... testing currently GP 2015... but with we have some concerns with the Canadian Payroll, as not all the functions are yet supported in the new release to replace the BP.
Yes, I think you should start planning an upgrade, I think it would be the best for you!
Thanks Alvaro for the reply.. We're still on GP2010R2... so maybe 2013/2015 have a better handle for this.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,113
Super User 2024 Season 2
#2
Martin Dráb
229,918
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (