My Oracle Support Banner

Pin_bill_accts Not Closing Accounts when DST Change on DOM Date (Doc ID 744095.1)

Last updated on AUGUST 20, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.0.0.0.0 to 7.0.0.0.0 [Release 7.0.0]
Information in this document applies to any platform.

Symptoms

Accounts are not getting billed when delay is on due to daylight savings and if the billing date is on Daylight savings day.

Accounts are picked by pin_bill_accts MTA application and passed to the worker thread. It’s the problem in the worker thread where the account was not billed and it was just passed through.

Worker thread is sending the following input flist to PCM_OP_BILL_MAKE_BILL opcode":

# number of field entries allocated 6, used 5
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 12280515104 0
0 PIN_FLD_END_T TSTAMP [0] (1222599600) Mon Sep 29 00:00:00 2008
0 PIN_FLD_PROGRAM_NAME STR [0] "pin_bill_accts"
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 12280515104 0
0 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 12280515309 42

The problem is only at the delay period, because billing works fine after changing the end_t to 29th Sept 1AM.

-- Steps To Reproduce:
1. Set config_billing_delay 1 in CM pin.conf.
2. Create an account with DOM date on which daylight savings change.
    e.g: Oct 28th for New Zealand.
3. Run billing exactly at the end of the bill cycle + 1 day delay period.

NOTE: the account should be created before DST happens to system.

Actual result: Bill not created.

Expected result: Bill should be created.

Changes

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.