Conversion Batch Job CIPVCCTK Generating Inadequate Key Lengths For CC_ENTITY_FLG = PREM Records (Doc ID 2246065.1)

Last updated on MARCH 24, 2017

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.5.0.2.0 to 2.5.0.2.0 [Release 2.5]
Information in this document applies to any platform.

Symptoms

Currently CIPVCCTK looks at the STGADM.CI_CC records and uses the PER_ID column value to reference the STGADM.CI_PER table for corresponding person record. The PER_ID value used to gen the CI_ID is used in the following SQL
EXEC SQL
1414 //I INSERT
1415 //I INTO CK_CC
1416 //I (
1417 //I CX_ID,
1418 //I INIT_ID,
1419 //I CI_ID
1420 //I )
1421 //I SELECT
1422 //I TBL.CC_ID,
1423 //I (ROWNUM + :I-KEY-INS-IN-DATA.START-ROWNUM) ,
1424 //I SUBSTR(
1425 PTBL.CI_ID ,
1426 1 , 00003)
1427 //I ||
1428 //I SUBSTR(LPAD(
1429 //I (ROWNUM + :I-KEY-INS-IN-DATA.START-ROWNUM) ,
1430 //I 00010 ,'0')
1431 //I ,
143200003 + 1 , 00010 - 00003)
1433 //I FROM
1434 //I CI_CC TBL
1435, CK_PER PTBL
1436 //I WHERE
1437TBL.PER_ID = PTBL.CX_ID
1438 //I $#BSES* ORA-SPECIAL-INSERT-WHERE
1439 //I $#BSEE* ORA-SPECIAL-INSERT-WHERE


The CI_ID formed via the  SUBSTR(CK_PER.CI_ID, 0,3)||’00’||CK_CC.INIT_ID statement results in a key length of 7 rather than 10 (which is the correct value) since the STGADM.CI_CC records with unpopulated PER_ID column values creates keys wherein the first three characters are blank.  All STGADM.CI_CC records with CC_ENTITY_FLG = 'PREM' have no PER_ID column values.

Run CIPVCCTK background process. Verify that there are inadequate key lengths generated for Premise-based customer contact records.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms