Loadflag of 34 causing incorrect shifting of data during the dst period
Last updated on OCTOBER 07, 2014
Applies to:LODESTAR EIP - Version: 04.53
Oracle Utilities Meter Data Management - Version: 4.53
Oracle Utilities Billing Component - Version: 04.53
Oracle Utilities Quotations Management - Version: 04.53
Oracle Utilities Rate Management - Version: 04.53
Oracle Utilities Portfolio Management - Version: 04.53
Oracle Utilities Load Profiling and Settlement - Version: 04.53
This problem can occur on any platform.
Interval data output is being shifted improperly when loaded from the database using a loadflag of 34.
-- Steps To Reproduce:
Load cuts individually and compare them to the merged cuts. The individual cuts are wrong and the
merged cuts are correct.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms