SOM Orchestrator Does Not Allow Updates

(Doc ID 2308939.1)

Last updated on SEPTEMBER 20, 2017

Applies to:

Oracle Utilities Service Order Management - Version 2.1.0.3 and later
Information in this document applies to any platform.

Symptoms


SOM Orchestrator does not allow updates  

Base update orchestrator does not allow updates on the FA if meter is a smart meter and activity status is “communication in progress”. For Smart Meters, It allows updates only if the order type is exchange.
 
You can check the following script : D1-UpdSpAct. It has following logic:
 
// if smart meter discard Update Orchestartor when specific activity is in Communication in Progress or Completed or Discarded states.  If smart meter and a meter exchange don't discard.
    if ("$isThisExchangeMeter = 'false' and $deviceCategory = 'D1SM' and (string(specificActivityBO/boStatus) = 'COMINPROG'  or string(specificActivityBO/boStatus) = 'COMPLETED'  or string(specificActivityBO/boStatus) = 'DISCARDED')")
        move 'F1RJ' to "parm/hard/nextStatusCondition";
        terminate;
    end-if;
end-if;


If FA is being worked in Field (not by SGG), then we should be able to send updates until the crew is onsite. The configuration done for this FA Type is a PassThru FA from CCB to SOM to the mobile system. For this the system should allow for the updates. We understand that Orchestrators do not allow for updates, however, PassThru FAs should allow for this type of update.

Steps to Recreate

  1. Create a Field Activity like Trim Tree.
  2. Make sure that Field Activity is in “Communication In Progress”
  3. Create an “Update Orchestrator” to change the start date.
  4. Update Orchestrator go to “Discarded” State.


Changes

 

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