No Cycle Fees In Trial Billing Due To A Problem With DST (Doc ID 556145.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 6.5.0.0.0 to 7.3.0.0.0 [Release 6.5.0 to 7.3.0]
Information in this document applies to any platform.
Problem is reported on Portal 7.2.1 release, but it can occur on any release.
***Checked for relevance on 11-Mar-2010***
Checked for relevance on 16-Mar-2012.


Symptoms

Trial billing did not generate cycle fees for 2 accounts with March 1 billing due to a DST issue.

There are 2 accounts with DOM =1 on Production server.

Since DST started around 2007 year end in Argentina, Portal server timezone changed from SAT3 (GMT-3) to SAT2 (GMT-2), as there was no OS DST patch, and on Jan 2 billing was run. These two accounts got picked up for billing, but there were no cycle events created (cycle forward). These 2 accounts were billed and there was an error in the log file and NEXT_BILL_T and FUTURE_BILL_T (as well as ACTG_NEXT_T, ACTG_FUTURE_T) were moved to next month and the month after next respectively.

TZ was changed back to SAT3 on Jan 3. Next day's billing generated cycle fees for these 2 accounts.  A temporary solution has been used to keep the BRM server timezone in SAT3 until the OS DST patch is released.

On Feb 27, 2008 (TZ is still SAT3), trial billing for these two accounts was run, but there was no cycle fees. Command used:

pin_trial_bill_accts -start 02/01/08 -end 03/02/08

On BILLINFO_T table, found the following data:

ACTG_LAST_T = 1201834800 (Fri, 01 Feb 2008 03:00:00 GMT) (= Feb 1 00:00:00 2008 on SAT3)
ACTG_NEXT_T = 1204336800 (Sat, 01 Mar 2008 02:00:00 GMT) (= Feb 29 23:00:00 2008 on SAT3)
ACTG_FUTURE_T = 1207018800 (Tue, 01 Apr 2008 03:00:00 GMT) (= Apr 1 00:00:00 2008 on SAT3)

This is supposedly what had happened.

1. On Dec 1st 2007 billing (SAT3), the account has:

NEXT_BILL_T:   Jan 1 GMT 3:00 2008
FUTURE_BILL_T: Feb 1 GMT 3:00 2008
ACTG_NEXT_T:   Jan 1 GMT 3:00 2008
ACTG_FUTURE_T: Feb 1 GMT 3:00 2008

2. On Jan 2 billing these time moved (on SAT2) to:

NEXT_BILL_T:   Feb 1 GMT 3:00 2008
FUTURE_BILL_T: Mar 1 GMT 2:00 2008 (= Feb 29 23:00:00 2008 on SAT3)
ACTG_NEXT_T:   Feb 1 GMT 3:00 2008
ACTG_FUTURE_T: Mar 1 GMT 2:00 2008 (= Feb 29 23:00:00 2008 on SAT3)

3. After Feb 1 billing (on SAT3), this account has:

NEXT_BILL_T:   Mar 1 GMT 2:00 2008 (= Feb 29 23:00:00 2008 on SAT3)
FUTURE_BILL_T: Apr 1 GMT 3:00 2008
ACTG_NEXT_T:   Mar 1 GMT 2:00 2008
(= Feb 29 23:00:00 2008 on SAT3)
ACTG_FUTURE_T: Apr 1 GMT 3:00 2008


Since NEXT_BILL_T, ACTG_NEXT_T are wrong, tried modifying the NEXT_BILL_T and ACTG_NEXT_T to Mar 1 GMT 3:00 2008; still no cycle forward events created, therefore no cycle fees.

From /account object, CHARGED_TO_T, CYCLE_FEE_END_T seem to be wrong too (as of Feb 27th 2008).

1 PIN_FLD_CYCLE_FEES ARRAY [1] allocated 20, used 6
2    PIN_FLD_CHARGED_FROM_T TSTAMP [0] (1201834800) Fri Feb 1 00:00:00 2008
2    PIN_FLD_CHARGED_TO_T TSTAMP [0] (1204336800) Fri Feb 29 23:00:00 2008
2    PIN_FLD_COUNT INT [0] 1
2    PIN_FLD_CYCLE_FEE_END_T TSTAMP [0] (1204336800) Fri Feb 29 23:00:00 2008
2    PIN_FLD_CYCLE_FEE_START_T TSTAMP [0] (1201834800) Fri Feb 1 00:00:00 2008
2    PIN_FLD_UNIT ENUM [0] 0



Steps To Reproduce (To simulate the same situation):

  1. Nov 1 2007: create an account
  2. Dec 1 2007: pin_bill_day
  3. Jan 1 2007: pin_bill_day
  4. Modify FUTURE_BILL_T, ACTG_FUTURE_T to Feb 29 23:00:00 2008
  5. Feb 1 2007: pin_bill_day
  6. From $PIN_HOME/apps/pin_trial_bill, run
    % pin_trial_bill_accts -start 02/01/08 -end 03/02/08
  7. Export the trial invoice from $PIN_HOME/apps/pin_inv
    % pin_inv_export -verbose -start 02/01/08 -end 03/02/08 -trial
     No cycle fees in the trial invoice.

 

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