My Oracle Support Banner

CCB 2.7 SP3 MO-Audit Algorithm Into CASE Maintenance Object is Triggered By Refreshing Case Page Even if There Are No Changes (Doc ID 2904490.1)

Last updated on OCTOBER 27, 2022

Applies to:

Oracle Utilities Customer Care and Billing - Version and later
Information in this document applies to any platform.


**Examples provided in this article do not represent real life personal/confidential information**

**Disclaimer:** This KM article may include the following abbreviations:

CCB - Oracle Utilities Customer Care and Billing

CM - Customer Modification

DB - Database

MO - Maintenance Object

 On : version, ENV - Environment

When Case is loaded/refreshed without any changes, Sync Request is created (MO – Audit Algorithm is triggered).

If Case is loaded/refreshed without any changes, Sync Request should NOT be created (MO – Audit Algorithm should NOT be triggered).

The issue can be reproduced at will with the following steps:
1. MO – Audit Algorithm plugged in to CASE Maintenance Object (MO)  is triggered just by loading/refreshing the Case page, even without any changes.
This causes Sync Request record to be created, even though it should not be created in the first place.

The issue has the following business impact:
There would be several Sync Requests that would be created for the Cases unnecessarily. This would quickly take up DB space with clutter Sync Request records.


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.