Event Index for a PSO with a Crew is Not Retained When the Trouble Code Changes from Groupable to Non-groupable
Last updated on MAY 02, 2016
Applies to:Oracle Utilities Network Management System - Version 18.104.22.168 to 22.214.171.124 [Release 1.12]
Oracle Network Management for Utilities - DMS - Version 126.96.36.199 to 188.8.131.52 [Release 1.12]
Information in this document applies to any platform.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms