Error in FDMEE Process...No Periods were identified
edited Mar 15, 2021 4:32PM in Hyperion Financial Data Quality Management (FDM/FDMEE) (MOSC) 1 commentQuestion
Product Name: PBCS Version 21.02.91
I'm running a data integration built by consultants (No longer available) that imports historical actuals in csv format and maps them into my ASO cube. This process worked fine for years FY 18 to FY 21, but when I tried to load data into FY 17, I get error message:
No periods were identified for loading data into table 'TDATASEG'.
I have checked Global Period Mapping and all periods in FY17 have been defined. I can see no difference in how the periods are set up in later years compared to FY 17.
Where should I look next?
0