Difference between abstract and concrete bundle models and use of the "Bundle assets" flag

[Fred Jean]

Hello,

Related to model bundles, there are 2 things I find not clear both in the documentation and in the HAM training course :

• Difference between abstract and concrete bundle model
  • Can someone provide an explanation different from the documentation, with examples if possible ?
  • How does one actually create an abstract vs concrete bundle model ?
    • The documentation states "To create an abstract model, set the model category to Bundle and add the components. To create a concrete model, create a model in the Product Catalog > Product Model > Bundled Models module and add components."
      • When I create a bundled model, the category is automatically set to "Bundle"; does this mean it should be changed to something else when creating a concrete model ?
      • In both cases it's saying to add components; for abstract it's missing the starting point : on what record/form should I set "the model category to Bundle" if not on a bundle model created through "Product Catalog > Product Model > Bundled Models" (as mentioned for the concrete model) ?
        
• use of the "Bundle assets" flag
  • From what I see, even if this does not seem to be explicit in the documentation, when the "Bundle assets" field is not checked, it's not possible to create Bundle Assets from the Bundle model even when status is In production.
    • what is the reason for that and what is the purpose of bundle models from which we cannot create bundle assets ?

[Ravindra H V]

Concrete Bundle Model:

• Fixed & Physical: A Concrete Bundle is a set of physical assets that are grouped together. Once the bundle is created, the items in it usually don’t change.
• Example: A laptop bundle that includes a laptop, charger, mouse, and keyboard. These items are always tracked as part of this "specific bundle".
• Bundle Asset Flag: The flag is set to true for each asset in the bundle to show they belong together.

Abstract Bundle Model:

• Flexible & Logical: An Abstract Bundle is a logical grouping of assets. These assets may not be physically grouped together but are grouped for management purposes.
• Example: A "workstation bundle" that includes any laptop, monitor, and keyboard. The assets could be different and purchased separately but are grouped for tracking.
• Bundle Asset Flag: The flag is also set to true to group these assets together, but they are not physically part of the same bundle.

Key Difference:
Concrete Bundle: A fixed, physical set of assets that are always grouped together.
Abstract Bundle: A flexible, logical set of assets that can change and aren’t necessarily physically grouped.
The Bundle Asset flag helps track whether an asset is part of any bundle, whether Concrete (fixed and physical) or Abstract (logical and flexible).

DOCS

Please mark it as helpful if you found this useful.

[Fred Jean]

Hello, thank you for the effort in trying to clarify this, but unfortunately it's still not clear for me; especially on the practical side :

- If I look at the list of bundle product models, how can I tell which is abstract and which is concrete ?

- How do I proceed to create an abstract bundle model vs a concrete bundle model ? (I can't spot the difference between "To create an abstract model, set the model category to Bundle and add the components" and "To create a concrete model, create a model in the Product Catalog > Product Model > Bundled Models module and add components";  it does not give the starting point to create the abstract model, where do we start if not from Product Catalog > Product Model > Bundled Models as stated for concrete models ?)