CDRs Were Picking The Wrong Revisions Of The Product From Memory
Last updated on OCTOBER 03, 2013
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.3.1]
Information in this document applies to any platform.
- Purchased a product for telephony on 10 Feb (ex: suppose with rateplan code ABC123) and priority is 100.
- Suspended that product on 12 Feb
- Rate a call started on 11 Feb
- Call is rated with default rateplan where as it is supposed to be rated with rateplan ABC123 of priority 100.
The below description should be the actual behaviour with the help of an example
Suppose Customer A is having 3 /purchased_product say P1, P2 and P3 and their revisions are as below,
Revision 1 - Jan 1 to Jan 10
Revision 2 - Jan 11 to Jan 20
Revision 3 - Jan 21 to Jan 30
Revision 4 - Jan 31 Onwards...
During pipeline startup, latest revision of all 3 purchased products P1, P2 and P3 will be loaded into pipeline memory.
If usage pertaining to purchased product P1 is passed dated Jan 15, then revision 2 of P1 will need to be refreshed/loaded into memory.
If usage pertaining to purchased product P2 is passed dated Jan 06, then revision 1 of P2 will need to be refreshed/loaded into memory.
So at this point of time; revision 2 of P1, revision 1 of P2 and latest revision of P3 will be available in memory.
In short, at any given point of time one particular revision of all purchased products owned by account A will be available in memory, depending on the
last usage passed.
If one is performing a test with lot of late CDRs one may hit a small performance issue due to the above ,but in a normal production scenario the CDRs would be more or less organised and this would be negligible
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms