Applies to:

Oracle Utilities Meter Data Management - Version 2.1.0.3 and laterInformation in this document applies to any platform.

Symptoms

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.