My Oracle Support Banner

BRM12 Delayed Billing Configuration priority order cm pin.conf vs business_params (Doc ID 2907074.1)

Last updated on MAY 15, 2024

Applies to:

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

Goal

On : 12.0.0.4.0 version, Core Billing

Delayed Billing configuration documentation links:

BRM 12: https://docs.oracle.com/en/industries/communications/billing-revenue/12.0/billing/setting-delayed-billing1.html#GUID-01BB9AAA-9E02-4ED9-A714-B6CF175F4A6A
BRM 7.5: https://docs.oracle.com/cd/E16754_01/doc.75/e16696/bll_setup_billing.htm#BRMBL204


Tested below three scenarios BRM 12:
=================================================
Scenario 1:

config_billing_delay set to 1 in Both cm and pin_billd pin.conf. ConfigBillingDelay business param value is set to 0.

In this case, delayed billing working as expected.

Scenario 2:
config_billing_delay set to 1 in Both cm and pin_billd pin.conf. ConfigBillingDelay business param value is set to 1.

In this case also, delayed billing is working as expected.

Scenario 3:
config_billing_delay set to 0 in Both cm and pin_billd pin.conf. ConfigBillingDelay business param value is set to 1.

Here, billing delayed is not working and billing is done on bill day itself.
====================================================================

So, It is clear that by configuring only business params, delayed billing is not working but as per BRM12 documentation, it should work.

So please suggest, which parameter need to be prioritized here ?

Also, what is Oracle recommendation for billing delay in BRM12 setup?
 

Solution

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
Goal
Solution
References


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