Error During Account Reconciliation Manager (ARM) Data Load: "No periods were identified for loading data into table 'TDATASEG'" (Doc ID 2146112.1)

Last updated on FEBRUARY 03, 2023

Applies to:

Symptoms

You're attempting to run a data load in ARM.  You've confirmed that the data is successfully loaded into the Financial Data Quality Management Enterprise Edition (FDMEE) staging tables from the Open Interface tables.  The load fails with the following errors:

"DataLoad Rule execution has errored for the rule : ARM_OIF_BAL_Functnl.Session Failed :464501 : ODI-1217: Session COMM_LOAD_BALANCES (464501) fails with return code 7000.
ODI-1226: Step FAILED - Invalid Source System fails after 1 attempt(s).
ODI-1232: Procedure COMM Finalize Process execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File "", line 10, in
File "", line 162, in finalizeProcess
RuntimeError: ODI-1226: Step COMM Pre Import Data fails after 1 attempt(s).
ODI-1232: Procedure COMM Pre Import Data execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File "", line 7, in
File "", line 4247, in preImportData
File "", line 2884, in insertImportProcessDetails
RuntimeError: No periods were identified for loading data into table 'TDATASEG'.

When reviewing the ARM schema tables, the Periods can be seen within the TDATASEG tables.

Cause

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