Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Order Management Guide Addendum for Industry Applications > Effects of Order Management >
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 3.
NOTE: Use caution when restructuring customizable products that are in use. If you regroup product components under different relationships in a customizable product, there will be conflicts between the new version of the customizable product and existing transaction data in quotes, orders, and assets.
Quotes
The following changes have been made to the Quotes screen.
- The action codes for quote and order line items have been modified and are as follows:
- Add. The item was added during the configuration session.
- -- (Dash). A dash means the item was not changed during the configuration session.
- Delete. The item was removed during the configuration session.
- Update. An attribute value for the item was changed during the configuration session. The Update action code is also assigned if certain fields in Quotes > Line Items are changed.
- 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.
- A Sales Order button is added to Quotes > Quote > Orders.
- 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.
- 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:
- Items with the One-Time price type are added together. Each item is then displayed separately in Opportunities > Revenues.
- 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.- Items with the Recurring price type are added together. Each item is then displayed separately in Opportunities > Revenues.
- 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.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Order Management Guide Addendum for Industry Applications Published: 18 April 2003 |