Pipeline Even After BILL_NOW, Refers Older Item Poid During Rating
(Doc ID 2141247.1)
Last updated on MARCH 22, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
We have a custom table in which we load the item poid generated in the .out CDR while rating.
In this test, rated the 1st CDR, then did 'bill_now' on the account and then again rated a 2nd CDR post that. The 2nd CDR rating still loaded the old item poid (same as CDR1) in the custom table, although a new item poid got loaded in event_t. The expectation is that the CDR out file should have reflected the new poid, which should have got loaded in our custom table also.
Repeated the same test by restarting the pipeline after performing bill_now. This time, even the custom table got loaded with the new item_poid. When we perform regular billing, we do not face this issue. Both event_t and custom table get populated with new item poid.
And found that the pipeline listener logs get updated only in case of regular bill. There is no update for bill_now. We think this indicates that event notification is not happening in case of bill now. We are using the OOTB configuration for bill_now with no customization at all.
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