My Oracle Support Banner

Start Of Brazil Daylight Saving Date not Considered when Computing Dates Using fm_utils_add_n_days (Doc ID 2553129.1)

Last updated on SEPTEMBER 18, 2019

Applies to:

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

Symptoms

SCENARIO:

The user has implemented a custom opcode related to payments, and this custom opcode implements function fm_utils_add_n_days to add one day. 

During the start of Brazil daylight saving time (DST), the current variable value of November 3, 2018 00:00:00 is added one day using fm_utils_add_n_days(1, &next_day_ts). It is expected that function fm_utils_add_n_days will return the first hour of November 4, but it results to November 3, 2018, 23:00:00. 

EXPECTED BEHAVIOR:

November 4, 2018 01:00:00 to be considered when computing dates as Nov 4 00:00:00 does not exist due to DST.

STEPS:

The issue can be reproduced with the following steps:
1. Create an account on Nov 4, 2018
2. Purchase a product
3. Run Bill Now
4. Submit a payment on Nov 6.
5. Execute get_late_payment opcode which is the custom opcode, which calls fm_utils_add_n_days(1, &next_day_ts) to add one day.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.