|Bookshelf Home | Contents | Index | PDF|
In the case of a new order, your Siebel application calculates the Service End Date of a time-based offering according to the value of the DurationValidityStart attribute of the time-based offering discount product.
Your Siebel application also sends the DurationValidityStart attribute values and Service End Dates for the discount products on the sales order to Oracle Application Integration Architecture and OSM. When the order is submitted, the Service Start Date and calculated Service End Date of the order are passed to Oracle Application Integration Architecture and Oracle Communications Order and Service Management. During the Fulfillment to Billing process, Oracle Application Integration Architecture passes the Service End Date to the Oracle Communications Billing and Revenue Management API to create products and discounts.
In the case of time-based offering products, Oracle Communications Order and Service Management sends the Service Start Date, the Service End Date, and the actual delivery date back to your Siebel application by way of Oracle Application Integration Architecture, so that the Siebel application can update the order line items with the new calculated dates. The actual delivery date is mapped to the Completed Date in Siebel CRM. These values are carried over to the asset during the Auto-Asset process. If the Action Code is Add, then the Completed Date value is carried over to the Effective From fields of the asset line items. If the Action Code is Delete, then the Completed Date value is carried over to the Service End Date fields of the asset line items.
|Siebel Order Management Guide Addendum for Communications||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|