Relationships and Reports

Good day all.  I am going through our Aras trying to understand what is going on with it.  We inherited this from another contract.  The previous caretakers created their own ItemTypes and didn't use any of the default ones.  We are trying to run a BOM report on parts, but are getting errors with it.  I have been looking at the Part ItemType & the s_Part ItemType (what is being used) to identify the differences and try to get things to work.  Here is where I am at.

The custom s_Part is using a "Parts List" instead of the BOM that the Part uses.  One of the differences I have noticed between these is that the BOM is a relationship back to Part & the Parts List is a null relationship.

When I run the custom BOM Quantity report, I receive a parts list with how many of each component is required.  If I run it from too high of a level (example:  Antenna Group) I receive an error that indicates that I do not have permissions.  The next lower assembly (Antenna Array) will work. 

The custom Multilevel BOM reports cause the system to crash.

I was reading through the article for creating Queries, but it doesn't work for our setup.  I think this is do to the null relationship. 

Any help would be greatly appreciated.  Thank you.

  • Sounds like fun. Now the question is, what do you actually want to achieve? Do you want to go on with the current setup and just make the missing features work?

    Queries and TGV also work for Null-Relationships, at least in newer Innovator Version. 

  • Angelalp,

    Right now I need to adapt to the current setup, hopefully this can be corrected when we upgrade.  I would like to understand why this happens on some parts and not others.  I have noticed that the s_Parts List document has other parts lists attached to the parts list.  This is something that I have to fix.  Any suggestion on why this could be happening would be really helpful.  Thank you.

    Aras v11 SP10 Build: 6667

  • "The custom Multilevel BOM reports cause the system to crash."

    Is this one a copy of the standard XSLT Report? These kind of Reports are easy to crash. I would start with the Report Query (only Innovator 11, will be moved to Method in Innovator 12). 
    When your problems mainly occur on complex and large Parts (lots of relationships), than this would indicate a wrong/inefficent query.