Changing a Job From a Non-Outage to an Outage Type Causes Customer Count to Drop to Zero
Last updated on DECEMBER 21, 2017
Applies to:Oracle Utilities Network Management System - Version 126.96.36.199 and later
Oracle Network Management for Utilities - DMS - Version 188.8.131.52 and later
Information in this document applies to any platform.
After changing the trouble type of a PDO to a non-outage, the job correctly changes to a non-outage, the customer count drops to 0 (as expected).
If the operator submits two new "No-Lights" calls for two different customers on the transformer, a new PDO is created (as expected).
If the operator then changes the trouble type of the previous non-outage job back to an outage (such as "NL - No Lights"), both jobs group together and the call count is 4 (as expected).
The customer count is 0 and the customer list is blank. (The number of customers should be the number of customers fed by the transformer.)
Originally, all of the customers were attached directly to the supply node (SND) that was attached to the transformer.
They had recently changed their customers modeling so downstream of each transformer were several "building structures" and attached to those were the supply nodes that had the customers.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms