ImportNewServiceLocation_v2 API uses inactive address creating new end user location
Last updated on MAY 16, 2012
Applies to:Oracle Communications MetaSolv Solution - Version 6.0.15 to 6.0.16 [Release 6.0.15 to 6.0.16]
Information in this document applies to any platform.
This problem can occur on any platform.
On 184.108.40.2069 in Production:
Execute ImportNewServiceLocation_v2 PSR API method that creates a new end user location that is associated to an inactive MSAG address causing this end use location to be unusable in the MetaSolv application.
-- Expected Behavior --
The ImportNewServiceLocation_v2 PSR API method should create a valid/active end user location.
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Execute ImportNewServiceLocation_v2 PSR API method using an existing MSAG Address from the
ADDRESS table that has the ACTIVE_IND set to "N"
Sample PSRSvcLocation structure:
2. Import NewServiceLocation_v2 API method executes successfully and creates a new end user location that is associated to the inactive ADDRESS_ID on the ADDRESS table
3. Open MetaSolv and search for this newly created address
4. This new End User Location is not active because the MSAG address that it is associated to on the ADDRESS table is inactive
-- Business Impact --
Due to this issue, users cannot order items for this end user location and/or search for this end user location in the MetaSolv application.
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