ECM 8.1.2.5-t2t_KDD_CASE_CUST_PHONS Error Due To Unique Key Which Needs PHON_EXT_NB (Doc ID 3040699.1)

Last updated on AUGUST 14, 2024

Applies to:

Goal

KDD_CASE_CUST_PHONS unique key needs PHON_EXT_NB added.

The CUST_PHON table has the primary keys PK_1369: CUST_INTRL_ID, PHON_SEQ_NB
This table allows the following customer data with the same phone number and usage code but different phone extension:

CUST_INTRL_ID PHON_SEQ_NB PHON_NB PHON_EXT_NB PHON_USAGE_CD
G1000002372 1 4162972600 3301 B
G1000002372 2 4162972600 B

The same data successfully flows into the FCC_CUST_PHON with the PK_1742: PHON_SEQ_NB, CUSTOMER_SKEY, CUST_INTRL_ID

However, when the same data tries to get loaded into the KDD_CASE_CUST_PHONS a database error occurs because of the unique key constraint
UK_CASE_CUST_PHONS: CASE_CUST_SEQ_ID, CASE_INTRL_ID, PHON_NB, PHON_USAGE_CD

UK_CASE_CUST_PHONS needs the PHON_EXT_NB to successfully allow the data to successfully flow into the KDD_CASE_CUST_PHONS table
 

Solution

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