Error With Timezone, Processing Forecast Data
(Doc ID 2717428.1)
Last updated on OCTOBER 23, 2020
Applies to:
Oracle Utilities Customer to Meter Base - Version 2.7.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
**Examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:
C2M - Customer to Meter
IMD - Initial Measurement Device
MDM - Oracle Utilities Meter Data Management
XAI - XML Application Integration
On : 2.7.0.3.0 version, Installation and Patching
ACTUAL BEHAVIOR
---------------
Error with Timezone, Processing Forecast Data
Submitting Forecast data into C2M from Quotation Management. In existing design from QM to MDM(2.0.1) we submit forecast data for the month of October in two parts, due to UK timezone using DST. In MDM the data is getting processed in GMT for the entire forecast period. In C2M when we follow the same approach, the first part (One hour) is being processed in BST and the rest of the month data is returning error through D1-IMDSeeder, as the system detects overcount.
EXPECTED BEHAVIOR
-----------------------
The system should use the same date/time format.
STEPS
-----------------------
1. Submitted XAI for forecasting Data
2. Executed FORECASTING Batch to process data from FACT table
3. IMD data crated through base business object (D1-InitialLoadIMDInterval); And also interval data created through base algorithm D1-IMD-DFLT
4. Imd data loaded for BST time zone which may issue in October forecasting data.
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 |