BOM Import - Working Version Issue

[Anonymous]

I am trying to import a simple BOM, but whenever I try to add a part that does not already have a working revision, I get an error "working version not available".

Why does the BOM import tool require a working revision at all? My understanding is I shouldn't need one if I am just adding an existing revision of a part on to a BOM.

Much apprecaited

[tony.mandatori]

Could it be that the items are linked to a Change Order and are undergoing a change?

The items are being imported with the current user permissions, and the working version will be modified if it finds a match.

[mikewatkinsweb]

Make sure when importing you include the Rev and Lifecycle, see attached example of how to import a BOM Hierarchy example

[Anonymous]

None of the items had an open change order associated with them.

Mike Watkins, why do I need to specify the revision, lifecycle or release date? I have no intention of updating any of these values, I simply want to add the current revision of each part num ber to my BOM. (nor do I accidentally want to update any of these values)

I did some more experimentation, each part that could succesfully be added to my BOM had a "working" revision already created for another reason. Each part that threw an error did not have a pre-existing "working" revision. I then took one of these parts, and added it to an unlreased change order (in order to create a "working" revision). After doing this, i could successfully add it to a BOM using the import tool. After running the import tool, it would add the current released revision of the part (in this case Proto1) and not the "working" revision.

Very strange.