Hyperion Essbase integration with ODI

4,741 views
4,351 views

Published on

Steps to extract data from hyperion essbase and load it into relational table.

Published in: Education
1 Comment
3 Likes
Statistics
Notes
No Downloads
Views
Total views
4,741
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
268
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide

Hyperion Essbase integration with ODI

  1. 1. Steps to extract data from hyperion essbase and load it into relational database.There are three methods to be able to extract data from essbase; these are using either a Calc script (9.3onwards), Report script of an MDX query. If your essbase db is BSO then you will be able to use all of themethods, if it is ASO then you will only be able to use the report script or MDX query.You first have to create a calc script using the DATAEXPORT function that will extract to a text file.The DATAEXPORT function writes a dense dimension as the columns so you have to decide how youwant your data to look, as it will need to be matched against how you reverse the essbase database inODI. I am using the Sample. Basic db and have decided to use the Scenario as the dense dimension forthe columns.It is important to use :- DataExportDimHeader On;As ODI will consider the first 2 records to be header information, the extract file will also have to writeto location which will be accessible by ODI, this is not so bad if ODI is on the same server as essbase butbecomes more of an issue if they are separate, one of the reasons I am not so seen on this method.
  2. 2. Running the calc script produces the following output :-Now, you have to set up the connection to essbase in the topology managerData Server:-Physical schema:-
  3. 3. Logical Schema:-New Project:-
  4. 4. Import Knowledge Modules:-Insert New model:-
  5. 5. In the reverse section, select the context and the logical agent, the KM to use is “RKM HyperionEssbase..”To be able to return the correct data columns the KM options have to be updated.MULTIPLE_DATA_COLUMNS – Set to “Yes” as our exported data has multiple columns.DATA_COLUMN_DIMENSION – Set to “Scenario” as this data dimension in the exported data fileDATA_COLUMN_MEMBERS – Set to “Actual, Budget” as these are the members in the exported datafile.
  6. 6. Reversing the cube producesYou will notice the members Actual & Budget have been generated in the data DataStore.Establish target connection.Create data server:-
  7. 7. Physical schema:-
  8. 8. Logical Schema:-Target Model:-
  9. 9. Reverse engineer produces following output:-
  10. 10. Interface:-
  11. 11. Within the flow area the LKM to use is “LKM Hyperion Essbase DATA to SQL”The Options are important to get correct.
  12. 12. EXTRACTION_QUERY_TYPE :- Three possible types CalcScript, MDXQuery or ReportScript, you will needto manually enter the type if you are not using the default ReportScript.In this lesson set it to Calcscript.EXTRACTION_QUERY_FILE :- This is the location of the file that will be run to extract the data fromessbase, so obviously three file types. For the CalcScript you can enter the fully qualified location of thefile or if it resides in the essbase app directory you can just type the name of it without the file typesuffix.In this lesson, set it to ESSTEST ( name of calculation script ESSTEST.csc)EXT_COL_DELIMITER :- this is the columns delimiter that is being used, in my example the calc script iscreating a comma delimited file so I just enter ,EXTRACT_DATA_FILE_IN_CALC_SCRIPT – This only applies if you are using the query type of CalcScript, itis the location of the file created by the calc script., this file must be accessible by ODI.The other options are self-explanator.The IKM I used was “IKM SQL Incremental Update” with the optionsInsert - trueUpdate - falseFlow control - falseDelete All - trueCreate target table - trueSee below screen shots for more info.
  13. 13. Run interface.Open operator to see the execution status.
  14. 14. View data in odi itself.

×