FAQ About NPA NXX Values In BRM
(Doc ID 2044492.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.5.0]
Information in this document applies to any platform.
Purpose of this article is to provide answers to some queries concerning NPA/NXX values in BRM based on the below scenario :-
One would like to understand how NPA/NXX values are assigned in PIN_FLD_SHIP_TO and PIN_FLD_SHIP_FROM fields when a voice call is made.
For e.g., a call is made from USA, +19178414441, to France, +33787821169. Below is logged in PCM_OP_RATE_TAX_CALC input flist,
Here NPA/NXX values are 337878 and 191784 which are not valid at all. The actual valid one's are 378782 and 917841. As the NPA/NXX values are not valid, tax calculations are always wrong and customer is getting 0 taxes in all the cases. Basically NPA/NXX values are picked just after the '+' sign followed by 6 digits but this looks to be incorrect.
Business has impact as the tax on international calls is always 0.
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
|Questions and Answers|
|Q1. What is default way to assign NPA/NXX values ?|
|Q2. Based on what fields PIN_FLD_SHIP_TO, PIN_FLD_SHIP_FROM, PIN_FLD_ORDER_ORIGIN and PIN_FLD_ORDER_ACCEPT are populated ?|
|Q3. Which are the fields to customize in op_rate_pol_tax_loc in order to populate NPA values 378782,2,0 in op_rate_tax_calc input flist? Currently SHIP_TO is assigned with ";;;;337878,2,0" value.|
|Q4. Why the tax is 0 even though both SHIP_FROM (NewYork) and SHIP_TO (Canada) have valid NPA/NXX values ? While the same tax calculation when executed from vertex GUI is working correctly.|
|Q5: If one returns PIN_FLD_SHIP_FROM, PIN_FLD_SHIP_TO, PIN_FLD_ORDER_ORIGIN and PIN_FLD_ORDER_ACCEPT in the output of PCM_OP_RATE_POL_TAX_LOC, then, will the same values be considered during PCM_OP_RATE_TAX_CALC input flist ?|