I suggest you take a look to the following support docs
i hope that helps
Thanks F.Amores for the reply.
I already have these docs but these docs are not fully clear on how to map Source to staging table and then staging table to ARM.
I need a self explainatory doc.
Pls share some self explainatory mapping concepts doc for FDMEE to ARM.
You have 3 ways of loading data into ARM depending on which source systems you want reconcile in it:
- If your source system is a file, you just have to create a file-based load to ARM
- If your source system is a supported source system then you have to create a data load for it with ARM as a target
- If you have to load balances from other source (Sub-ledger, database, etc.) you have to use Open Interface Adapter.
In your case you would have to create a file-based load.
All of this is very well explained in the implementation document you can find in support.
It also shows how to create the import formats and how to map Profile dimension and other dimensions.
Profile ID is typically a combination of your dimensions depending on how they are defined in ARM. For example, if you want to reconcile at Account-Company level, then you have to import into ARM "Profile dimension" values like A1-C1, A2-C2... where A and C are account and company respectively. You will have to configure this in your import format.
Hope that helps.
Can you please indicate which page no. shall I follow to map Source file to staging table and then staging table to ARM?
Also what process shall I follow to kick the data load start?
There is no staging table. What do you refer with staging table?
TDATASEG Table of FDMEE acts as staging table between FDMEE and ARM. That basically means... "ARM takes data from that table of FDMEE". In any case this is totally transparent for you so you don't have to worry about that.
You just load your file into ARM and you create maps between your file and ARM dimensions.
Data Loads are launched from ARM (Period Management).
You can refer to ARM documentation for that.