My Oracle Support Banner

Older Events not Getting Captured Though ITEMs are Captured in the Invoicing (Doc ID 2315175.1)

Last updated on OCTOBER 11, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


On Oracle Communication Billing and Revenue Management (OCBRM) version 7.5.0  PatchSet 13, older Events (e.g. an item of Aug-2017, which had an event of Apr - 2017) are not getting captured though ITEMs are captured in the Invoicing.

It is observed that all events related to items are not getting captured in the invoicing.

Item to refer:
ITEM POID - 303940221438687888
ITEM TYPE - /item/payment

Customer had an item of Aug-2017, which had an event of Apr - 2017. As per the search flist, it found that the start date is being fetched as 27th May 2017. Below is the snapshot of the log:

Qn1: How the Date ranges are being fetched to extract the EVENTS Arrays?
Qn2: Is the 60 Days configurable one or is it default setting?
Qn3: Why the default value is set as 60 days? And can it be a configurable parameter to this field?


To view full details, 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 a vibrant support community of peers and Oracle experts.