My Oracle Support Banner

ACTG_FUTURE_T In BILLINFO_T Table In BRM Wrongly Populated For FEB 1 Billed Customers (Doc ID 1994315.1)

Last updated on MARCH 22, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.0 to 7.5.0]
Information in this document applies to any platform.


Upon analysis of billinfo details for a customer's bill on February 1, it was found that ACTG_FUTURE_T field of BILLINFO_T table in BRM is populated as March 29. Due to this, after billing on March 1, ACTG_NEXT_T is populated as 29th of March and ACTG_FUTURE_T is populated as 28th of April. This is causing wrong dates in the invoice in the production environment, leading to rejection of invoice distribution.

  1 Creating a customer on 28th of Jan.
  2 Since it's a one day billing, the DOM will be 1, after the one day billing. And the current billing cycle is (1st of Feb to 1st of Mar)
  3 Move the PVT to 1st of Mar and perform billing, the current billing cycle is 1st of Mar to 29th of Mar

The problem is in step 3, billing cycle is 1st of Mar to 29th of Mar, instead of 1st of Mar to 1st of Apr.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.