COULD NOT DELETE SP WHEN THERE IS NO EXISTING PENDING SYNC REQUEST
(Doc ID 1584053.1)
Last updated on MARCH 04, 2019
Applies to:Oracle Utilities Customer Care and Billing - Version 2.3.1 and later
Information in this document applies to any platform.
**Disclaimer:** This KM article may include the following abbreviations:
CCB/CC&B - Oracle Utilities Customer Care and Billing
SP - Service Point
SA - Service Agreement
BO - Business Object
OUAF/FW - Oracle Utilities Framework
MO - Maintenance Object
Problem on SP deletion.
Could not delete SP when there is no existing Pending Sync Request.
Steps To Reproduce:
1. Load an instance of one of the following MOs with an audit algorithm that creates a sync request:
Account, Item, Meter, Meter Configuration, Meter Read, Person, Premise, Premise, SA (Service Agreement),
SP/Item, History, SP/Meter History, Service Point.
2. Make sure that no Pending sync request exists for this object.
3. Delete the object.
4. Notice that a “<Entity Id>…not found” error is displayed.
Multiple Sync Request Pre-Processing algorithms:
1. Create 2 sync request pre-processing algorithms for the same algorithm type (algorithm 1 and 2) with different
corresponding type mnemonic soft parameters (type 1 and type 2, respectively).
2. Plug-in both pre-processing algorithms to a sync request BO. Algorithm 1 first, followed by algorithm 2.
3. Create an instance of the sync request BO for an entity with type = type 1.
4. Open the sync request created, notice that Sync Required element is set to F1NQ (Synchronization not required).
5. Transition the sync request. Notice that the sync is discarded with Discard Reason = Synchronization not required for <entity> Type.
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