This content has been marked as final. Show 4 replies
You only need to import the dimensions from a source file that you actually need to determine the target system dimensions.
If you are loading to HFM, each of the 12 dimensions is required but you can hard code a specific value (like [None]) in the import format.
If you are loading to Essbase, you do not need to activate all of the dimensions of the target cube, only those that actually need to be mapped. The others can be set in a load rule that you can specify in the adaptor.
Hopefully this helps.
Thanks for the response and I have situation like below.
Our Flat file has 11 dimensions whereas HFM needs 10 dimensions only from flat file dimensions. In this case how will we keep aside the extra dimension in flat file while loading? Please explain.
It's pretty straightforward, you just don't associate the superfluous dimension data in your source file with a target system dimension when you define your import format. FDM will only import data tah you tell it to.1 person found this helpful
Thanks for the helpful answer.