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

Last updated on MAY 02, 2016

Applies to:

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

Symptoms

A PSO with crew event was created.  The event index was not preserved when the toublel 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, integrations will need some way to correlate the two events and not act on seeing the CNL 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.

Cause

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