Mobile Number Change End Date Is Not Set Correctly In Pipeline Cache
(Doc ID 2487420.1)
Last updated on DECEMBER 01, 2023
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Pipeline Manager
Migrated the complex legacy data using PL/SQL to BRM database.
In mobile number change scenario, user added few rows with different effective_t value in AU_SERVICE* tables for a service.
For these mobile numbers the end date is not properly set in pipeline memory, and because of that, all the old CDRs are getting rated where as they should have got rejected.
Here is the data seen from database, for the account in question:
It is showing that cell number xxxxxx2057 is valid from 14-MAR-18 to 19-JAN-2038, whereas its valid period is only from 14-MAR-18 to 19-MAR-2018.
So it is showing 2147483647[19-JAN-2038] for the cell number in pipeline memory but data in au_service_t table looks fine. why ?
NOTE: For a new account created in the Same system and mobile number change scenario for that account is all working fine.
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