RuntimeError: No periods were identified for loading data into table TDATASEG. - Dec-25
in Planning
Summary:
Hello Experts,
We have an integration which pulls data from Reporting Cube to FS cube. For the first time we are facing this issue for Dec-25 which has 6 week and period is ending on 01/03/2026 for Source application.
Source Application has an explicit Mapping which is based on 4-4-5 calendar
Dec-25 period is ending on 01/03/2026
Target application uses Global Mapping –
Dec-25 calendar end on 12/31/2025
When we ran for Nov-25. Period key is passed as 11/30/2025 and Program completed normal, and data is loaded into target application.
Log shows Filters are applied for FY25 and Nov
When we ran for Dec-25, period key passed as 12/31/2025
Tagged:
0