SASP Batch Does Not Process Stop Reads On Stopped Service Agreements
Last updated on FEBRUARY 16, 2018
Applies to:Oracle Utilities Customer Care and Billing - Version: 2.1.0 to 2.1.0 - Release: 2.1 to 2.1
Information in this document applies to any platform.
The SASP batch process will never find stop reads as the SA needs to be in either a Pending Stop or Stopped status for the Stop Activity FA to be linked to it. The code only looks for Active SA’s. The description is contradictory in the it looks for SA/SP records for active SA’s but also states that it will process stop reads.
Users have to manually resolve missing stop meter reads on SA/SP records because the batch process does not work as expected based on the text in the algorithm.
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