You can specify the mapping and update your mapping table, so that quarter data will be mapped with the Months. Also you need to modify your import profile. After doing this you need to select the location and period in FDM and then you can upload the data.
But this still require uploading separately and each time only can load data to one period. Is there anyway to upload four quarters in one go by uploading one data file?
Multi-period loads are supported in FDM Classic using the multiload functionality. However, for this to be utilised your source files must match a specific format. For details see p.150 in the FDM admin guide.
thanks for the help. But the file format is fixed, expected to be produced by essbase data export.
I would like to know if there are any ways to handle this kind file other than the standard multiple period load function.
There is no out-of-the-box functionality to support this. If you want a solution to load a specific multi-period file format it will require a fair amount of custom scripting and will not be supported by Oracle.
thanks for the reply
for the customized scripting, do you Have any ideas on the logic or functions I can use ? I have little experience to the FDM scripting, do you have any materials/website about that ?
There is some material on scripting in the FDM admin guide, although fairly generic is a good starting point. Outside of that review the existing adapter scripts to see how they process the period information. However, you need to be pretty confident in what you are doing scripting wise before modifying the adapter scripts (always create a copy of the adapter and use the copy to experiment with). As you have little experience with FDM scripting your safest approach would be to engage someone familiar with the FDM API to help you out as it will save you a lot of time and pain in the long run if this is the oute you want to go down.
If it's FDM Classic you could set Period Dimension as a custom dimension in the adapter.
Then you create mappings for the period dimension
Q1 -> Mar
Q2 -> Jun
Lastly you would need to modify the export action so your "Custom Period" dimension would be exported instead of the POV Period.
This solution would be working for data load but you would have issues for drill through.