Import BOM using level Template
we have Excel sheet with BOM data to be imported to Agile PLM using Level template.below is a sample of the data format we get.
We were able to import Manufacturer, Manufacturer part number, item, AML from the same excel sheet using standard template import option.
the Level 0 Assembly has a level 1 BOM Item which has a Level 2 UNder it. as shown in teh data below.
the level 1 Item, ImportItem002 has a single associated manufacturer and MPN with it and in teh excel sheet we have 2 rows for it 1 row highlighting the BOM related attributes like quantity etc. and 2nd row for ImportItem002 having the associated MPN and MAnufacturer.
Similarly for the Level 2 Item, ImportItem004 has a 2 associated manufacturer and MPN with it and in the excel sheet we have 3 rows for it 1 row highlighting the BOM related attributes like quantity etc. and 2 rows for ImportItem004 having the associated MPN and MAnufacturers.
IN such case when we use the level template, it is importing only level 1 BOM items into level 0 and further it fails. How can we proceed about reading data in the format that is below?
It looks like you may just have a problem with the way your template is setup to handle the BOM & MFR data.
The Item information doesn’t need to be repeated for each AML row. Also – the first AML row can be on the same line as the Item Data and additional AML rows are only necessary for multiple AML entries.
See the attached file for what I believe to be the correct format (lower green section) for your sample upload data.
I’d try the lower format and see if it works better for you.
I am trying with the same template but out of the three Manufacturers I am trying to import, one does not exist in Agile. This is causing the failure of import for the other two existing Manufacturers as well. However, if I use all the three manufacturers names which exist in Agile, I am able to import AMLs successfully using the same template.
Is it really necessary that all the Manufacturers must be present in Agile?
Doing it all at once is quite all right but the table does get quite tricky and complicated and trying to debug it worse than a tire fire.
What I usually do is break it down into a few basic simple steps.
1. import and create all parts
2. Import and create all manufacturer parts
3. Import parts->manufacturer parts relationship ie. “AML”
When you have the above 3 all done, you essentially have all the components in Agile ready.
Now you do the BOM Building which becomes easy.
Your spreadsheet will contain two mandatory columns:
1st column: Parent Part number
2nd column: Child Part number
(rest of the columns is depends on what you have in your BOM’s. ie. ref des, qty, findnum, etc…)
This table becomes very simple as I have attached.
On the Agile side, when you choose Import, you choose the following:
Standard, No template
Bill of Materials
Define Attribute Map
For the Mapping, it works like this:
Parent part number -> Parts/Documents:TitleBlock:Part Number
Chile part number -> Parts/Documents:BOM:Item Number
Everything else maps accordingly as well. ie qty -> qty, ref des -> ref des
Yes it does require more spreadsheets but they are more basic but breaking it down into steps allows easier troubleshooting.
