A customer is expecting options and variants (Classic variants) to manage their product BOM. We are not able to understand how the product structure (explained below) will be managed using options and variants and also if this scenario is a correct candidate for variant management or not.
Customer scenario is explained below, any suggestions regarding the use case will be helpful.
We are unable to understand,
Also, it would be helpful if anyone could tell where we can find information/knowledge about best practices regarding variant management in such scenarios.
Customer doesnot have Product configurator license hence we are not exploring that option.
Thanks and Regards,
I see a few scenarios depending on business practices and requirements.
Scenario 1 -
Assuming nodes are all physical items in the structure, and assuming the company follows some kind of form/fit/function rule for part numbering, you must have different part numbers for the standalone Subassembly1/2 and the nested instances inside Product 1. If you do not, there would be problems with inventory if you have 2 items named the same, but in the real world they aren't actually the same. See CM2 principles for an example of this methodology
In this case, these structures are not well suited to using legacy options and variants, as you will want to create pre configured variants that hold static BOMs
Scenario 2 -
If the structures are more logical, and you have interfaces/integrations in place to handle discrete part numbering, you could use legacy options variants to make components 11,12,13,14 disappear from the bomview when looking at product 1 with the right variant condition - eg "Standalone = TRUE/FALSE" and appear in the bomview as unconfigured when looking at sub assembly 1/2. In the snapshot - the variant configuration is applied on the left, but not on the right.
One more thought - it would seem like your product structures should be organized more around common and exclusive groups so that optional content (eg comp 11, 12) is not mixed with standard content (component 3,4,5). This method would lend itself better to options and variants as well