Due Date is Calculated as ter the Payment Term Changed Between BDOM and the Actual Bill Run Time (Doc ID 2113898.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

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

Goal

On : 7.5.0.10.0 version, Core Billing

Actual behavior:

Due date is calculated as per the payment term changed between BDOM and the actual bill run time.

Billing is identifying and picking up the last change in payment term and assigning due date accordingly.

Scenario:

1. In system there are multiple payment term configured such as 1001(NET_0 -> due_t = bill.end_t), 1002(NET_30, due_t = bill.end_t + 30 days), 1003(NET_5), 1004(NET_10).
2. On Jan 25 2016 an account is created with default payment term 1001 (NET_0) and credit card as payment Type.
3. So the billing cycle is set to be Jan 25 2016 00:00 - Feb 25 2016 00:00
4. Now on Feb 25 2016 08:00 hrs, payment term is changed from 1001(NET_0) to 1003(NET_5).
5. Again on Feb 25 2016 10:00 hrs, payment term is changed from 1003(NET_5) to 1004(NET_10). Please note that till now billing is not run for the cycle Jan 25- Feb 25
6. Now on Feb 25 2016 11:00 hrs billing is run, and due date is calculated as per the payment term 1004(NET_10).

Expected behavior:

Due date should be calculated based on the value which exist before BDOM which is NET_0.

Actually billing should not pickup any payment term change made after the current bill cycle which in this case ends on Feb 25 2016 00:00.

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