Deriving Levels within a Bundle Structure
If an Order Line Item has a bundle product, Order Management uses a logic to derive the bundle structure and mark the line item as a Top Bundle, a Sub-bundle, or a Component. This will help Billing logic to look at the bundle product's billing values and determine what levels in a bundle structure should be invoiced. The billing application will mark the Billing Headers (BH) of the corresponding levels with Contracted as True. For the other levels, either the BH is not created or will have Contracted as False.
Order Management uses the following logic to derive the appropriate bundle structure:
| Condition | Derived Level |
|---|---|
| (OLI.LineType = "Product/Service" AND Product.ConfigurationType = "Bundle" AND OLI.HasOption = TRUE AND OLI.ParentBundleNumber = NULL) | Top bundle |
| ((OLI.LineType = "Product/Service" OR OLI.LineType = "Option") AND (Product.ConfigurationType = "Bundle" OR Product.ConfigurationType = "Standalone") AND OLI.HasOption = TRUE AND OLI.ParentBundleNumber != NULL) | Sub-bundle |
| (OLI.LineType = "Option" AND (Product.ConfigurationType = "Option" OR Product.ConfigurationType = "Standalone") AND OLI.HasOption = FALSE AND OLI.ParentBundleNumber != NULL) | Component |
|
Note: Orders created from Conga CPQ or external systems must contain the payload mentioned in the Condition column so that Order Management determines the correct level in the bundle structure.
| |