Problem Viewing the BOM for Some Items

[Anonymous]

For some of the items I have that include a BOM, I am having trouble accessing the BOM tab.  When I attempt to, I get the following error message:

The problem has been here for several weeks (I've been too busy to look for a solution until now), so the suggested solution of refreshing the page does not fix it.  Additionally, I have been testing out the beta version of PLM 360 and when I try to access the same BOM there, it goes into an infinite loop of redirects.

All that to say, it seems like this is a problem that is related to something I've done wrong in PLM, but I have no idea where to look for the problem, and as far as I can tell, this item is the same as other items whose BOMs come up just fine.  I would just recreate the item and delete the old one, but I would prefer to not have to figure out what is in the BOM all over again, and I would like to identify what the problem is anyhow so that I can make sure I don't repeat it.

[dvirh]

Hi Tim,

This certainly looks like data related and I think the best course of action will be to open a support ticket.

If you want to try to debug the problem yourself, I would sugget to see if the problem reproduces with other BOM Views that have different fields in them. You can start by creating a BOM view with minimal data in it and see if the problem goes away. If it does, you can add additional fields until it breaks.

[nguyentru · Accepted solution]

Hi Tim,

Based on the limited information, it is hard for me to pin point the issue.

However, there aree some simple steps you can do to see it may resolve the issue.

1. In the BOM Tab, check the BOM view selection to see if it is calling any fields from the Item Details Tab with (derived or picklist).  There are times when the information from the original workspaces has been changed and the  field in the current workspace has not been updated correctly.

2. In the BOM Tab, also check the BOM view selection to see if it is calling any fields from the Sourcing Tab.  There is a minor bug that we are working to resolve regarding pulling information from sourcing tab.

Please give it a try.  If these doesn't work, we can meet up tomorrow to go over in more details.  (see my email invite)

Either way, please open a support ticket to allow us to track the issue.

Thank you,

Trung

[Anonymous]

@nguyentru, Thanks so much for taking the time to help me.

Here are the fields I have in my BOM:

Item Details Fields

• Image
  

System Fields

• Descriptor
• Change Pending
• Attachments
• Lifecycle

System Sourcing Fields

• Supplier/Part Number
• Total Cost

Custom Sourcing Fields

• Source URL

BOM Fields

• Quantity

Of these, the only fields that I'd be willing to cut out would be some of the System Fields (and even those will probably become useful later).  All the other fields are providing important information.

Having said that, I did discover that the error only occurs when I'm trying to view the BOM in the nested view of an item that contains one particular part in the BOM or a subassembly of the BOM.  Viewing the BOM of particular part (which is empty except for the item itself) does not produce the error even though all the fields are shown (although the fields containing sourcing information are empty except for a hyphen, as they should be).  Additionally, opening the flat view of the BOM does not produce the error (although some fields such as the image are not included in this view).

Thinking the problem was related to the part being included in the BOM, I tried several different means of removing the part from the BOM.  Since the "Delete" button is only shown in the nested view of the BOM, I tried editing the BOM and changing the quantity to 0.  However, this merely changed the quantity and did not actually remove the part from the BOM.  I then tried deleting the part itself from PLM.  However, even though the part showed that it had been deleted, it still wasn't removed from the BOM.

Anyhow, that's what I've tried so far.  I've accepted your invite, so we can certainly figure out what the problem is tomorrow when we can share screens.

Also, I'd be happy to open a support ticket, but I haven't been able to find where I can do that.  Am I just missing something obvious, or is it really that well hidden?

[Anonymous]

Indeed, the problem was with a field from the sourcing tab.  Specifically, it was a custom field used to enter the source URL for the part (with a URL data type for the field).  Strangely enough, this field was not a problem for some BOMs, but it was for others.  There did not appear to be any rhyme or reason to which BOMs it worked with and which BOMs it didn't.  Even if I remove the single part that is common across all the BOMs that have the problem, the error still occurs.

Hopefully, that information helps in the debugging process.