Unexpected Cycle Arrears Fees Generated (Doc ID 742787.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 6.5.0.1.1
This problem can occur on any platform.

Symptoms

-- Problem Statement:
Unexpected Cycle Arrear (CA) events are generated during billing: closing billing of month M generates CA events for both month M and month M+1.

-- Steps To Reproduce:
Step 1: On Jun 01, account creation (with several product purchases).

Step 2, on Jun 30, product cancel, forward-dated to Jul 1.

This is done via the following opcode and input flist:

D Mon Jun 30 00:01:38 2008 billsvil2 cm:28930 fm_bill_cancel_deal.c:135
op_bill_cancel_deal input flist
# number of field entries allocated 20, used 6
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 4519847 0
0 PIN_FLD_PROGRAM_NAME STR [0] "OLI_D10"
0 PIN_FLD_START_T TSTAMP [0] (1214863200) Tue Jul 01 00:00:00 2008
0 PIN_FLD_END_T TSTAMP [0] (1214863200) Tue Jul 01 00:00:00 2008
0 PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.1 /service/telco/gsm/tim_gprs 4519447 10
0 PIN_FLD_DEAL_INFO SUBSTRUCT [0] allocated 20, used 1
1 PIN_FLD_NODE_LOCATION STR [0]
"billsvil2#28625/1#20080926-151247.311:billsvil2#28625/1#20080926-151247.311"

As a result of this cancel, account's billing is triggered (account's DOM is 1 and account has not been billed yet). This is as expected.

Billing generates Cycle Arrears fee events for the month of June (i.e. with an earned range June 1- June 30), as expected, but also for the month of July, and this is unexpected.

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