DataExport command in Essbase

by diptirk on Sep.19, 2012, under Essbase

The jexport in System 9 had been replaced with the dataexport command in the EPM version. A great and fast method of exporting the data from Essbase. Had been using it since a long time and would prefer any time over the report script. DataExportLevel ALL | LEVEL0 | INPUT : This option is used to specify at what level do you need to export the data. When it is ALL, that indicates All Data at all levels would be exported, even the consolidated and calculated data. When it is LEVEL0, that indicates only the base members from Level0 data blocks; and when it is INPUT, it will export the data that had been loaded into the app via a data load or via lock-andsend. DataExportDynamicCalc ON | OFF : This option is used to indicate if the data export excludes the dynamically calculated data. When it is ON- the dynamically calculated values are included in the export file; and if it switched to OFF, then the dynamically calculated values are excluded from the export file. DataExportDecimal n : Any number between 0-16. This indicates the precision, not exactly the precision but the number of digits after the decimal that should be present in the export file. If the data in the database is 10.243333, and in the data export option you have specified the DataExportDecimal to be 2, then the value that gets exported in the data file is 10.24. DataExportPrecision n : Any number between 0-16. This also indicates the precision but the thing to keep in mind is that if you have both the option specified in the calc script, then the DATAEXPORTDECIMAL would hold precedence over DATAEXPORTPRECISION. DataExportColFormat ON | OFF : This option indicates if the data export is in columnar format or not. When it is ON- the data gets exported in columnar format and if it is OFF the data is not in columnar format. If you want to reuse the exported data for loading into some other application etc., then its a good idea to export the data in a columnar format. DataExportColHeader dimensionName : This option is used only when the data is being exported to a text file and is any of the dense dimension around which the other data is referenced in the export file. So in the script if you have specified that the Header is the Account dimension, the way the script behaves is all the data for a particular account gets exported before moving to the next account. DataExportDimHeader ON | OFF : Its a good idea to use this command if you want to re-use the data for loading into some other application. This option will insert the header record (all the dimension names used in the exported data file) at the beginning of the export file. DataExportRelationalFile ON | OFF : This option enables the data to be exported in a format where it can be directly used to load into a relational database. If the data is missing, then it is ignored and hence consecutive delimiters may appear. DataExportOverwriteFile ON | OFF : This option will replace the already present data export file with a new export file whenever the script is executed. DataExportDryRun ON | OFF : This is more for the developers use. When the switch is turned ON, the script would execute without exporting the data. But if you will check the log file, it will write all the information that would have been written, had the script been executed with the data being exported.
Leave a Comment more...

ActiveX Error in Hyperion Financial Reporting

by diptirk on Nov.03, 2011, under Hyperion Planning, Uncategorized

Run-time error 429 ActiveX component cant create object. I dread that thing when it pops up when I launch the Hyperion Financial Reporting Studio after installing. Even after configuring it using the Hyperion Configuration Utility doesnt help. The error still comes up each time you launch the Financial Reporting Studio. The way to get around is to run the following utility and restart the machine. %HYPERION_HOME%\BIPlus\install\bin\HRRunAnt.cmd