Siebel Communications Guide - Downloads - Oracle
Siebel Communications Guide - Downloads - Oracle
Siebel Communications Guide - Downloads - Oracle
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Overview of <strong>Siebel</strong> <strong>Communications</strong> ■ About Prebuilt Integration with <strong>Siebel</strong><br />
<strong>Communications</strong><br />
■ Discounts (for example, 50% off the first 3 months and a free minutes discount)<br />
■ SMS (Short Message Service) for text messaging. This service might include rate plans (for<br />
example, SMS Basic and SMS Unlimited)<br />
In this example, the activation fees and usage fees are simple products, the rate plans, features, and<br />
discounts are customizable products, and the SMS is a nested service bundle.<br />
Behavior of Service Bundles<br />
The Billing Service Type field for a service bundle is populated with data when the products in the<br />
<strong>Oracle</strong> <strong>Communications</strong> Billing and Revenue Management application are synchronized with the<br />
products in the <strong>Siebel</strong> application. Examples of values for the Billing Service Type field include:<br />
■ /service/telco/gsm/telephony<br />
■ /service/telco/gsm/sms<br />
■ /service/telephony<br />
■ /service/ip<br />
■ /account<br />
To see the Billing Type field and the Billing Service Type field for a service bundle or a product in that<br />
bundle, navigate to the Administration - Product screen, Products view and select the record for a<br />
service bundle or a product in that bundle. Expand the form in the Detail view. The Billing Type field<br />
and the Billing Service Type field display in the Logistics section of the form. After products are<br />
synchronized, do not change the values in these fields.<br />
Though <strong>Siebel</strong> <strong>Communications</strong> provides no validation rules, all product components under a service<br />
bundle must have the billing account, service account, and billing profile of the root product in that<br />
service bundle. The billing account, service account, and billing profile fields are associated with the<br />
line items in an order and are populated when a user creates an order.<br />
If you modify, disconnect, suspend, resume, or transfer a service item that relates to a parent service<br />
bundle, or if you upgrade or downgrade a promotion for a service item that relates to a parent service<br />
bundle, multiple service charges can be automatically created if the parent service bundle includes<br />
child service bundles to which service charges apply.<br />
If a service bundle status is updated, the statuses of the product components in a service bundle are<br />
updated. If a customizable product that contains a service bundle is updated, the status of the<br />
service bundle is updated. The SIS OM Order Line Item Update Main workflow updates the status<br />
field of order line items, but administrators can configure this workflow to update other fields.<br />
About Simple Service Bundles<br />
A service bundle is a type of complex product that is created manually in a <strong>Siebel</strong> application. A<br />
simple service bundle is a subscription product that is created in <strong>Oracle</strong> <strong>Communications</strong> Billing and<br />
Revenue Management, then marked as a service instance in a <strong>Siebel</strong> application. When an order<br />
containing this product is submitted, <strong>Oracle</strong> Application Integration Architecture recognizes the<br />
product as a simple service bundle and creates a service instance in <strong>Oracle</strong> <strong>Communications</strong> Billing<br />
and Revenue Management.<br />
28<br />
<strong>Siebel</strong> <strong>Communications</strong> <strong>Guide</strong> Version 8.1 Rev. D