Delayed Events For The Precreated Item Goes To Next Billing Cycle (Doc ID 850958.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.4.0.0.0 [Release 7.3.1 to 7.4.0]
Information in this document applies to any platform.
Information in this document applies to any platform.
**Checked for relevance on 04-June-2012***
*** Checked for relevance on 30-Aug-2016 ***

Goal

The Delayed events for the precreate true usage items goes to the next billing cycle. Why?

Example scenario:

Step 1: Configure Delayed billing for 5 days.
Step 2: Have usage item which is precreate true.
Step 3: Process CDR for the usage item in the delayed period. Created two events, Both the
events are rated on 14th June but the start time of the event is on 24th May. The current
billing cycle is from 11th May to 11th June. So the event occurs on the delayed periods.
Event 1 for item Precreate False.
Event 2 for item Precreate True.

The issue is the EVENT 1 for precreate false item went to the item of correct billing cycle.
The EVENT 2 for precreate true item went to the item of next billing cycle, even though the
output file from PRE is having the current billing cycle item.

 

Solution

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