Material variant and Nested KMAT
When a header material is a variant (FERT), it can be linked to a Superbom using CS40.
A superBom is a Kmat bom.
A nested KMAT is a KMAT used as a configurable component in a superbom.
On a KMAT in KMAT scenario, both configuration profile are executed which is fine!
On a KMAT in Material Variant scenario, the configuration profile of the KMAT is not executed.
On the top level, since we use the Type-matching, we have a working bom when we remain with the KMAT. If the kmat has a variant, the bom becomes inconsistent.
In order to build inventoty on the variant, a planned order must be able to have a resulting bom that execute configuration on every level...
Any ideas on how to proceed?