Convertion Batch CIPVPRFI Record Key Has Not Been Replaced And CI_PROC_FLOW_K Is Empty (Doc ID 1909850.1)

Last updated on OCTOBER 04, 2022

Applies to:

Symptoms

Convertion Batch CIPVPRFI - Insert CI_PROC_FLOW runs successfully with no errors, but record key in production table CI_PROC_FLOW has not been replaced and production table CI_PROC_FLOW_K is empty

STGADM is the schema of the conversion environment
CISADM is the schema of the production environment (where the Insert Batches are inserting the actual final values and keys)
All records have been inserted in CI_PROC_FLOW table from STGADM to CISADM, but:

Schema: STGADM – Conversion environment
Record for STGADM
select * from stgadm.ci_proc_flow where proc_flow_id = '662599999'
returns 1 record

Old / new key table entry exists
select * from stgadm.ck_proc_flow where cx_id = '662599999'
returns 1 record

Schema: CISADM – Production environment
Record key has not been replaced for CISADM
select * from cisadm.ci_proc_flow where proc_flow_id = '662599999'
returns 1 record

Proc flow Keys Table (CISADM.CI_PROC_FLOW_K) is empty
select * from cisadm.ck_proc_flow
returns no records at all

For CISADM.CI_PROC_FLOW_CHAR key replacement has occurred:
select * from cisadm.ci_proc_flow_char where proc_flow_id = (select ci_id from stgadm.ck_proc_flow where cx_id = '662599999')
returns 4 records

EXPECTED BEHAVIOR
-----------------------
Production tables are expected to be correctly populated

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Precondition:
a.) Verify that the following DB tables are not empty
 CI_PROC_FLOW
 CK_PER
 CK_ACCT
 CK_TAX_ROLE
 CK_SA
1.) Switch hibernate.properties to point database to the conversion DB.
2.) Delete all records of STGADM. CX_PROC_FLOW and STGADM.CX_PROC_FLOW_K
3.) Verify record count of STGADM. CK_PROC_FLOW
4.) If record size from previous step is 0, then run batch job CIPVPRFK
Expected Result: Batch run completed successfully and STGADM. CK_PROC_FLOW is populated with values.
Actual Result: Batch run terminated abnormally (Batch Run status remain at 20 ) and console logs throws an error ' Error 173 Called program file not found in drive/directory'.
5.) Run batch CIPVPRFI
6.) Verify STGADM. CX_PROC_FLOW is not empty.
Expected Result: Batch run completed successfully and STGADM.CX_PROC_FLOW is populated with values.
Actual Result: Batch run terminated abnormally (Batch Run status remain at 20 ) and console logs throws an error 'Error 173 Called program file not found in drive/directory'.

Cause

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