This chapter covers the following topics:
This chapter describes setup tasks that you must perform to Oracle Quoting that are specific to the Oracle Telecommunications Service Ordering (TSO) solution. For more information on functionality, setting up, or using Oracle Quoting, refer to:
Oracle Quoting Implementation Guide
Oracle Quoting User Guide
Before you can set up Oracle Quoting for use with the TSO solution, you must set up the core applications for the Oracle TSO solution. For details, refer to the chapter, Implementing the Oracle TSO Solution.
Following is the setup checklist for implementing TSO-specific functionality for Oracle Quoting.
Setup Step | Required/Optional |
---|---|
Implement Oracle Quoting | Required |
Set Profile Options | Required |
Set Up Recurring Charges | Required |
Set Up Payment Due with Order | Optional |
Customize Quoting UI for TSO | Optional |
The following profile options pertain to TSO functionality with Oracle Quoting. For a complete list of mandatory Oracle Quoting profile options, see the Oracle Quoting Implementation Guide.
The following table summarizes the profile options and their recommended settings for TSO functionality.
This profile option determines whether users can change the quantity of a component. It applies to both the Forms and HTML versions of Oracle Quoting. If the setting is Yes, users can change component quantity. If the setting is No, users cannot change component quantity. You must set this option to No to prevent the user from changing the quantity of Component items of a Container Model.
This profile option determines whether users can change the quantity of a top-level model product. It applies to both the Forms and HTML versions of Oracle Quoting. You must set this option to No to prevent users from changing the quantity of the network container. If the setting is Yes, users can change the quantity of top-level model products. If the setting is No, users cannot update the quantity of top-level model products. If the setting is null, the default value is Yes.
This profile option determines if instances appear by default in the search results form. It applies only to the Forms version of Oracle Quoting. If the setting is None, no instances appear by default, and you must conduct a search in order to view any results. If the setting is null, the default value is None.
This profile option determines the default Oracle Installed Base relationship for the Relationship Type menu on the Oracle Install Base Relationships page. It applies to both the Forms and HTML versions of Oracle Quoting. If the setting is Component_Of, the Relationship Type default value is Component-of. If the setting is Connected_To, the Relationship Type default value is Connected-To. If the setting is null, the default value is Component_Of.
This mandatory profile option determines the default quantity that appears in the QTY field of the Oracle Telecommunications Service Ordering window. It applies to both the Forms and HTML versions of Oracle Quoting. If the setting is null, a default quantity of 1 applies. You must set this value to 1 if you are using a container model.
This mandatory profile option determines how to process the order in Oracle Order Management and Oracle Service Fulfillment Manager. You set up order types in Oracle Order Management, and you must include workflow to pass order to Oracle Service Fulfillment Manager. It applies to both the Forms and HTML versions of Oracle Quoting. If the setting is null, there is no assumed default value.
This mandatory profile option determines the default status of a new quote. It applies to both the Forms and HTML versions of Oracle Quoting.
This profile option determines whether or not attributes appear in the Installed Base search results for reconfiguration and trade-ins. It applies only to the Forms version of Oracle Quoting. If the setting is Yes, the attributes appear in the search results. If the setting is No, the attributes do not appear in the search results. If the setting is null, the default value is No.
This profile option determines the number of instances that can appear at one time in the component or connection details. It applies only to the Forms version of Oracle Quoting. If the setting is null, the default value is 100.
This mandatory profile option determines if network container functionality is enabled. It applies to both the Forms and HTML versions of Oracle Quoting. If the setting is Yes, you can reconfigure TSO items. If the setting is No, you cannot. If the setting is null, the default value is No.
Oracle Quoting supports recurring charges for a product if the product has a charge periodicity and it is part of a Container Model. Quoting users should not add a product having a periodicity that is not part of a Container Model. If such a product is added to the quote, the user will not be able to submit the quote to an order in Oracle Order Management. This is due to the fact that Order Management will raise an error for such a scenario. The Order Management system parameter, Enable Recurring Charges, must be set to Yes in order to be able to place the quote (having recurring charges) as an order.
In Quoting HTML UI, the charge periodicities for recurring charges are displayed in the Charge Periodicity column. For a one-time charge, the value in the Charge Periodicity column is blank.
To enable the recurring charges feature in Oracle Quoting (HTML), implementers should expose the Charge Periodicity column from the Products subtab. For more information, see the section, "Customize Quoting UI for TSO", below.
The quote total will be the sum of the header level pricing charges and the quote lines (price, tax and charges) that do not have a periodicity. Thus, quote lines that have a periodicity (i.e., recurring charges) will not be included in the quote total. The following quoting functionality is based on this definition of the quote total:
Searches against the quote total
Order Amount qualifier (mapped to Quote Total)
Seeded approval attribute, Quote Total
For Contracts integration: Total article variable (mapped to Quote Total)
In addition, the following Oracle Order Information Portal attributes for Quoting (header level) exclude quote lines that have a periodicity:
Total
Total List Price
Total Selling Price
Total Adjustment Amount
Total Adjustment Percent
Following is the impact of the profile option, ASO: Enable Defaulting Rule, on how charge periodicity is derived:
At the time of quote line creation:
If the profile option is Yes, then the default value for the Charge Periodicity is derived per the defaulting rule.
If the profile option is No, then the default value for the Charge Periodicity is derived from the item setup in the Oracle Inventory Item Master.
At the time of quote template line creation:
The default value for the Charge Periodicity is derived from the item setup in the Oracle Inventory Item Master.
For payment terms that have one or more payment installments, the Days Due field must be set to 0 (zero). In addition:
If such a payment term is associated to a quote line, then the quote line will have a non-zero pay now amount (assuming a non-zero quote line price).
If such a payment term is associated to the quote header and there are header level pricing charges on the quote, then there will be a non-zero pay now amount associated with the quote header level pricing charges.
Implementers may wish to alter the Oracle Quoting UI (for both Forms and HTML) to display elements specific to the pay now amount. For more information, see the section, "Customize Quoting UI for TSO", within this chapter.
Both the HTML and Forms version of Oracle Quoting allow implementers to configure the UI to support TSO-related fields and UI elements. These setups are discussed below.
In the HTML version of Oracle Quoting, implementers can change the display of columns on the Products page to expose TSO-related columns. The following list shows a sample setup of the columns implementers might display on the Products page:
Charge Periodicity
Instance Name
Also note the following:
The Template Details page can display the Charge Periodicity column.
The display of the Instance Name is not dependent on the profile option, ASO: Use Container Model setting. Implementers can show/hide Instance Name using OA Personalization. This applies wherever Instance Name is displayed in the HTML BLAF UI.
When using the TSO solution, implementers may wish to rename columns to be more applicable to the TSO functionality.
For more information, refer to the Oracle Quoting Implementation Guide chapter, Implementation Tasks for Oracle Quoting (see the section, "Enabling Oracle Quoting Features with OA Personalization").
With the Forms version of Oracle Quoting, implementers can customize the Pricing region. When using the Oracle TSO solution, implementers may wish to expose the Charge Periodicity column.
For more information, refer to the Oracle Quoting Implementation Guide chapter, Implementation Tasks for Oracle Quoting (see the section, "Using Folder Functionality to Customize Forms").
Consider either of the following for the default Line Type:
An Oracle Configurator Functional Companion must always set the default Line Type.
The default Line Type should be blank in Oracle Quoting, and the Oracle Order Management defaulting rules in the order (as opposed to the quote) set the default Line Type.
Use the selectable columns OA personalization feature to show the Line Type on the Quoting lines page and to rename columns, such as renaming Line Type to Action.
Use lookups to disable line and table-level actions that do not apply to the given implementation, such as Split Line, Add Service, ATP check, or Trade In option in Installed Base searches.
For more information, see the Oracle Quoting Implementation Guide.