Unbilled Earned Revenue Corresponding to Late Usage Not Reported Correctly (Doc ID 2199175.1)

Last updated on JULY 25, 2017

Applies to:

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

Symptoms

On : 7.5.0.14.0 version, General Ledger (GL)

After enabling the SegregateJournalsByGLPeriod business parameter, Unbilled Earned Revenue corresponding to late usage was not reported correctly.

Expected Result:
------------------
* Any late usage created in BRM on the 1st of the month, prior to the GL job execution, will be included in the GL run.
* Any late usage created in BRM after the GL job for the prior month (Example: usage for 6/25 created on 7/3) would be included in the subsequent month GL as it missed the GL run window

However, It looked like some late usage was properly going to the journal with old effective date but some late usage was still going to the new bucket even before GL run.


Changes

 

Cause

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