Expired Device Command Activities Initiating Outbound Communications
(Doc ID 2512375.1)
Last updated on OCTOBER 07, 2019
Applies to:Oracle Utilities Smart Grid Gateway Adapter for Sensus RNI - Version 220.127.116.11 and later
Information in this document applies to any platform.
On : 18.104.22.168 version, Environment
Device Commands (On Demand Read, Remote Connect and Remote Disconnect) are configured in their respective Activity Types to expire after a certain number of days. When a Device Command Activity has been left in the ‘Waiting for Effective Date’ past this deadline and has been manually transitioned (or a batch is executed) to the next state, MDM proceeds to create an Outbound Communication to Head End-System. No check happens to verify if the Activity is past its expiration date.
Steps To Recreate
Create a device, device configuration, measuring component.
Create a service point and install the above created meter at this service point.
Configure device commission activity type with activity expiration days and expiration minutes.
Create a device commission activity on this device and populate effective date.
Activity will be created in ‘Waiting for Effective date’ state.
When the activity is in this state for long and past the expiration days / minutes configured on activity type, execute D1-CRWT batch to move the activity to next state.
The activity creates an outbound to head-end.
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