Unable to Customize To Do Message for Device Events (Doc ID 2479533.1)

Last updated on MAY 31, 2024

Applies to:

Symptoms

When a device event to do is created because the meter does not exist in MDM, the to do message is a very generic "To Do created for Device Event. (11801, 12306)". If we wanted to create a message override to suppress the creation of the to do, the override will suppress more than we need because of the generic nature of the message. If you look at the logs it does show that the to do was because the meter does not exist in MDM (11801,12374 "There is no device for Head End %1 with Device Identifier Type %2 and Value %3."). This should be the message category and number combination that should be used for this to do.

Steps to Recreate

1. Search for Device Event ID (in Error state) due to the meter does not exist in MDM. In the Device Event screen it should show Device Event Type as Error and Device field is blank.
2. Reprocess Device Event
3. Go to log: Device event To Do is created because the meter does not exist in MDM, the to do message is a very generic "To Do created for Device Event. (11801, 12306)".

Expended Behavior

It is expected that the application will suppress To Do creation for specific messages when device event creation hits an error.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.