ACCEPTED SOLUTION
Accepted Solutions
Bernard,
I have posted a screenshot of PSB in 10.2 M020. I am using some custom views. But you can see that the structure is located on the left side. And you can make edits to the BOM on right side of the screen using the Uses tab. This is fundamentally different than clicking on Actions > Edit BOM in Windchill 9.1. We use this for small BOM changes.
For larger BOM changes, or initial BOM creation, when our BOM isn't CAD driven, then we use an Excel spreadsheet. The way I have leveraged the Import from Spreadsheet functionality is by having users input information onto the same spreadsheet they've used for a long time, and are familiar with. Then I use a macro to reformat the data (on a separate worksheet) into a structure that Windchill prefers for its import engine. This way the users are happy, and Windchill is happy. The macro does the work to make them both happy. The user only needs to click on Import from Spreadsheet, and load the Excel file. And then check the output message from the import (success or failure?).
What format and structure is required for importing WTPart structure into Windchill using the Import from Spreadsheet function? The easiest way is to go to an existing BOM and export it via the Actions menu. It has been a while, so I can't remember the specifics. But that is the principle. You can do this for components too, not just BOM structure. There is also information regarding all of this in the Windchill Help Center in your installation. I had to make some changes to the import spreadsheet structure when we upgraded from 9.1 to 10.2, but they were all related to PartsLink and classification - not the basic functionality. So whatever you develop now will be able to be useful even after you upgrade.
Bernard,
I have posted a screenshot of PSB in 10.2 M020. I am using some custom views. But you can see that the structure is located on the left side. And you can make edits to the BOM on right side of the screen using the Uses tab. This is fundamentally different than clicking on Actions > Edit BOM in Windchill 9.1. We use this for small BOM changes.
For larger BOM changes, or initial BOM creation, when our BOM isn't CAD driven, then we use an Excel spreadsheet. The way I have leveraged the Import from Spreadsheet functionality is by having users input information onto the same spreadsheet they've used for a long time, and are familiar with. Then I use a macro to reformat the data (on a separate worksheet) into a structure that Windchill prefers for its import engine. This way the users are happy, and Windchill is happy. The macro does the work to make them both happy. The user only needs to click on Import from Spreadsheet, and load the Excel file. And then check the output message from the import (success or failure?).
What format and structure is required for importing WTPart structure into Windchill using the Import from Spreadsheet function? The easiest way is to go to an existing BOM and export it via the Actions menu. It has been a while, so I can't remember the specifics. But that is the principle. You can do this for components too, not just BOM structure. There is also information regarding all of this in the Windchill Help Center in your installation. I had to make some changes to the import spreadsheet structure when we upgraded from 9.1 to 10.2, but they were all related to PartsLink and classification - not the basic functionality. So whatever you develop now will be able to be useful even after you upgrade.
Jeff,
Maybe there is a typo on slide 12? The bullet points for "model driven product structure" are actually seen under "import from spreadsheet" and vice versa? Screenshot below.
Also, as I was paging through the slides, I noticed the "Uses" tab. The Unit column is editable. In general, in Windchill a UOM is editable both on the WTPart itself, and in the BOM (WTPartUsageLink). This is quite confusing to me actually. A UOM should not change after an item is initially set up, in my experience. We're connected with our Oracle ERP system, and in that system a UOM cannot be changed for an item. If you set up an item as Liters for example, it should be purchased in Liters, sold in Liters, used on BOMs as Liters. A user should not have the potential to put it on the BOM as Milliliters or worse - Gallons. Therefore I think UOM should be read-only on WTPartUsageLink. We have made that customization at the site level for our Windchill installation.
Anyway, my rant is digressing from the OP. Sorry. Should be discussed in a different venue.
