Error while defining Application Mapping "No Periods Were Identified For Loading Data Into Table 'TDATASEG'" in PBCS

(Doc ID 2358077.1)

Last updated on FEBRUARY 07, 2018

Applies to:

Oracle Planning and Budgeting Cloud Service - Version 17.12.54 and later
Information in this document applies to any platform.


There is a GLOBAL mapping defined for the year 2018 and when users try to define the Application mapping for the year 2018, it will not fetch the details for the newly added periods.

When we see the logs we can spot the error "No periods were identified for loading data into table 'TDATASEG'


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms