Importing data using FDMEE gets failed after applying 126.96.36.199.220 patch, when period mapping type is set to "Explicit"
(Doc ID 2609807.1)
Last updated on DECEMBER 02, 2019
Applies to:Hyperion Financial Data Quality Management, Enterprise Edition - Version 188.8.131.52.210 and later
Information in this document applies to any platform.
In Hyperion Financial Data Quality Management, Enterprise Edition 184.108.40.206.220 version
Users may use "Explicit" period mapping to transfer data between two Hyperion applications. During this process, the import process gets failed.
The same setup works fine when the period mapping is set to "Default", the gets imported successfully without any issues.
From the process details log
When explict mapping was working fine: (before 220.127.116.11.220)
DEBUG [AIF]: doAppPeriodMappingsExist - <APPNAME>-<DBNAME>: N
When explict mapping is not working fine: (after 18.104.22.168.220)
DEBUG [AIF]: doAppPeriodMappingsExist - <APPNAME>: N
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document