This appendix covers the following topics:
This chapter lists assumptions and restrictions for Oracle Telecommunications Service Ordering (TSO) functionality.
Following are general assumptions about the implementation and use of the Oracle TSO solution:
Users cannot make changes to pending orders. The following are not supported:
Placing new quotes based on pending orders
Modification of entered but non-booked orders by launching Configurator from the Order Management Sales Order Pad (users can modify the data on booked orders, but they cannot reconfigure them once the orders are booked)
Users can reconfigure order lines for an order that is in the Negotiation phase. The line workflow for an order line of an order that is in the Negotiation phase does not start until it becomes an order in the Entered state.
Users cannot reconfigure order lines that are part of a container model after booking the order.
Users can reconfigure order lines for an order that is in the Entered state if the workflows for the line types are the same. When users enter an order line, the workflow for the order line starts. For example, if a user reconfigures an order line such that its line type changes from Disconnect to Change, the workflow that implements the line types Disconnect and Change must be the same.
Orders that hold container models are solution-based models. Importing of solution-based models is not supported.
From the order, users cannot directly remove an order line that is holding an item instance that has been reconfigured in Configurator. To remove such an order line, users must: invoke Configurator, undo the change, and then explicitly remove the order line.
Users cannot copy order lines that hold reconfigured item instances.
Users cannot copy a booked order that is holding reconfigured item instances.
Orders that hold container models require transaction details to hold, for example, item instance attribute values and relationships. Importing of transaction details as part of an order import is not supported.
Users can cancel an order (or all order lines) belonging to the same model. To prevent cancellation of orders, implementers can set up processing constraints.
It is not possible to convert an order in the negotiation phase into an order if the revision of the item instance in the installed base is higher than the revision of the item instance on the order line of the order that is in the negotiation phase.
The line type for an order line that is holding a component that is part of a container model cannot be changed on the order line itself; the line type for such a line can only be changed by invoking Configurator. Configurator will feed the appropriate line type back to the order line based on the rules set up in Configurator.
Users can only reconfigure instances of quotes and orders for the sold-to customer who owns the service in Oracle Installed Base. For example, Customer X cannot reconfigure services belonging to Customer Y.
Following are the assumptions with respect to equipment in the Oracle TSO solution:
Equipment items are allowed in Order Management/Quoting only in Add and Disconnect flows.
Only the shipping of standard items and kits within a container is supported. Shippable PTO models or option classes, or any ATO models, option classes and items are not supported.
The quantity of the trackable root model (MI, PTO model) will always be 1 and will be non-shippable.
Shippable and inventory transactable items cannot have a quantity greater than 1.
Removal of shippable equipment from a configuration will result in deleting the item instance in Configurator and decoupling the instance from the configuration in the installed base. In order to return the item removed from the configuration, the standard RMA process needs to be followed for the decoupled instance.
A replacement flow, as understood by IB Replace_by relationship (i.e., transfer of warranties, etc.) is not in supported.
Using Oracle Installed Base extended attributes for shippable items in Oracle Shipping is not supported. This applies to items captured in Configurator.
If an item is flagged as Shippable, then it should also be flagged as Inventory Transactable and vice versa.
In-store equipment exchange or loaner is not supported.
No connectors to shippable items are allowed. This is because connectors can only be defined against PTO Models or ATO Models and those cannot be shippable. This requirement is avoids failing installed base transaction relationships pointing to already returned instances.
If a shippable item is ordered but not shipped (just handed to the customer by the reseller for instance), there is no way to capture the serial number of the new item.
Oracle Depot Repair integration is not supported.
The TSO solution is dependent on Instance Locking functionality (in Configurator, Installed Base, and Order Management).
The Container Model is not serviceable, since it is an artificial, non-trackable item on the order.
A tangible item is a serial controlled item as defined in Oracle Inventory
Following are the assumptions with respect to Payment Due with Order (Pay Now) amounts in the Oracle TSO solution:
The Payment Due with Order amount is charged through Oracle Receivables, not a third party billing system.
If a line has a Payment Due with Order component, the entire line is handled through Oracle Receivables.
If an order has all (only) recurring charge lines and a header level charge, the header-level charge is sent to Oracle Receivables.
Recurring charges are not included in the Payment Due with Order total.
The payment method for the Payment Due with Order amount is not programmatically restricted to credit cards only.
Deposits are not supported.
Following are the assumptions with respect to recurring charges in the Oracle TSO solution:
All of the selling applications use the same mechanism to default periodicity.
Oracle Order Management does not over-write the periodicity values from Oracle iStore and Oracle Quoting.
Following are Oracle Configurator integration assumptions about the implementation and use of the Oracle TSO solution:
To successfully reconfigure an instance, implementers must accurately follow all setup steps and tips.
Implementers should not connect two or more connectors from one source item to one target item.
It is recommended that users do not use pricing in the Oracle Configurator Summary window. It is recommended that all pricing of TSO products should occur through the hosting applications.
Configurator cannot infer disassembly sequences from the delta computations. A consultant must build the fulfillment workflows.
Certain types of substantial changes to a configuration model require the developer to re-validate existing instances. These changes include:
Changing a trackable, multiple instantiable child Model of the container model to non-trackable
Deleting a trackable, multiple instantiable child Model of the container model
Deleting a Connector node from one trackable model if there are connection rules with participants across the Connector
Adding, deleting, or changing a connection rule between trackable items
Adding, deleting, or changing any item that is a participant of a connection rule between trackable items
Following are Oracle Inventory integration assumptions about the implementation and use of the Oracle TSO solution:
The quantity of an IB Trackable item in a container model is restricted to one.
Following are Oracle Order Management integration assumptions about the implementation and use of the Oracle TSO solution:
Oracle Order Management restricts the quantity to 1 for non-serialized, IB Trackable, container Items. For tangible items, the quantity is also restricted to 1.
When item instances are selected for reconfiguration from the installed base onto the Sales Order or Quick Sales Order forms, the values for the Bill To Address and Ship To Address for the order lines default from the values stored for these attributes for the item instance in Oracle Installed Base (if available).
If a customer wishes to add more item instances into a container model that has already been added as an order line in the Sales Order or Quick Sales Order forms, the sales representative positions the cursor on the order line that is holding the container model and selects the function that invokes the Install Base (Item Instance Query) to select more item instances. When the Item Instance Query form is invoked in this way, the list of available item instances to select in the Install Base are restricted to only show item instances that have been set up in the Oracle Bills of Materials to be a part of the selected container model. In Oracle Quoting, this functionality is represented with a separate action, Add to Model.
Before you can find item instances from either the Sales Order or Quick Sales Order forms, you must specify the Customer field in the order header.
In the Sales Order Form or the Quick Sales Order Form, you cannot update the customer information in the order header or the order line when you have selected an item instance on a line.
TSO functionality is not available from the options window in Oracle Order Management. The TSO functionality is not available if the profile option OM: Use Configurator is N.
You cannot invoke the window to choose item instances back to order lines from Oracle Install Base after booking the order.
You cannot update order line attributes: IB Owner, Installed at Location, and Current Location that are holding a reference to an item instance.
If the function, Remove Unchanged Components, is invoked from the header level in the Sales Order or Quick Sales Order forms, then all the unchanged lines below any container model on the order will be removed. If Remove Unchanged Components is invoked from the line level, only the unchanged lines below the top model or sub-model of the line that the cursor resides on will be removed from the order.
Following are Oracle Quoting integration assumptions about the implementation and use of the Oracle TSO solution:
The function, Remove Unchanged Components, always removes all of the unchanged lines on the quote.
If a customer wishes to add more item instances into a container model that has already been added as an order line, the sales agent must search Oracle Installed Base to find the item instances. When the Item Instance Query form is invoked in this way, the list of available item instances to select in the installed base are restricted to only show item instances that have been set up in the Oracle Bills of Materials to be a part of the selected container model. This functionality is represented with a separate action, Add to Model.
Following are Oracle Service Fulfillment Manager integration assumptions about the implementation and use of the Oracle TSO solution: