This content has been marked as final. Show 2 replies
In FDM the target period (month/year) and scenario is driven by the settings in your POV. The period and scenario you choose here determines where it goes in the target not the content of your file. Therefore you can have a data file for say November 2012 actuals but load via FDM with a POV set to January 2012 Budget and thats where all the data will go. In your import format you will therfore only set associations with the Mapped dimensions so that the relevant source values are associated with the correct dimension mapping table. Control tables control the associations for Periods and Scenarios/Categories. In your case the Period value in column one will not be used for any mapping activity.
You can put validations into FDM scripts to check the data content of the file matches the Period / Scenario settings in the selected POV but as FDM is primarily a user driven load process this isn't normally necessary.