Real Time Pipeline Is Not Setting Balance Impact Period Correctly For Future Cycle (DST - Daylight Saving Time) (Doc ID 1081025.1)

Last updated on NOVEMBER 29, 2012

Applies to:

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

Symptoms

When current or the future billing cycle includes the Winter/Summer time change date
(ex: 10th Mar - 10th Apr, with time change date on 28th Mar 2010),
the time offset is not correctly calculated for the start_time or end_time of the future period.

ex : Current billing period : 18th Feb - 18th Mar
Next billing period : 18th Mar - 18th Apr
Next billing period calculated on discount balance impact : 18th Mar 01:00:00 - 18th Apr
Trace from realtime pipeline :


DISCOUNT_PACKET
....
GRANTED_AMOUNT: <7.525084> :SET
AMOUNT: <7.525084> :SET
QUANTITY: <7.525084> :SET
VALID_FROM: <20100317230000> :SET ==>  one hour less here
VALID_TO: <20100417230000> :SET==> one hour less here
...


Trace from Cm :

CMAP fwd_op_to_em: resp flist: 0
...
0 PIN_FLD_POID POID [0] 0.0.0.3 ...
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.3 /account 59348 0
0 PIN_FLD_BAL_IMPACTS ARRAY [0] allocated 20, used 16
...
1 PIN_FLD_SUB_BALANCES ARRAY [assign] allocated 20, used 4
2 PIN_FLD_VALID_TO TSTAMP [0] (1271545200) Sun Apr 18 01:00:00 2010==> one hour extra here
2 PIN_FLD_VALID_FROM TSTAMP [0] (1268866800) Thu Mar 18 00:00:00 2010
...




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