CMT Process Doesn't Work With Delayed Billing Functionalities (Doc ID 1543874.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

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

Goal

BRM system is configured with delayed billing functionality.
A delayed billing of 17 days is used.
Accounts that are in the delayed period, when migrated, have their cycle dates wrongly set.
If the NEXT_BILLING_DATE is in the past (because the account is supposed to be in the delayed period),
CMT automatically changes it to one cycle ahead. It will cause loss of one billing period. It seems CMT is not capable of recognizing BRM is working with
delayed billing and should accept a NEXT_BILLING_DATE with a past date (when this account is supposed to be in the delayed period).
 

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