This chapter covers the following topics:
This chapter provides information about adminstering the Oracle Telecommunications Ordering (TSO) solution after setup.
If you modify a container model in either Oracle Applications or Oracle Configurator Developer, model data can become out of synchronization with configured components at a customer's site. In this case, it is strongly recommended that you re-validate any installed configurations.
The following are examples of changes that occur in Oracle Applications to a container model that require you to re-validate installed configurations:
The following are examples of changes made in Oracle Configurator Developer that require you to re-validate a container model:
Deleting a connector node from a trackable model, when a rule contains participants from the connector's parent and the target model.
Adding, deleting, or changing a rule defined using a connector, when the rule contains participants from two trackable components.
Adding, deleting, or changing a rule in a trackable model that is not defined using a connector, but the rule propagates to a participant in a rule defined using a connector between trackable components.
Adding, deleting, or changing any item that is a participant in a rule defined using a connector, when the connector's parent and target are both trackable.
In this procedure, log in to Oracle Configurator Developer with Configurator Administrator or Configurator Developer responsibility.
Steps
Open the container model.
Republish the model.
In Oracle Quoting, create a new quote.
Search for all components within the customer's existing network configuration.
Select all of the components, and add them to the quote. If this step fails due to a large number of components, create multiple quotes with fewer sets of connected components, then continue the validation process separately for each quote. For each quote, try to select sets that have very few, if any, connections between each set.
If the changes made to the container model do not affect the customer's installed configurations, verify that all items appear with your No Action or Reprice Line Type. Because you define Line Types in Oracle Order Management, the exact text can vary. For more information, see the Oracle Order Management Suite Implementation Manual.
Verify that any items affected by the changes made in the container model are invalid within the configuration.
Submit the quote. If no errors occur, you have re-validated the configuration successfully.
If errors occur:
Enhancements to Oracle Service Fulfillment Manager (SFM) that assist you with notification errors while using the Oracle TSO solution include:
Incorporating enhancements to allow you to act upon notifications created as a result of a failed action
Improving interactions with third parties by automatically re-sending XML messages to them if the original XML message failed to send
Notification error-related tasks include:
"Retry Install Base Updates"
"Retry Failed Outgoing Messages"
"Manage Failure Notifications in HTML"
You should monitor your sales orders to check for error notifications.
In this procedure, log in to Oracle Forms with SFM System Administrator responsibility and navigate to Operations, Flow-Through Manager.
Steps
In Order Num field:
Specify the OM Order Number.
Choose Sales Order as Source Application in the Search window.
Click Go.
Expand the order in the tree to view the Service Fulfillment lines that Oracle Service Fulfillment Manager has received.
Choose a line and navigate to the Work Items tab.
Click Parameters.
View the parameters that the system passed from the line into Oracle Service Fulfillment Manager.
Oracle Service Fulfillment Manager (SFM) updates the install base with provisioning data after an order is complete in SFM. If the install base update fails, SFM sends a response notification to the SFM System Administrator. The System Administrator has the option to retry the failed action.
It is recommended that you routinely monitor sales orders to be aware of errors that can occur, such as when provisioning fails. Provisioning failure can occur when there is an incompatible discrepancy between the order and the information in either Oracle Service Fulfillment Manager or the install base. A provisioning failure appears on the Sales Order form in the status of the flow.
After you have fixed any problems pertaining to the incompatible discrepancy, you can retry to update the install base.
In this procedure, log in to Oracle Forms with SFM System Administrator responsibility and navigate to Operations, Flow-Through Manager.
Steps
Enter search criteria to find the Order Number.
Select the Order Number, and click View Details. The Order Information window appears.
Click the Notification button.
The Notification Inbox opens.
Click View Details.
For more information on your options, such as retrying to update the install base, refer to the Oracle Service Fulfillment Manager Implementation Guide.
The XDP Resubmit Failed Message concurrent program resends XML messages that have failed to be sent successfully to third-party systems. The concurrent program takes a message code as input. When you run the concurrent program, SFM identifies and attempts to resend all failed messages with the specified message code.
You should run the XDP Resubmit Failed Message program if:
You have information that some of your messages failed to send
You want to monitor and verify the sending of your messages.
In this procedure, log in to Oracle Forms with SFM System Administrator responsibility and navigate to Concurrent, Run Requests.
Prerequisite
You need to know the Message Code of the message that you want to check.
Steps
Select Single Request and click OK.
In the Name field, choose XDP Resubmit Failed Message.
Click OK.
Enter the Message Code.
Click OK. Any messages that the system had failed to send reappear in the Outbound Message Queue. An adapter program polls the queue to send messages from the queue.
To view messages in the Outbound Message Queue, choose Administration, Queue Console.
In the Queue Console, select and open the Outbound Message Queue. The Entries field shows the number of messages in the queue.
Select a message and click the View Details button.
SFM includes an HTML version of the Fallout Manager that you access to manage failure notifications. You view the automatically created failure notifications in HTML using Oracle Workflow. From the Workflow Notification page, you can navigate to the SFM HTML user interface to modify the workitem parameters and retry the failed action.
In this procedure, log in to Oracle Forms with Workflow Administrator Web (New) responsibility and navigate to Status Monitor area.
Prerequisite
See "Add Function for Menu Notifications" in the chapter, Set Up Service Fulfillment Manager.
Steps
In the Status Monitor area, click the Notifications link.
The Workflow Notifications page opens and displays: Type, Subject, and notification Date.
To view details of the order number notification, click the Subject hypertext link. The Notification Details page shows the selected failure notification message and hypertext links that let you fix the errors, such as Workitem Parameters.
In the Details area, click the link to update Workitem Parameters. The Workitem Parameters for Failed Order Line page opens.
In the Retry Value column, enter corrections to the workitem parameters.
Click the Update button. The Workitem Parameters for Failed Order Line page closes and the Notification Message Details page opens.
Click the Retry button.