Siebel Order Management Guide Addendum for Communications > Employee Asset-Based Ordering > About Managing Time-Based Offerings >

Example of Including a Time-Based Offering in a New Order


This topic gives one example of including a time-based offering in a new order. You might use this feature differently, depending on your business model.

As an example of a time-based offering in a new order, consider a bundled promotion, Wireless Silver Plan. This bundled promotion includes a component discount product, 10% Discount. The 10% Discount component product has attributes with values as described in Table 17.

Table 17. 10% Discount Product Attribute Values
Attribute
Value

Duration

3

DurationUnitOfMeasure

Months

DurationValidityStart

Now

To include a time-based offering, in this case the Wireless Silver Plan bundled promotion, in a new order, you would follow this procedure.

To include a time-based offering in a new order

  1. Select the Wireless Silver Plan bundled promotion as a line item in a new order.

    For information about creating and processing an order, see Processing a Sales Order Through Oracle Application Integration Architecture Integration.

    This bundled promotion includes the component discount product, 10% Discount, which therefore becomes part of the order.

  2. Set the date field values of the promotion as shown in the following table.
    Field
    Value
    Comments

    Due Date

    11/19/2009

    None.

    Service Start Date

    11/24/2009

    By default, this field displays the value in the Due Date field, but this value can be changed manually by users.

    Original End Date

    None.

    None.

    The Service End Date field value of the promotion is calculated from the DurationValidityStart attribute value of the 10% Discount component, as follows:

    • Now. If the DurationValidityStart attribute value is Now, then the Service End Date value is calculated as Due Date plus Duration multiplied by Unit of Measure. The Service End Date is three months after the Due Date of 11/19/2009, or 02/19/2010.
    • Original Start. If the DurationValidityStart attribute value is Original Start, then the Service End Date value is calculated as Service Start Date plus Duration multiplied by Unit of Measure. In this case, the Service Start Date has been specified as 11/24/09. Therefore, the Service End Date is three months after the Service Start Date of 11/24/2009, or 02/24/2010.
    • Original End. For a new order, there is no Original End Date. Consequently, if the DurationValidityStart attribute value is Original End, then the Service End Date value is calculated as Due Date plus Duration multiplied by Unit of Measure. The Service End Date is three months after the Due Date of 11/19/2009, or 02/19/2010.
Siebel Order Management Guide Addendum for Communications Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.