I am getting issue at Validation stage. It is showing the below. The custom1 dimension is showing missing value. Does it mean am i missing any Custom1 mapings?
|FM Entity||PartitionKey||CatKey||PeriodKey||View||FM Account||ICP||Custom1||Custom2||Custom3||Custom4|
|JpnCorp||839||12||11/30/2013 0:00||YTD||10030||[ICP None]||[None]||[None]||GLLoad|
|JpnCorp||839||12||11/30/2013 0:00||YTD||10231||[ICP None]||[None]||[None]||GLLoad|
|JpnCorp||839||12||11/30/2013 0:00||YTD||10305||[ICP None]||[None]||[None]||GLLoad|
Yes you do. On the workflow validation screen, select the amount field and left click. It gives you an option to drill back to the import source transactions (workflow import screen). From the source transaction do the same and it gives you an option to view the mapping conversion rules used for each dimension
from the discussion so far, it would suggest that the custom 1 source members are not actually being imported. (you did not respond to an earlier question about confirming if the source value appears on the import screen. Have you checked your import format to ensure that custom 1 is specified, and picking up the correct source field and does not have an import script attached which could be giving the blank source value . Also in your mappings have you got a default (catch-all) mapping record?
Further have you checked the adaptor to confirm the custom 1 dimension is active and not defined as "lookup"?
Sorry for the late reply
Did you import the mapping for UD1 with a template? Are there any preceeding/trailing spaces for the mapping for UD1?
"No preceeding/trailing spaces for mapping for UD1"
Have you checked your import format to ensure that custom 1 is specified,
I forgot to create import format for custom1.
I created Custom1 import format and ran the process again. Now it is not showing empty for custom1. but i am getting intersection validation error. A new page opened and for some entities validation got failed(invalid intersection).
Thanks for your help.
Unchecking the Intersection Validation flag just means the errors will now occur when you load the data into HFM, instead of being trapped in FDM which provides you with the chance of correcting the errorsbefore loading the file. you will now end up with a partiually loaded file into HFM which may not be what your users are expecting!