Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Communications Guide > Overview of Siebel Communications > About Prebuilt Integration with Siebel Communications > About Service BundlesThis topic describes service bundles and their behaviors in Siebel Communications. Description of Service BundlesA service bundle is a group of related services that you sell as a package. Service bundles simplify service selection and configuration. A single billing instance in the Oracle Communications Billing and Revenue Management application is constructed for a service bundle. A service bundle is similar to a product bundle. For more information about product bundles, see Siebel Product Administration Guide. You can create service bundles. To create a service bundle, select Service Bundle in the Billing Type field for the bundle. Other examples of values for the Billing Type field include: Discount, Event, Item, and Subscription. A service bundle can include the following content:
To see the products in a bundle, navigate to Administration - Product screen, Products view, select the product bundle, and click the Bundle Product view tab. A service bundle for wireless phone service might include the following items:
In this example, the activation fees and usage fees are simple products, the rate plans, features, and discounts are customizable products, and the SMS is a nested service bundle. Behavior of Service BundlesThe Billing Service Type field for a service bundle is populated with data when the products in the Oracle Communications Billing and Revenue Management application are synchronized with the products in the Siebel application. Examples of values for the Billing Service Type field follow: To see the Billing Type field and the Billing Service Type field for a service bundle or a product in that bundle, navigate to the Administration - Product screen, Products view, and select the record for a service bundle or a product in that bundle. Expand the form in the Detail view. The Billing Type field and the Billing Service Type field appear in the Logistics section of the form. After products are synchronized, do not change the values in these fields. Although Siebel Communications provides no validation rules, all product components under a service bundle must have the billing account, service account, and billing profile of the root product in that service bundle. The billing account, service account, and billing profile fields are associated with the line items in an order and are populated when a user creates an order. If you modify, disconnect, suspend, resume, or transfer a service item that relates to a parent service bundle, or if you upgrade or downgrade a promotion for a service item that relates to a parent service bundle, then multiple service charges can be automatically created if the parent service bundle includes child service bundles to which service charges apply. If a service bundle status is updated, then the statuses of the product components in a service bundle are updated. If a customizable product that contains a service bundle is updated, then the status of the service bundle is updated. The SIS OM Order Line Item Update Main workflow updates the status field of order line items, but administrators can configure this workflow to update other fields. About Simple Service BundlesA service bundle is a type of complex product that is created manually in a Siebel application. A simple service bundle is a subscription product that is created in Oracle Communications Billing and Revenue Management, then marked as a service instance in a Siebel application. When an order containing this product is submitted, Oracle Application Integration Architecture recognizes the product as a simple service bundle and creates a service instance in Oracle Communications Billing and Revenue Management. A simple service bundle combines a service bundle and a billing product into a single Siebel CRM product. Combining two products in one can simplify the product hierarchy of a service bundle. Additionally, synchronizing an already-created subscription product from Oracle Communications Billing and Revenue Management minimizes the manual setup steps for a service bundle in Siebel Communications. A simple service bundle can include only products of billing type Event as components. These event products are synchronized from Oracle Communications Billing and Revenue Management. For example, a simple service bundle called Internet Service might have a component event product called Internet Activation. A simple service bundle can be a simple product or a complex product. A simple service bundle that is a simple product represents a single-event product in Oracle Communications Billing and Revenue Management. A simple service bundle that is a complex product represents a multiple-event product in Oracle Communications Billing and Revenue Management. In Siebel Communications, a simple service bundle can be a root-level product, can be nested in another service bundle, or can be nested in a complex product. Comparison of Service Bundles and Simple Service BundlesFigure 1 shows how a specific grouping of services might be set up using service bundle functionality only, and how the same grouping of services might be set up using simple service bundle functionality. On the left, under Service Bundle, the item labeled SB and shaded in blue represents a service bundle manually created in Siebel CRM, with its Billing Type set to Service Bundle. Items labeled BC and shaded in yellow represent service bundle component products synchronized from Oracle Communications Billing and Revenue Management. The Internet Access Service bundle is mapped to the Internet - MCF product, and the Internet - MCF product is mapped to multiple events in Oracle Communications Billing and Revenue Management. On the right, under Simple Service Bundle, the item labeled SI and shaded in pink represents a subscription product synchronized from Oracle Communications Billing and Revenue Management, with its Service Instance flag set to Y. Items labeled BC and shaded in yellow represent service bundle component products synchronized from Oracle Communications Billing and Revenue Management. The Internet - MCF product is mapped to multiple events in Oracle Communications Billing and Revenue Management. In the service bundle, certain features are set up as multiple nested products. For example, Internet Email might be two products, a service bundle product manually configured in Siebel CRM, with an associated component product synchronized from Oracle Communications Billing and Revenue Management. By contrast, in the simple service bundle, the corresponding features are set up as single products. For example, Internet Email might be one product, a subscription product synchronized from Oracle Communications Billing and Revenue Management, then flagged as a service instance in Siebel CRM. Constraints on Simple Service BundlesSimple service bundles operate under the following constraints:
New Purchases and Simple Service BundlesNew orders for simple service bundles have the following characteristics at run time (that is, when new order processing occurs in Siebel Communications):
Change Orders and Simple Service BundlesChange orders for simple service bundles have the following characteristics at run time (that is, when change order processing occurs in Siebel Communications):
Configuring a Simple Service BundleTo configure a simple service bundle, follow this procedure. To configure a simple service bundle
Viewing the Event Items in a Simple Service BundleTo view the child event items associated with a simple service bundle, follow this procedure. To view the event items in a simple service bundle
Guidelines for Service Bundles and Simple Service BundlesThe bundling requirements of a service determine whether to define the service as a service bundle or a simple service bundle. When deciding, observe the following guidelines and cautions:
|
![]() ![]() |
Siebel Communications Guide | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |