My Oracle Support Banner

Web Call Entry Shows Duplicate Records in Event History If Customer has Multiple Calls For an Outage (Doc ID 2721235.1)

Last updated on OCTOBER 19, 2020

Applies to:

Oracle Utilities Network Management System - Version 2.3.0.2.0 to 2.5.0.0.0 [Release 2.3 to 2.5]
Oracle Network Management for Utilities - DMS - Version 2.3.0.2.0 to 2.5.0.0.0 [Release 2.3 to 2.5]
Information in this document applies to any platform.

Symptoms

On : 2.3.0.2.0 version, NMS Infrastructure

If a customer places multiple calls for a single event, or places calls for separate non-outage events and an outage event, and then those all get grouped together,
Web Call Entry's Event History for that customer is extremely confusing.
You get one-row-per-incident-per-event instead of just one-row-per-event.


There should be only a single entry for each customer

How To Repeat:

  1. Launch WCE on an OPAL demo system.
  2. For Account 2313303, place an All Out call.
  3. Save it.
  4. Again, for account 2313303, place an All Out, Cause: Pole Hit and Down call.
  5. Save it.
  6. Again, for account 2313303, place an All Out, Cause: Pole Hit and Down,
    Description: Pole Fire  call.
  7. Save it.
  8. Search for account 2313303.
  9. View the Call History.
  10. You'll see 3 calls.
    This is correct.
  11. View the Event History.
  12. Event History shows three identical rows for that event, which is rather misleading.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
 Fix Description
 Migration
References


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