Hello Bob
In your case, if I understood you correct, you want to build
the system and then load all time periods, master data and key figures via flat
files. To do so, the compressed file of .zip format needs to contain the
manifest and the data file.
The data has to be a .csv file. For master data, you can see
the required headers in the configuration section under “Master Data Types”.
You should include all required attributes as well as all those you want to
load. I believe you should follow the same order.
The time profile file always contains the period ID, start and
end date, period description as well as parent ID. It has to be loaded before
you load the key figure data.
When loading key figures, keep in mind that only store key
figures are loaded at the key fields of their base planning level as well as
the date field.
The manifest is an .xml file. It tells the system how to
handle the data imports, e.g. the .csv file name, the object you are loading, delimiters,
Planning Area, Scenario, etc.
A manifest pretty much represents a batch run.
Lastly, I am afraid but I don’t have a document describing
those steps myself.
The above are my notes from the training class I took.
Hope this helps,
Jens