Hi FDM experts,
I have an issue that I wanted to reach out to you on regarding fixed-width import formats and how to cater for my current scenario for export to Hyperion Planning.
I am working with a flat file (.txt) I need to import to FDM with the current format;
|Year||Channel||Product||Jan-MTD-Account 1||Jan-MTD-Account 2||Jan-YTD-Account1||Jan-YTD-Account2||....||Dec-YTD-Account2|
These are all fixed in width so the field lengths will need to be defined in the import format. The requirement for loading to the system is only a speciifc Month YTD value for both Account1 and Account 2.
If my chosen Month is 2013 Jan, I will only require columns F and G to be loaded. These are the issues I have identified;
Your help is much appreciated!
the solution you are looking for needs pivoting your source file.
Think that FDM, by default, only accepts files with one single column for amount. You have to pivot your file based on your logic and import the pivoted file.
Year Channel Product ... Jan-YTD-Acc1 Jan-YTD-Acc2 ...
2013 CH1 PR1 1000 2000
If your POV is Jan-2013, your data imported will look like:
Year Channel Produc Account Amount
2013 CH1 PR1 ACC1 1000
2013 CH1 PR1 ACC2 2000
All this process can be automated by playing with Import Scripts.
It is possible to do this by using an import script linked to the import format to create additional records however, whether it is practical in this situation is debatable. It might be easier to have a pre-import script that reads through the source file and creates the period files with the records as detailed in the previous response.