What's new in Customer Journeys?

Connect and learn more!
RuntimeError: No periods were identified for loading data into table 'TDATASEG'. — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

RuntimeError: No periods were identified for loading data into table 'TDATASEG'.

Accepted answer
43
Views
2
Comments
edited Jan 24, 2024 7:56PM in Planning 2 comments

Summary:

Running into this error on the import, even though the periods are defined in Period Mapping. It works for Oct-23 period, but the error happens when running for Nov-23. I can't find a difference in period mapping. Any other ideas as to what may be causing this error?


RuntimeError: No periods were identified for loading data into table 'TDATASEG'.

Content (please ensure you mask any confidential information):


Version (include the version you are using, if applicable):

24.01

Code Snippet (add any code snippets that support your topic, if applicable):

2024-01-24 19:47:30,475 FATAL [AIF]: Error in CommData.insertImportProcessDetails

Traceback (most recent call last):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!