MetaSolv Solution ASR SBILLNM Issue
(Doc ID 2541872.1)
Last updated on AUGUST 19, 2019
Applies to:
Oracle Communications MetaSolv Solution - Version 6.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 6.3.0 version, ASR
====================
ACTUAL BEHAVIOR
----------------------------
The ASR webservice is associating only the predefined address (From Access Customer details) of the SBILLNM and not the address submitted by carrier in the ASR creation web-service input tags
EXPECTED BEHAVIOUR
========================
The SBILLNM address given in the ASR Order should come.
Steps :
======
1-For ACNA XYZ ,configured Secondary Name, DEF (for e.g) is having address as ADDR1
2-Create order using the web-service giving the address as ADDR2 . Sample as follows :
<sbillnm>DEF</sbillnm>
<acna>XYZ</acna>
<fusf>E</fusf>
<street>ADDR2</street>
<city>ADDR2</city>
<state>ADDR2</state>
<zipcode>XXXXXX</zipcode>
3-ASR order gets created in MSS with SBILLNM DEF and address=ADDR1, but not with ADDR2 provided in the web-service.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |