Data Problems with Circuits and Tasks when Supp Cancelled Order's "Circuit cancellation in progress..." Process Fails
(Doc ID 2165834.1)
Last updated on FEBRUARY 22, 2017
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
MetaSolv Solution version 18.104.22.1686
When an Engineering Work Order is Supp Cancelled and the "Circuit cancellation in progress..." process fails for a valid business logic reason, the order's tasks remain in a status of Ready and all prior task dependencies are ignored. The Supplement Type is rolled back to its previous value instead of being left as Cancel. This allows the DD task to be completed and the circuits on the EWO are incorrectly placed into a status of In Service.
For example: EWO order for a circuit has a Supplement Type of 2-New Due Date with tasks assigned. The DLRD task has been completed and the circuit in a DLRD Issued. The order is Supp Cancelled and the "Circuit cancellation in progress..." fails for "The cancellation process has been halted. There are one or more circuit(s) riding circuit [EXCHANGE_CARRIER_CIRCUIT_ID]." This error is followed by "One or more circuits could not be canceled and have been placed in 'Problem' status. These circuits must be designed manually." The Supplement Type is rolled back to 2-New Due Date and all tasks are open and in a status of Ready.
The following Service Request Notes are entered for the order:
When the Supp Cancel process fails, the tasks should revert back to their original state and not remain in a 'Ready' status without their initial dependencies.
Due to this issue, when the DD task completes, the circuits that were in 'Problem' status on the order can be updated out of 'Problem' status and completed. This allow the downstream order groups to complete both the DLRD and DD.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|