Last updated on MARCH 02, 2017
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
Users are getting multiple issues which to us randomly reflect the new paths based on the 2 “valid” orders.
So when the provisioners try to work one or the other order, they have to take a best guess at which issue they should use to make the needed changes to these ckts.
When a parent circuit that has child riders is modified, pending design issues are created for these children that have the document_number of the order the parent is being
modified by. These child circuits are NOT on this order, so their status and activity with the order are both null (this can be seen clearly in the Design
Issues list of Connection Design Search/Maintenance).
Problem occurs during reconciliation when a parent connection is changed, causing the issue to its children circuits.
Users can’t fix the issue without a lot of work.
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