PER_KEY is not updated in CF_SA table When the Main Customer for an Account is Changed in CCB (Doc ID 3058133.1)

Last updated on NOVEMBER 08, 2024

Applies to:

Oracle Utilities Advanced Spatial and Operational Analytics - Version 2.8.0.2.0 and later
Information in this document applies to any platform.

Goal

We are facing data mismatch issue for below scenario.

Scenario: When the main customer (PERSION_ID with MAIN_CUST_SW=Y) for an account is changed in CCB, and if any changes happened in CCB for any 1or 2 SAs for that particular account , then in target table CF_SA the PER_KEY is not updated for all SA's available for an Account.

As the Main customer is changed for an account, then in CF_SA all records should be pointing to new per_id and eventually all PER_KEY should have updated key value. But currently it is not happening.

Solution

	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

Goal

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.

PER_KEY is not updated in CF_SA table When the Main Customer for an Account is Changed in CCB (Doc ID 3058133.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!