1 Kudo

Import Tool with multiple workspace Access

Status: Solution Provided
by Contributor Asingh5 on ‎01-25-2013 10:42 AM

It is common for a BOM to have a wide variety of components/items associated in it (For Example Screws, Washers, Nuts, Hardware, Motors and sub-assemblies). Many would organize those components/items in more than one workspace within PLM360.

 

In order to mass create/update BOMs of a specific product practically, the import tool must allow access to add/remove 'child' items from other workspaces - Especially if PLM360 allows you to do it manually.

 

Having access to only the 'Parent' workspace in the import tool is impractical. This either results in poor item organization within the workspace when trying to make the import tool work OR results the user performing a tedious manual process.

 

Overall, I think the import tool is a great feature for BOMs; however it still needs to incorporate a multi-workspace functionality to serve its purpose practically.

 

Regards,
Amrit Singh

Status: Solution Provided
Hi Amrit, Currently our import tool does have the functionality to create Parent and Child relationship. Through the import tool you can import n the Part Number, Name etc... and create the Hierarchy BOM, Level BOM, or Parent Child BOM. Please refer to the link for instructions. http://help.autodesk.com/view/PLM/ENU/?guid=GUID-D887D527-2187-4210-B04B-33745853E112
Comments
by Employee nguyentru on ‎11-04-2013 03:48 PM
Status changed to: Solution Provided
Hi Amrit, Currently our import tool does have the functionality to create Parent and Child relationship. Through the import tool you can import n the Part Number, Name etc... and create the Hierarchy BOM, Level BOM, or Parent Child BOM. Please refer to the link for instructions. http://help.autodesk.com/view/PLM/ENU/?guid=GUID-D887D527-2187-4210-B04B-33745853E112
by Contributor Asingh5 on ‎11-05-2013 06:28 AM

Does this allow access to a parent child relationship if the parent and child are in different workspaces?

by plmadmin on ‎02-18-2014 03:18 PM

Support,

Please revise the status on this request. 

 

The status was set to "Solution Provided" however, I don't see how the Solution solves Amrit's original issue. 

 

It does not solve the inability to import BOMs where child items resides in a different workspace.

 

 

 

 

You are not logged in.

Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register

Announcements
IdeaStation Guidelines
Review guidelines and best practices
before posting a new idea


PLM 360 Survey