Open APIs

Hi All, @Lutz Bettge @Kamal Maghsoudlou

I am struggling to understand the concept of the BundledGroupProductOffering as specified in the TMF620 Product Catalog Management v5 user guide.  In the v4 version, we could support hierarchy of bundled product offerings using the BundledProductOffering sub-resources.  This would allow us to bundle simply product offerings or nested bundles.

What is the difference/purpose of the BundledGroupProductOffering?  The API description is quite brief.  Is this to add a hierarchical grouping name rather than re-usable/re-sellable bundles?

Thanks in advance

Hi All, @Lutz Bettge @Kamal Maghsoudlou

I am struggling to understand the concept of the BundledGroupProductOffering as specified in the TMF620 Product Catalog Management v5 user guide.  In the v4 version, we could support hierarchy of bundled product offerings using the BundledProductOffering sub-resources.  This would allow us to bundle simply product offerings or nested bundles.

What is the difference/purpose of the BundledGroupProductOffering?  The API description is quite brief.  Is this to add a hierarchical grouping name rather than re-usable/re-sellable bundles?

Thanks in advance

Hi Rochana,

sorry for late response.

first of all, the structure of BundledProductOffering and attached Option still exists for backward compatibility and for cases where the complexity introduced with BundledGroup is not necessary, so you surely can build a hierarchy without using the new structure.

Concerning the new BundledGroup: It is a collection of ProductOfferings (modeled as BundledProductOfferings) from which a customer may choose; the total number of Product instances that he may choose is defined by the Option element attached to the Group, and for each of the BundledProductOfferings, the attached Option then defines how many instances the Customer may choose from that particular ProductOffering.

Imagine a structure like this:

The PO "Bundle" has (possibly amongst others) a group that refers to two different kinds of accessories. From "Accessory 1", the customer may choose between 2 and 4, and from "Accessory 2" he may also take between 1 and 4. But in total, he can must choose at least 4, up to 7 in total. So he may not choose 2 of "Accessory 1" and 1 of "Accessory 2", because that is less than the required total of at least 4, and he may also not chose the maximum numbers of both types of Accessories, because that exceeded the total of 7.

Using the "bundledGroupProductOffering" self-association, more complex restrictions can be built if necessary.

Does this clarify the new Group structure?

Hi All, @Lutz Bettge @Kamal Maghsoudlou

I am struggling to understand the concept of the BundledGroupProductOffering as specified in the TMF620 Product Catalog Management v5 user guide.  In the v4 version, we could support hierarchy of bundled product offerings using the BundledProductOffering sub-resources.  This would allow us to bundle simply product offerings or nested bundles.

What is the difference/purpose of the BundledGroupProductOffering?  The API description is quite brief.  Is this to add a hierarchical grouping name rather than re-usable/re-sellable bundles?

Thanks in advance

Thanks Matthieu and Lutz.

That indeed clarifies the purpose of the selection group.  The examples in the TMF620 user guide are incorrect.  I have raised a new JIRA ticket to get these updated and also improve the descriptions of the fields.

Hi Rochana,

sorry for late response.

first of all, the structure of BundledProductOffering and attached Option still exists for backward compatibility and for cases where the complexity introduced with BundledGroup is not necessary, so you surely can build a hierarchy without using the new structure.

Concerning the new BundledGroup: It is a collection of ProductOfferings (modeled as BundledProductOfferings) from which a customer may choose; the total number of Product instances that he may choose is defined by the Option element attached to the Group, and for each of the BundledProductOfferings, the attached Option then defines how many instances the Customer may choose from that particular ProductOffering.

Imagine a structure like this:

The PO "Bundle" has (possibly amongst others) a group that refers to two different kinds of accessories. From "Accessory 1", the customer may choose between 2 and 4, and from "Accessory 2" he may also take between 1 and 4. But in total, he can must choose at least 4, up to 7 in total. So he may not choose 2 of "Accessory 1" and 1 of "Accessory 2", because that is less than the required total of at least 4, and he may also not chose the maximum numbers of both types of Accessories, because that exceeded the total of 7.

Using the "bundledGroupProductOffering" self-association, more complex restrictions can be built if necessary.

Does this clarify the new Group structure?

Hi All, @Lutz Bettge @Kamal Maghsoudlou

I am struggling to understand the concept of the BundledGroupProductOffering as specified in the TMF620 Product Catalog Management v5 user guide.  In the v4 version, we could support hierarchy of bundled product offerings using the BundledProductOffering sub-resources.  This would allow us to bundle simply product offerings or nested bundles.

What is the difference/purpose of the BundledGroupProductOffering?  The API description is quite brief.  Is this to add a hierarchical grouping name rather than re-usable/re-sellable bundles?

Thanks in advance