My Oracle Support Banner

F1-GENXO Batch Generating Delete Headers PK For BF Value MO In Incorrect Order (Doc ID 2821159.1)

Last updated on SEPTEMBER 15, 2022

Applies to:

Oracle Utilities Customer Care and Billing Cloud Service - Version 21A and later
Oracle Utilities Framework - Version 4.4.0.3.0 to 4.4.0.3.0 [Release 4.4]
Oracle Utilities Customer to Meter Base - Version 2.8.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On: 21A version, Environment

While running the generalized export batch, entities like BF Value are coming
out as deleted even though they exist in the tables. This is happening
because of the mismatch of the primary key sequence. While inserting the updated
entities to the F1_MO_UPD table, the sequence of the primary keys i.e. pk1,
pk2, pk3 etc are different than what is defined in the primary key constraint
of the table.

Steps to replicate:
1. Go to generalized export dashboard and enable the ongoing export to
Context Sensitive Zone MO.
2. Go to any context sensitive zone and edit some sequence or add a new zone.
3. Run the F1-GENXO batch.

Expected: The extract file should contain the updated values of this MO.
Actual: The extract file has the entry and is showing that as deleted=true.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.