Data Management Error "No Periods Were Identified For Loading Data Into Table TDATASEG" While Extracting Data From EPBCS Application
(Doc ID 2979619.1)
Last updated on DECEMBER 21, 2023
Applies to:
Oracle Enterprise Planning and Budgeting Cloud Service - Version N/A and laterOracle Planning and Budgeting Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
When attempting to extract data from Oracle Enterprise Planning and Budgeting Cloud Service (EPBCS) Application, the following error occurs.
ERROR
-----------------------
FATAL [AIF]: Error in CommData.insertImportProcessDetails
Traceback (most recent call last):
File "", line 1102, in insertImportProcessDetails
RuntimeError: No periods were identified for loading data into table 'TDATASEG'.
-----------------------
FATAL [AIF]: Error in CommData.insertImportProcessDetails
Traceback (most recent call last):
File "", line 1102, in insertImportProcessDetails
RuntimeError: No periods were identified for loading data into table 'TDATASEG'.
Changes
Alternate hierarchy for Period members has been added to Period Dimension in Target Application.
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |