3750400 - Manage Multilevel Bill of Material preselects wrong alternative BOM for subitems and expansion fails with error - SAP S/4HANA Cloud Public Edition

• In the “Manage Multilevel Bill of Material” app, the sub-item “Alternative BoM” field is prefilled with an incorrect value (inherited from the header alternative) when navigating into subassemblies.
• Attempting to expand a subassembly with the incorrect prefilled alternative raises the error: “No components exist for this subassembly”.
• The “Alternative BoM” dropdown shows only valid alternatives for the selected date; choosing a valid alternative allows the component tree to expand.
• On initial load, a component may display an alternative value that does not exist for that component, while another subcomponent may show a correct alternative.

SAP S/4HANA Cloud Public Edition

1. Launch the “Manage Multilevel Bill of Material” app.
2. Enter a material that has multiple components, where at least one component is a subassembly with multiple BoM alternatives, and choose Go.
3. Open the object page and expand a component that is a subassembly.
4. Observe that the sub-item “Alternative BoM” is prefilled with an incorrect value inherited from the header; expanding the subassembly raises “No components exist for this subassembly”.
5. Open the “Alternative BoM” dropdown, select a valid alternative for the subassembly, and expand again; the component tree now displays correctly.

• A gap in handling alphanumeric alternative values during default variant determination causes an incorrect alternative to be displayed initially for subassemblies.
• On initial load, the system prioritizes the lowest (alphanumeric) alternative and evaluates the “Selected Date” validity only after the dropdown is accessed, which can lead to an invalid preselection and expansion error.

1. As a workaround, open the “Alternative BoM” dropdown for the subassembly and select a valid alternative for the current “Selected Date”, then expand the node.
2. If needed, adjust the “Selected Date” to fall within the validity period of the intended subassembly alternative, then expand.
3. Monitor upcoming updates: a fix to ensure the correct default alternative is displayed will be delivered with the 2608 release.

• refer to: SAP Note 3072643 (general information about support channels and platforms).
• refer to: SAP Note 560499 (Customer Interaction Center contact options).

manage multilevel bill of material, alternative bom, wrong default alternative, alphanumeric alternatives, default variant determination, subassembly expansion, no components exist for this subassembly, selected date, validity period, multilevel bom app, dropdown alternatives, variant selection, ui prefill, bom hierarchy, sub-item alternative , KBA , LO-MD-BOM-2CL , Bills of Material (Public Cloud) , Problem