Product Cycle_end_t Is Incorrect If The Relative Offset Of Product Validity In Days Is Spanning Across DST
(Doc ID 1917822.1)
Last updated on FEBRUARY 18, 2019
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
Scenario:
1. Purchase a deal with a product, the end time of the product is set with an offset of 184 days and the start time is immediate.
2. Purchase another deal with product, the start time is set with an offset of 184 days.
Actual result :
The end time of the first product is 1 day less than the start time for the second product.
Example: Product-1 end_t:
0 PIN_FLD_CYCLE_END_T TSTAMP [0] (1422691200) Sat Jan 31 00:00:00 2015
Product-2: start_t:
0 PIN_FLD_CYCLE_START_T TSTAMP [0] (1422777600) Sun Feb 01 00:00:00 2015
Expected Result:
The end time for the first product is always the same as the start time for the second product.
Example: Product-1 end_t:
0 PIN_FLD_CYCLE_END_T TSTAMP [0] (1422777600) Sun Feb 01 00:00:00 2015
Product-2: start_t:
0 PIN_FLD_CYCLE_START_T TSTAMP [0] (1422777600) Sun Feb 01 00:00:00 2015
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 |
| Cause |
| Solution |
| References |