DST Hour From 2-3 Not Converted To Local Time In Summary Usage Period (Doc ID 2394461.1)

Last updated on SEPTEMBER 27, 2022

Applies to:

Symptoms

DST Hour from 2-3 not converted to local time in summary usage period
When a usage transaction’s start and end dates are spanning a DST shift the outbound message with extracted interval does not represent the time shifts when SPI is 1 hour or less.

Steps:

The following are the steps to replicate
1. Create an Interval MC with 30 minute interval.
2. Create Usage Subscription using Get Interval Usage rule.
a. Setup the usage rule so that the target interval is 30 minute.
b. Setup the usage rule so that it extracts intervals.
3. Create usage rule for March 12, 2017 12AM to March 12, 2017 06AM.
4. Verify that the correct service quantities are reflected on the UT.
5. Transition the UT to sent status and check the outbound message created.
6. Verify that the summary SQs does not reflect the DST shift.

Cause

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