web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Manufacturing BOM problem

(0) ShareShare
ReportReport
Posted on by 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

I have the same question (0)
  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    Hi Alvaro,

    Did you ever managed to tackle this BOM view issue ?  I've users that complain on a  regular basis that when they try to access to some BOM views, the system hangs on them and I have to kill their session... We definitely ruled out all the security issues and network latency, as the GP client is executed off a Citrix or RDP server and is next to the GP Database server in terms of connection.  

    My suspicion goes towards a child component of a BOM that points to a parent component or itself, which causes GP to an endless loop...

    Did anybody ever got an answer from Microsoft why this is allowed in GP when creating a new BOM in MRP ??? it looks like that when trying to use the 'BOM Copy' function, it catches those faulty BOM's, but not when you create them from scratch... somehow a bid design flaw..

    Usually for us the only way to fix the issue is to delete the entire BOM a recreate it or copy it from a previous version if there is one (and assuming it's not already faulty).

  • Alvaro Rodríguez Ochoa Profile Picture
    2,395 on at

    Hi Beat, it's weird, but we haven't had any issues since then, this is an okd thread, not sure if when we upgraded tp GP 2013 got fixed or what, but haven't had any issues, or at least reported to me since.

    Hope you find an answer soon, sorry I can't hep you any further with this issue.

    Best regards.

  • Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    Thanks Alvaro for the reply.. We're still on GP2010R2... so maybe 2013/2015 have a better handle for this.

  • Alvaro Rodríguez Ochoa Profile Picture
    2,395 on at

    Yes, I think you should start planning an upgrade, I think it would be the best for you!

  • Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    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.

  • Alvaro Rodríguez Ochoa Profile Picture
    2,395 on at

    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!

  • BrennerKlenzman Profile Picture
    65 on at

    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

  • Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    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,

  • wperkinson3 Profile Picture
    2 on at

    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

  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    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

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans