MDM On-Demand Read Using Creation Date To Determine Activity Expiration Date
(Doc ID 2414498.1)
Last updated on MARCH 27, 2019
Applies to:Oracle Utilities Meter Data Management - Version 126.96.36.199 and later
Information in this document applies to any platform.
MDM On-Demand Read Activity is using creation date/time to determine the expiration date/time. For any ODR activities with a future dated effective date, the activity is forced to timeout immediately after the ODR is sent to the Head-End System.
The issue appears to be with algorithm D1-WTTMOUTEX
It is expected that the Activity should determine expiration date/time based on when the Activity Outbound Communication was sent.
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