My Oracle Support Banner

Event Index for a Probable Service Outage with a Crew is Not Retained When the Trouble Code Changes from Groupable to Non-groupable (Doc ID 2127169.1)

Last updated on MARCH 12, 2021

Applies to:

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


A Probable Service Outage (PSO) with crew event was created.  The event index was not preserved when the trouble code changed from group to non-group.

In cases like this when the trouble code changes from groupable to non-groupable (or vice versa) or even from an OUT to a NON, the event index should be preserved if at all possible.  Otherwise, integration will need some way to correlate the two events and not act on seeing the cancel of the first event.

A PSO with one call (having a groupable trouble code) and a crew assignment will have it's event number change if the call is resubmitted (UPDATE_EXISTING_INC='Y') with a non-groupable trouble code.

If there is no crew on the PSO, the event index is preserved.


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

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