Siebel Order Management Guide Addendum for Industry Applications > Effects of Order Management on Other Siebel Applications >

Effects of Order Management on Fields and Functions


This section describes the effects of Siebel Customer Order Management on fields and functions in the following screens:

Product Administration

Products are defined in Product Administration > Products. Several new fields have been added to the product record that are specific to order management. Fields added to the product record for order management are listed in Table 2.

NOTE:  When you are configuring the product in Siebel Tools, be sure to include the right More Info form for the Product Administration screen. For communications, media, and energy, the Product Administration screen uses the applet named Product Administration view. For other industry applications, use the applet prefixed with the name or initials of the product. For example, for Siebel Life Sciences, use LS Product Administration view.

Table 2.  Fields Added to the Product Record by Order Management
Field
Function

Service Instance

This check box designates the product as a service item.

Customer-facing applications use this flag during check-out to request additional information about the account. Anonymous users cannot place orders containing products marked as a service instance. To order these products, anonymous users must create and account by registering.

Service Instance is also used to identify the products that display in the Trouble Tickets Service Instance field.

Track as Asset

This check box causes the Order To Asset workflow to copy the item to the asset table. Items in this table display as customer assets in the Service Items or Billing Items applet. These applets list the assets that the customer has purchased. Asset tracking may not be suitable for some items. For example, usage-based products like Excess Minutes or Installation charges may not be tracked as assets.

Price Type

Required. The menu choices are One-Time, Recurring, and Usage.

Select One-Time if you charge the customer only once for the product. For example, you would select One-Time for hardware products that the customer purchases. Items in this category are totalled in quotes and orders as non-recurring charges (NRCs).

Select Recurring if you periodically charge the customer for the product. For example, you would select Recurring for a product that is a monthly service. Items in this category that have the Per Month unit of measure are totalled in quotes and orders as monthly recurring charges (MRCs). No other unit of measure is totalled in quotes and orders.

Select Usage if you bill the customer based on amount of usage for a product. For example, you would select Usage for electrical service billed by kilowatt hour of usage. This price type is for information only and is not used in any price computations.

Ship

This check box designates the product as one that must be shipped to the customer.

UoM

Unit of Measure. This menu provides a variety of choices such as per Month, Pound, Day, Case, Dollar, and Dozen.

Per Month is the only unit of measure for which subtotals and totals are provided in quotes and orders. Other unit of measure totals can be configured using Siebel Tools.

The UoM that can be selected is determined by price type. For example, if the price type is Recurring, only the per Day, Month, Year and so on. units of measure can be selected. You can add additional units of measure in the Applications Administration screen.

Auto Explode

This check box identifies items that will be exploded or ungrouped by the Ungroup and Quote to Order workflows.

Network Element Type

Select a value for all products that are network components.

Select Network to designate a product as the top level component of a network (e.g. Frame Relay). This does not have a location.

Select Network Node to designate a product as a location in a network (e.g. Port).

Select Network Connection to designate a product as a connection between two locations in a network (e.g. Access, PVC).

Compound Product

This check box identifies a product as a compound product for which compound product rules are specified.

Service Length and Service Length UoM

The user can define a service length within the product definition to specify how long the service will be provided.

Select an integer in the Service Length field and select the units of measure in the Service Length UoM field. For example, to specify that the service will be provided for six months, select 6 in the Service Length field and select month in the Service Length UoM field.

Service Length Period

A concatenated field that displays the values in the Contract Length and Service Length UoM fields.

Service Start Date and Service Date

Displays the start date and end date, which are calculated based on the period selected and the completion date of the line item. For example, if the Service Length Period is 14 weeks and the Completed Date is Jan. 1, 2004, the Service Start Date will display Jan. 1, 2004, and the Service End Date will display April 15, 2004.

Quotes

The following changes have been made to the Quotes screen.

  • The Delta Quote button has been removed from Quotes > Line Items. Instead, a Modify button was added to the Service Items and Billing Items applets. For more information about the Modify button and its associated workflows, see Workflows for Employee Ordering.
  • The Sum Components button has been removed from Quotes > Line Items.
  • An Auto Order button is added to Quotes > Quote > Line Items.
  • A Modify button has been added to Orders > Sales Order > Line Items. This button creates a follow-on order for an order that has reached the point of no return.
  • If a user creates multiple orders from the same quote, the application generates the full history in the Quotes > Orders view.
  • New fields have been added to the following views:
    • Quotes > Quotes form
    • Quotes > Quote > Line Items
    • Quotes > Quote > Line Items > Attributes
    • Quotes > Quote > Line Items > Totals
    • Quotes > Quote > Line Items > Line Item Detail
    • Quotes > Payments> Totals

Orders

The following changes have been made to the Orders screen.

  • In Orders > Sales Order, and in Orders > Line Item Detail, Pending has been added to the Status field LOV. Pending is the status of the order after it has been created but before it has been submitted.
  • An Auto-Asset button has been added to Orders > Sales Order > Line Item. This button is for application demonstration purposes only and may be absent from the installation. The underlying auto-asset method is designed to be called by the external provisioning system when an item has been completed.
  • The auto-asset process is initiated by setting all line items to complete and clicking the Auto-Asset button at the line item level. For any type of product, for example, frame relay, wireless service, or DSL, the auto-asset process must be run on each line item.
  • New fields have been added to the following views:
    • Orders > Sales Order form
    • Orders > Sales Order > Line Items
    • Orders > Sales Order > Line Items > Attributes
    • Orders > Sales Order > Line Items > Totals
    • Orders > Sales Order > Line Items > Line Detail
    • Orders > Sales Order > Payments> Totals

Opportunities

The following changes have been made to the Opportunities screen.

When the user clicks Update Opportunity in Quotes > Quotes, the revenue associated with the quote is transferred to the opportunity listed in the quote's Opportunity field. In Opportunities > Opportunities, the user can display the opportunity and view the total revenue that has been transferred from Quotes. The user can also display all the line items contributing to total revenue.

Revenue is computed and displayed in Opportunities differently. The following process describes the steps in how revenue is generated from a quote:

  1. Items with the One-Time price type are added together. Each item is then displayed separately in Opportunities > Revenues.
  2. The price of each item that has the Recurring price type is multiplied by a designated number of periods (occurrences). For example, an item is priced at $10 per month. If that item is typically purchased for one year, the number of occurrences associated with that product should be set to 12, so the revenue for this item is $120.

    NOTE:  You can change the number of occurrences used to compute the revenue in one of two ways:

    You can define the number of periods used to compute revenue for an item by entering a number in the # of Occurrences field in the Item's product record. This is useful when the company changes the way in which a product is sold—for example, if the default length of the contract is changed from one to two years. (You edit product records in Product Administration > Products.)

    You can also define the number of periods in the # of Revenue Occurrences field in Quotes > Line Item Detail. This is useful when a particular customer purchase is for a different number of periods than is usual.

  3. Items with the Recurring price type are added together. Each item is then displayed separately in Opportunities > Revenues.
  4. The two price type subtotals are added together. When the user selects Update Opportunity in the Opportunities > Revenues drop-down menu, the total is displayed in the Revenue field in Opportunities > Opportunities.

The amount of revenue contributed by each item is displayed in
Opportunities > Revenues. Items with the One-Time price type display only once. Items with the Recurring price type display once for each unit of measure (per week, month, and so on.). For example, if an item's revenue is computed using a period of 12 months, there is a separate line item for each month.

Siebel Order Management Guide Addendum for Industry Applications Copyright © 2007, Oracle. All rights reserved.