This content has been marked as final. Show 8 replies
DATAEXPORT and a Load Rule, Data Synchronization, ODI
There are many tools that can extract data from Essbase.
Whoops! I forgot 126.96.36.199 has microcosting which is stored in a relational database.
What HPCM engine are you using? Standard or Microcosting?
Edited by: MattRollings on Aug 29, 2012 8:33 AM
This thread here seems quite useful to me as well.
Other than using data export with a load rule, can other options like using interface table, data synchronization across applications using EPMA be used?
I have posted a question on the using of interface table to sync data,
Data sync using interface table
does it appear that I might have missed some steps?
You can use data sync, but if you are moving data from one essbase application to another, it can be slow - especially with the multitude of dimensions that HPCM creates.
You are usually looking at 40,000 records per second out of planning (which is not fast).
I guess I am still missing what you are trying to do. You do not need to use the interface tables, what EXACTLY are you trying to do? If you are trying to seed Driver and Expense data into the HPCM calculation cube (Essbase BSO), just use load rules and DATAEXPORT calc scripts. If you are trying to get data into the staging tables for HPCM, you need to use SQL or an ETL tool.
Don't over-engineer the solution... it will end up being slow. Figure out a solution that has the least amount of steps, is efficient, and will scale well.
Your information is very helpful! Thanks!
Now I'm working on the data export and load rule. Here is part of the export file data:
DirectAllocation GenealogyAllocation AllAllocations SysAllocVar1 SysAllocVar3
FY12 [SCPOCCostSubCat].[NoMember] [ACPOCCostSubCat]@[A50121001M04] [LOPOCCostSubCat]@[A50121001M04] BegBalance [ACPOCActivity]@[MM01] [LOPOCActivity]@[MM01] Actual HEG14Y Working CostReceivedPriorStage 123.076923
FY12 [SCPOCCostSubCat].[NoMember] [ACPOCCostSubCat]@[A50121001M04] [LOPOCCostSubCat]@[A50121001M04] BegBalance [ACPOCActivity]@[MM01] [LOPOCActivity]@[MM01] Actual HEG14Y Working FixedDriverValue 8
Yet the loading returned an error as I believe there are some data which HP cannot cater those HPCM specific data, e.g. "[SCPOCCostSubCat]"
Should we write script / is there any functions that we can specify which which column of data to be exported and feed into HP?
If you are moving genealogy data (data from more than 2 non consecutive stages) you would pull the data from the ASO reporting cube. Try doing it the old fashion way, report script to text file, then an import to Planning. In the load rule get rid of all of the extra luggage that is embedded into the HPCM dimension member names.