Behavior of Service Bundles
The 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:
/service/telco/gsm/telephony
/service/telco/gsm/sms
/service/telephony
/service/ip
/account
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.