Hierarchy challenge

[Anonymous]

Community  -   I have an ask from our top management to help do root cause analysis on our SKUs.    Our SKUs are made of multiple components (the BOM).    We do not have any formal document that outlines the Parent (SKU) with all of its children.    I made a basic example spreadsheet and loaded into Power Bi  (see below).     The far left column represents the full SKU, and the columns to the right, the children that make up the SKU.   

I have another table, called Quality, that lists all of these parts in one column  (including the full SKU), and this is where the quality scores, for each item, are found.   

Ideally what I'd like to do is to be able to have a relationship, one to many, to the table below, and the quality table.  

Since each SKU  (in the yellow column) is unique, I thought about adding an index column that would be the unique identifier to each SKU  (and all of its subsequent components  - PN = part number).     Then I would create a separate table of just the full SKU (yellow column) and it's unique Index ID.    These would both be dimension tables.    Then relate those tables to the Quality table. 

Am I on the right track?  

[v-easonf-msft]

Hi , @Anonymous 

Could you please tell me whether your problem has been solved?
 For now, there is no content of description in the thread. If you still need help, please share more details to us.

Best Regards,
Community Support Team _ Eason

[edhans]

There is no need to create an index. If the SKU number is unique, that should be your unique 1-many relationship field. It would need to be complete - so each part would need to be listed in the SKU column, but you could have a column that designated if this was a finished goods or a component. I also don't understand why you would want a Quality table. Can you not put the Quality score in the Item table as a separate column (dimension) of the SKU itself? 

If that doesn't help, or doesn't fully answer the question, can you post what you are going for? I recognize I don't understand your business, so I fully understand I may be missing a key point here.