Hyperion Financial Data Quality Management (FDM/FDMEE) (MOSC)

MOSC Banner

Importing More Columns than Needed by Essbase

I am developing an FDM application and am looking to bring in more columns via a SQL query than I have dimensions in Essbase. I do not want to export these columns to Essbase, I just want them to sit in the import table. Basically, I want the end user to be able to drill down into the import table in FDM and see additional information beyond what they would get from Essbase. I managed to bring the extra columns of data into the import table, but if I map to ignore, it ignores the whole row and I end

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center