This chapter covers the following topics:
This chapter includes setup information that is specific to the Oracle Telecommunications Service Ordering (TSO) solution.
The Oracle TSO functionality leverages the following Oracle Applications:
Oracle Accounts Receivable
Oracle Advanced Pricing
Oracle Advanced Product Catalog
Oracle Configurator
Oracle Contact Center
Oracle Bills of Material
Oracle iStore
Oracle Installed Base
Oracle Inventory
Oracle Order Management
Oracle Quoting
Oracle Service Fulfillment Manager
Oracle Telecommunications Billing Integrator
The mandatory applications provide core TSO functionality (see "Mandatory Dependencies for the Oracle TSO Solution", below). Others are required only if the related functionality is desired. TSO-specific implementation information for these applications is located within this guide. Additional information on setting up core functionality of these applications can be found in the relevant documentation for the specific application.
Note: Due to the limited or generic nature of the functionality provided by some of these applications, this document does not contain separate implementation chapters on Oracle Accounts Receivable, Oracle Advanced Product Catalog, Oracle Telecommunications Billing Integrator, or Oracle Trading Community Architecture.
Oracle TSO functionality requires integration with several other Oracle applications. Therefore, you must set up the required dependencies. The following table and sections outline the dependencies.
Note: This document provides additional setup information that is not included in the implementation guides of the Oracle applications that are required to support the TSO solution. You should use this document in conjunction with the implementation guides of each of these Oracle applications.
The following table lists the TSO functionality provided by the Oracle applications involved in the TSO solution.
| Application | Functional Dependency Related to TSO |
|---|---|
| Oracle Accounts Receivable | Payment Due with Order functionality |
| Oracle Advanced Pricing | Recurring charges; provides an attribute for periodicity |
| Oracle Advanced Product Catalog | Recurring charges |
| Oracle Bills of Material | Required for Oracle Configurator |
| Oracle Configurator | Configurable items; container models; partial reconfiguration of network items; computation of configuration deltas; persistence of attributes and Line Types; tangible item in a network container |
| Oracle Installed Base | For tangible items in a network container, provides an API to prevent reconfiguration of "locked" instances; stores purchased products |
| Oracle Inventory | Recurring charges; Payment Due with Order; provides a periodicity UOM class and UOM codes |
| Oracle Order Capture schema | Payment Due with Order; recurring charges; defaults the charge periodicity code on the quote line from Inventory; provides support for periodicity-based pricing; provides a source rule to derive the periodicity code |
| Oracle Order Management | Capable of capturing, booking, and provisioning orders; Payment Due with Order; recurring charges; tangible item in a network container; provides profile option to specify the periodicity UOM class; provides a system parameter to enable recurring charges; API dependency for Order Tracker and e-mail notifications |
| Oracle Trading Community Architecture | Stores information about customers and their interconnected relationships |
For information about implementing these Oracle applications, see the respective product implementation guides.
For Payment Due with Order functionality, the Oracle TSO solution has a dependency on Oracle Accounts Receivable (AR) via Oracle Order Management. AR provides an API that calculates the pay now amount. Oracle Order Capture schema handles pay now subtotals, pay now taxes, pay now shipping/handling, and pay now grand totals. Oracle Inventory provides the setup UI for item-level payment terms for Payment Due with Order. In Oracle iStore, Oracle Order Capture defaults item-level payment terms from the Inventory Item Master during the add-to-cart process.
For recurring charges, Oracle Order Capture schema handles the following:
Defaults the charge periodicity code on the quote line from the Oracle Inventory Item Master
Provides support for periodicity-based pricing
Provides a source rule to derive the periodicity code
Oracle Advanced Product Catalog seeds the attribute that stores periodicity of TSO items.
Below is a list of the dependencies on Oracle Order Management:
Provides the profile option to specify the periodicity UOM class. When selecting a periodicity while creating an item, the periodicity needs to belong to the UOM class.
Provides a system parameter to enable recurring charges.
API dependency for Order Tracker and e-mail notifications
Oracle Advanced Pricing provides a pricing attribute for periodicity. Oracle Inventory provides a periodicity UOM class and UOM codes.
During the RMA flow, Oracle Installed Base calls an Oracle Configurator procedure to remove tangible items from the configuration. The configuration is validated after the removal of the tangible item.
If a Model includes non-shippable items and at least one shippable (tangible) item, when the tangible item is shipped, Oracle Order Management ensures that the shipped quantity is not updated for all the other lines in the Container Model.
All ordering applications have a dependency on Oracle Order Management and Oracle Configurator for this functionality with the following limitations:
Only shipping (ADD) and discontinue (DISCONNECT) flows is supported for tangible items within a container.
Only shipping of standard items and kits within a container is supported; PTO and ATO models are not supported.
The quantity of the root model (MI, PTO model) will always be 1, and will be non-shippable.
The quantity of tangible items cannot be more than 1.
Replacement flows that transfer warranties by using the Oracle Installed Base "Replace By" relationship are not supported.
The use of extended attributes for tangible items is not supported.
No connectors are allowed from/to tangible items within a container.
Removal of tangible items from a configuration will result in deleting the item in Oracle Configurator and de-coupling the item from the configuration in Oracle Installed Base. In order to return the item that was removed from the configuration, the standard RMA process needs to be followed.
The following Oracle applications can be integrated to use the Oracle TSO solution:
Oracle Contact Center (TeleService)
Oracle iStore
Oracle Quoting
Oracle Service Fulfillment Manager
Oracle Telecommunications Billing Integrator
For information about the functionality related to TSO within these products, see the chapters, Oracle TSO Functionality and Using the Oracle TSO Solution, as well as the relevant setup chapters with in this guide.
The setup flow below shows a typical Oracle application setup sequence for the Oracle TSO Solution.
Set up products in the following order:
Oracle Inventory
Oracle Advanced Product Catalog
Oracle Bills of Material and Oracle Installed Base
Oracle Configurator
Oracle Order Management (workflows only)
Oracle Service Fulfillment Manager
Oracle Advanced Pricing
Oracle Quoting, Oracle Contact Center, Oracle Order Management (except workflows), and Oracle iStore
This section contains high-level implementation flows for recurring charges and Payment Due with Order functionality.
Following are the product-specific implementation flows for setting up recurring charges in the Oracle TSO solution.
For recurring charges setup in Oracle Advanced Pricing, attach the Charge Periodicity pricing attribute to a price list line or a modifier line.
For recurring charges setup in Oracle Inventory, set up recurring charges items with a value (e.g., Monthly) in the in the Charge Periodicity field.
Following are the Oracle Order Management setups for recurring charges:
Set the system parameter, Enable Recurring Charges.
Set the profile option, OM: UOM Class for Charge Periodicity, to Period.
Modify the Order Management UI to show charge periodicity.
For recurring charges setup in Oracle iStore, set the profile option, IBE: Enable Recurring Charges, to Yes.
For recurring charges setup in Oracle Quoting, expose the Charge Periodicity column from the Products subtab.
Following are the product-specific implementation flows for setting up Payment Due with Order in the Oracle TSO solution.
Following are the Oracle Inventory setups for Payment Due with Order:
For each item that will have a Payment Due with Order amount associated with it:
Set the Payment Terms field to Pay Now.
Enable the Invoiceable Item and Invoice Enabled check boxes.
Following are the Oracle Order Management setups for Payment Due with Order:
Set the Order Management system parameter, Installment Options.
Set up payment term or terms for Payment Due with Order amount.
Set up defaulting rules automatically default line-level payment terms and payment type.
Set up a credit checking rule to specify at ordering for the transaction type being used for the order.
Assign the following workflow processes to the line transaction types that will be used: Line Flow - Generic, Bill Only with Payment Assurance and Line Flow - Generic, with Payment Assurance.
Set up taxes to be calculated at the entry point, not inclusive in the lines.
Expose the following fields in the Order Management UI: Initial Due Balance, Due with Order, Initial Due Subtotal, Tax, Charges, and Total.
For Payment Due with Order setup in Oracle iStore, set the profile option, IBE: Enable Pay Now, to Yes.
For Payment Due with Order setup in Oracle Quoting, display UI elements specific to the Payment Due with Order amount.