MSS 6.3.0 | TN Conflict Validation Missing On Disconnect Cancel Of Trunk Telephone Numbers
(Doc ID 2747192.1)
Last updated on APRIL 08, 2021
Applies to:Oracle Communications MetaSolv Solution - Version 6.3.0 and later
Information in this document applies to any platform.
MSS 18.104.22.1680 | Trunks
When reusing a Pending Disc Telephone Number where the Telephone Number was disconnected without disconnecting the service item, users are able to supp cancel the Disconnected TN's order even though the pending TN's order is still open. Users realize the issue only during the completion of the DD task of the pending TN when the application stops the DD completion stating a TN conflict. This requires a rework of the order.
MSS should not allow the TN-Disconnect Order to be Supp-Cancel in this scenario .
Scenario in which this issue is happening:
1-A change order is created from a Trunk Product which have TNs assigned.On this order , one or ,more TNs are disconnected w/o disconnecting the Trunk service Item .
2-Create a new order and pull the same disconnecting TN/TNs on this order as New. A new TN-suffix is generated in the TN Inventory in "Pending" status . The status of the previous suffix is "Pending Disconnect"
3-Supp-Cancel the order created in step 1 and MSS allows the Supp-Cancel to complete and also allows the DD task of this order to complete.
4-In the TNI now the older suffix is "In-Service" while the latter suffix is in "Pending" . Users don't come to know about this corruption in the TNI until they complete the DD task of the New Order.
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