PBCS: Period mapping with non-default month name does not work correctly since 16.12.
Last updated on SEPTEMBER 19, 2017
Applies to:Oracle Planning and Budgeting Cloud Service - Version 16.12.53 and later
Information in this document applies to any platform.
When month name in Period dimension is different from default (ex. Apr), importing data by FDMEE fails in 16.12 or later. For example, when you select Apr-18 as Period, importing data fails with the following warning message:
WARN [AIF]: Warning: No records exist for Period 'Apr-18'
In 16.11, the data load rule worked fine.
Upgraded to 16.12.
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