Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Configure Bundle Products

A bundle must be configured to let the billing engine to know the level (bundle, sub-bundle, components, etc.) at which it needs to be billed.

Since the a bundle can be configured in different ways across transactions, the billing levels are derived at the order level. For more information, see Deriving Levels within a Bundle Structure. Billing uses this information to mark the corresponding billing headers as Contracted or Informational . The Contracted billing headers are picked up for invoicing, while the Informational ones are not invoiced.

For more information on how to associate billing and invoicing with a product, refer to Associating Billing and invoicing with a Product.

The billing header is marked as contracted and billing records are generated, subjected to settings at the product and order line item levels as follows:
Bundle Invoice Level on the ProductDerived Level in a Bundle Structure on the OLIBilling Header of the Bundle or Components (Options)Create Billing for Informational Products in a BundleBilling Records Generated
Top BundleTop BundleContracted = TrueNAYes, Contracted
ComponentsComponentsContracted = TrueNAYes, Contracted
Top BundleAny value other than Top BundleContracted = FalseYesYes, Informational
ComponentsAny value other than ComponentsContracted = FalseYesYes, Informational
Top BundleAny value other than Top BundleContracted = FalseNoNo billing records
ComponentsAny value other than ComponentsContracted = FalseNoNo billing records

The billing records under the billing headers with Contracted = True, are picked up for invoicing. However, Informational billing records can be created for tracking or auditing purpose.

You can bill a bundle product in one of the following ways:
  • Bill the top Bundle product and Bundle Options separately
  • Bill the Bundle product including all Options rolled to the bundle product)
  • Bill each Bundle Option Item separately

To bill the top bundle only

To bill the top bundle, it is required that the Contracted flag must be True only for the bundle product and options must have Contracted flag as False. If you want to bill the bundle product including all options rolled to the bundle product, configure the bundle and options as follows:

ProductBundle Invoice Level on the ProductDerived Level in a Bundle Structure on the OLIBilling Header
BundleTop BundleTop BundleContracted = True
Option-ATop BundleComponentsContracted = False
Option-BTop BundleComponentsContracted = False

When the entire bundle is initiated for billing, the billing records (BH, BSRs,and BSDs) are generated for the bundle product only.

As per the organizational policy, If you want to generate informational billing records for the options, set the Create Billing for Informational Products in a Bundle setting to Yes at the product level before initiating the billing.

As per the organizational policy, If you do not want to generate informational billing records for the options, set the Create Billing for Informational Products in a Bundle setting to No at the product level before initiating the billing. Billing header will not be generated for this configuration.

To bill the components only

To bill the components only, it is required that the Contracted flag must be True only for the components and bundle must have Contracted flag as False. If you want to bill only the components and not the bundle product, configure the bundle and options as follows:

ProductBundle Invoice Level on the ProductDerived Level in a Bundle Structure on the OLIBilling Header
BundleComponentsTop BundleContracted = False
Option-AComponentsComponentsContracted = True
Option-BComponentsComponentsContracted = True

When the entire bundle is initiated for billing, the billing records (BH, BSRs,and BSDs) are generated for the components only.

As per the organizational policy, If you want to generate informational billing records for the bundle, set the Create Billing for Informational Products in a Bundle setting to Yes at the product level before initiating the billing.

As per the organizational policy, If you do not want to generate informational billing records for the bundle, set the Create Billing for Informational Products in a Bundle setting to No at the product level before initiating the billing. Billing header will not be generated for this configuration.

To bill the top bundles and components

To bill the top bundle and components both, it is required that the Contracted flag must be True for bundle and the components. If there is a sub-bundle as part of this bundle configuration, the Contracted flag must be false for this product. If you want to bill bundle and the components, configure the bundle and options and sub-bundle as follows:

ProductBundle Invoice Level on the ProductDerived Level in a Bundle Structure on the OLIBilling Header
BundleTop Bundle, ComponentTop BundleContracted = True
Option-ATop Bundle, ComponentComponentsContracted = True
Option-BTop Bundle, ComponentComponentsContracted = True
Sub bundleTop Bundle, ComponentSub-bundleContracted = False

When the entire bundle is initiated for billing, the billing records (BH, BSRs,and BSDs) are generated for the bundle as well as for the components.

As per the organizational policy, If you want to generate informational billing records for the sub-bundle, set the Create Billing for Informational Products in a Bundle setting to Yes at the product level before initiating the billing.

As per the organizational policy, If you do not want to generate informational billing records for the sub-bundle, set the Create Billing for Informational Products in a Bundle setting to No at the product level before initiating the billing. Billing header will not be generated for this configuration