Hi Naveed
There is no limit imposed by the model on nesting product specifications within specifications. But be aware that the semantic meaning is that the entire structure will be referred to from a product offering that points to the top level of the specification structure, with the pricing in the product offering. And the entire structure should instantiated in the product inventory, this is not a commercial bundle. If you wish to create a commercial bundle, you would do that using product offering.
For example, suppose you have a Broadband product that always includes an email box with no pricing implications. You might decide to create a separate product spec for the email box, and refer to it from the Broadband product spec. Your Broadband product offerings would refer to the Broadband product spec, and when the spec is instantiated for a customer she will receive a Broadband product that contains an email box product.
You should consider carefully why you would want multiple levels of specification, and consider also presentation aspects (how do you show this in the inventory to the end customer).
Note: Strictly speaking, we should not use the term Bundling when talking about product specifications, it would be more accurate perhaps to talk about atomic and composite. But the spec and model use that terminology so we are left with that.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------
Original Message:
Sent: Sep 06, 2019 05:57
From: Naveed Ahmed
Subject: Question about multi-level nesting of Product Specifications
Hi,
I am working with Product Catalog Manager. I just want to ask what rule do we have for multi-level nesting of Product specifications?
In other words do we allow "bundle of bundles" for Product specifications?
Thanks in advance.
Best regards,
Naveed
------------------------------
Naveed Ahmed
PiA Bilisim Services Ltd.
------------------------------