Problem With Day Light Saving At Exactly Midnight In The Cycle Of Change.
(Doc ID 1517750.1)
Last updated on MARCH 29, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.5.0.0.0 [Release 7.4.0 to 7.5.0]Information in this document applies to any platform.
Symptoms
BRM used the wrong hour for the cycle fees generated during the billing cycle. This problem occurred only for the bill cycle that coincides with the Daylight Saving hour change.
For example the cycle fees generated:
0 PIN_FLD_CYCLE_FEES ARRAY [1] allocated 20, used 6
1 PIN_FLD_CHARGED_FROM_T TSTAMP [0] (1350788400) Sun Oct 21 01:00:00 2012
1 PIN_FLD_CHARGED_TO_T TSTAMP [0] (1353466800) Wed Nov 21 01:00:00 2012
Should be:
1 PIN_FLD_CHARGED_TO_T TSTAMP [0] (1353463200) Wed Nov 21 00:00:00 2012
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! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |