FDM Load to Essbase Does Not Load All Records When One Error is Present (Doc ID 1360618.1)
Last updated on AUGUST 01, 2016
Hyperion Financial Data Quality Management - Version: 18.104.22.168.00 and later [Release: 11.1 and later ] Information in this document applies to any platform.
We are using the batch loader to automate FDM data loads. During the export stelp, when the load encounters a member that doesn't exist in the application it stops at that record. Is there a way to load all the other records and log the members that don't exist in the app?
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