TBS Is Allowing The Change 'PSR' To Close Prior To Closure Of Disconnect ‘PSR’ (Doc ID 2307206.1)

Last updated on SEPTEMBER 13, 2017

Applies to:

Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.

Symptoms

On : 6.2.1 version, Work Management

ACTUAL BEHAVIOR
---------------
TBS is allowing the change 'PSR' to close prior to closure of Disconnect ‘PSR’


CURRENT BEHAVIOR:


While moving a TN from one customer to another you have to create two PSRs . A disconnect 'PSR' to DISCONNECT the TN from one customer and a change 'PSR' to make the TN IN-SERVICE to another customer. TBS is allowing the change 'PSR' to close prior to closure of Disconnect PSR when the change ‘PSR’ DD is in the SYSTEM QUEUE and completed by BGADMIN.

EXPECTED BEHAVIOR:

The DD task on a change ‘PSR’ is in the SYSTEM queue, TBS should not allow it to auto complete by BGADMIN if there are tn’s pending disconnect on another PSR. TBS should throw an error.


EXPECTED BEHAVIOR
-----------------------
The customer expects that if the DD task on a change ‘PSR’ is in the SYSTEM queue, TBS should not allow it to auto complete by BGADMIN if there are tn’s pending disconnect on another PSR. TBS should throw an error.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
POT045

1. Find a TN that's in-service.
2. Create a Disco order to disco the TN.
3. Assign tasks.
4. Create another PSR and assign the same TN.
5. Assign tasks and complete the DD task.
6. Now check TN INV, you'll see that the -0 is pending disco and the -1 is
in-service.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot complete the disconnect order.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms