Last updated on NOVEMBER 30, 2011
Applies to:Oracle Communications MetaSolv Solution - Version: 6.0.15 to 6.0.15 - Release: 6.0.15 to 6.0.15
Information in this document applies to any platform.
If the account has inservice TNs, and the BTN is null, MSS should not force users to
assign a BTN even if another previous BTN has been assigned on other inservice service items for
a given account.
If the account has inservice TNs and BTN is being disconnected and BTN resides on seperate
inservice service items for the account then in the Error Response to the user provide what
Service Location and Level 1 product where the BTN exists so they will know where to go modify
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms