FDMEE Ignores Explicit Mappings When Target Application is Hyperion Planning
Last updated on AUGUST 08, 2016
Applies to:Hyperion Financial Data Quality Management, Enterprise Edition - Version 18.104.22.168.000 and later
Information in this document applies to any platform.
When running a data load rule to import a source file and load to a Hyperion Planning Application, the import completes without issue, however the validation is not mapping for two dimensions. Both dimensions have explicit mappings, however they are not being picked up at validate.
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