How Is FCT_Zoning Handling B_NUMBER Including Special Characters
(Doc ID 1911618.1)
Last updated on MARCH 25, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]Information in this document applies to any platform.
Goal
Special characters seems to be inproperly used by Pipeline Engine in finding a match in INTEGRATE.IFW_STANDARD_ZONE.
For example:
A_NUMBER is “0639371347546” and B_NUMBER is “063*2474”.
The expectation is that the CDR will get suspended, while it is not actually. On the other hand, Pipeline finds a match in the standard zoning table if “*” is omitted frm B_NUMBER.
When B_NUMBER passed in the CDR contains a special character "*", if we look into the IFW_STANDARD_ZONE that is configured, there should be no matched, thus the CDR should get suspended.
However, a CDR formed like that is successfully processed, while if you omit the special character in the B_NUMBER and search "0632474" in IFW_STANDARD_ZONE.DESTIN_AREACODE, there is a match.
Solution
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
| Goal |
| Solution |
| References |