Last updated on DECEMBER 15, 2013
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.0.0]
Information in this document applies to any platform.
This problem can occur on any platform.
***Checked for relevance on 16-Dec-2013***
Account is not getting billed when delay is on due to daylight savings and if the billing date is on Daylight savings day.
Accounts were 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 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.1 /account 12280515104 0
0 PIN_FLD_END_T TSTAMP  (1222599600) Mon Sep 29 00:00:00 2008
0 PIN_FLD_PROGRAM_NAME STR  "pin_bill_accts"
0 PIN_FLD_ACCOUNT_OBJ POID  0.0.0.1 /account 12280515104 0
0 PIN_FLD_BILLINFO_OBJ POID  0.0.0.1 /billinfo 12280515309 42
Then the only problem for this is the delay period, so to confirm this, change the end_t to 29th Sept 1AM and run billing and its works.
-- Steps To Reproduce:
1. Set config_billing_delay 1 in CM pin.conf
2. Create an account with DOM date on which daylight savings changes.
e.g: Oct 28th for New Zealand
3. Run billing exactly at the end of the bill cycle + 1 day delay period.
NOTE: account should be created before DST happens to system.
Actually result: Bill not create.
Expected result: Bill should create.
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