BOM Multi Level Recursion?
Currently am importing a BOM via Excel on to Agile PLM 9.3.5. The BOM imported is a partial BOM, It is not matching the Excel sheet.
The BOM Structure is as below, the sub assembly(Level 1 BOM) of a top level assembly (Level 0) becomes sub assembly(Level 2) for another sub assembly(another Level 1 BOM)
In this scenario the BOM import will be partial and throws an error
Duplicate items: Items <child item number> is already used on the BOM for Part <Parent item Number>
Note:
Under Smart rules of Java Client “BOM Multi Level recursion” is set to “allow”
Manu,
Not quite certain I am clear. So during a load…. you are loading multiple BOMs at the same time, hence for the single BOM you are loading the level 1 and subasseblies so level 2s and perhaps level 3s. You have at least one PN that shows up in multiple assemblies on the BOM and when you load you are getting this error. Can you verify the scenario?
hello Patric,
To be more pricise on this am attaching the Excel sheet and the expected BOM structure
Import is performed in webclient
Import>> Browse for excel >> Choose Level Template >> Mapping the attributes and specify ECO>> Import
Java Client Configuration:
Smart Rules
BOM Multilevel Recursion: allowed
Hello Patrick,
Yes, this error comes when atleast one Part Number exists in multiple assemblies of BOM
Here with attaching the excel sheet for more information on the BOM structure
Error:
Duplicate items: Items “ImpItem005” is already used on the BOM for Part “ImpItem004”
Duplicate items: Items “ImpItem007” is already used on the BOM for Part “ImpItem005”
Note:
Yellow highlighted rows define the multiple occurrence
Uncertain why this may be. You may want to attempt to load the BoMs individually and see if that is allowed.
Manu, While I do not have a spreadsheet example handy at the moment, some of our users have had better luck using the Parent-child template, rather than the level template. If I recall, this would mean that you have a PARENT column and a CHILD column. The parent item part number shows up in as many rows as there are level 1 child items. If the child items have components of their own, then they get their own rows, but they are now the parent item, etc. In this type of import, there is no need to specify the level. Naturally, you still need columns to specify other BOM specific attributes, like find number, quantity, etc. If the items already exists, then the spreadsheet should be fairly simple, but if you intend to have this import create items that do not currently exist, then obviously, you have to add much more information. Hope this helps.
Steve
Based on the screenshots I do not think this a recursion issue. The Smart Rule allows A -> B -> A where a child owns one of its parents. I would look at your “Duplicate Item Numbers”, “Duplicate Find Number” and “Duplicate Ref Des” Smartrules. Depending on the settings the error might be triggered by one of these rules being set to “Disallow”.
