Hi, does anyone have any experience with deciphering and determining how to relate what appear to be parent/child SKUs in Flexera for Mulesoft (a Salesforce company)?  I know I've seen this kind of ambiguous roll up with Cisco products before, but I have no experience working with Mulesoft (reseller = Carahsoft) SKUs.   From the SKU structure, one can infer that the child SKUs are "lower" in BOM than the longer parent SKU, but I think it is inappropriate to think that the parent "contains" the child. In these scenarios, do practitioners process both levels or ignore one in favor of the other? We had previously submitted the SKUs to Flexera content team for processing, but I think they (as we Texans would say, "bless them for trying") probably profiled them incorrectly. Detailed example from PO: - Part No. 100-0001-67 (qty :1) Anypoint Platform Base Subscription Production vCore (qty : 2) Pre-Production vCore (Qty : 4) Salesforce.com, Inc. - 100-0001 - Part No. 100-0003 (qty :14) Additional Production Core/vCore MuleSoft - 100-0003 - Part No. 100-0003 (qty :4) Additional Production Core/vCore MuleSoft - 100-0003   Thanks, David NTT DATA Services ... View more

Is there any practice or experience within this group for capturing or integrating or enriching NIGP Code data at the purchase end of the asset lifecycle? https://www.nigp.org/our-profession/nigp-code   Thanks, David Mathias NTT DATA Services ... View more