Importing Data

Note the following important information when performing data import operations:

  • The data types of the driver members must be the same as the imported value data types or data errors will occur. Date fields must specify the format with a /DF switch and the data type of the driver member must be type date. Similarly, a Smartlist member must be of type smartlist if the Smartlist value exists in the application and in the specified Smartlist. Text values must be bound to driver members of type text.

  • In addition to driver member types, the evaluation order of dimensions must be set so that the driver member values are evaluated correctly.

  • Outline Load utility data import does not import #missing values. To ensure the correct Oracle Essbase cells will contain #missing values, clear the block (which sets all cells in the block to #missing) to be loaded with the /ICB command on all data imports. See Clearing an Essbase Block Using the /ICB Parameter.

To import data from a relational database:

  1. Back up the Oracle Hyperion Planning relational store and the Essbase data. See the Oracle Enterprise Performance Management System Backup and Recovery Guide.
  2. Create a relational table in an application.

    The following graphic is an example of a relational table named Data_Table1 located in database Test_300A:


    Example of a relational table used when importing data from a relational data source.
  3. Create a Planning application form.

    The following graphic is an example of a Planning form named Test_300:


    Example of a Planning application form used when importing data from a relational data source.
  4. Create a .properties file.

    Note:

    Effective column heading names are obtained from the column name on the select statement, which can be overridden with the "as" clause.

    The following is an example of a properties file named myprop_relational.properties:

    /A:TEST_300
    /U:admin
    /IR
    /RIQ:DATA_QUERY2
    /D:Entity
    
    DATA_IMPORT_QUERY3 = SELECT Entity ,"DATA LOAD CUBE NAME" as 'Data Load Cube Name',"AUNSPEC" as "aUnspec","ACUR" as "Salary_aCur","ANONCUR" as "aNonCur","APER" as "aPer","ASL" as "aSL","ADATE" as "aDate","ATEXT" as "aText","POINT-OF-VIEW" as "Point-of-View" from Data_Table1
    
    
    /RIC:Test_300A
    /RIR:jdbc:weblogic:sqlserver://[scl34390]:1433;DatabaseName=Test_300A
    /RID:weblogic.jdbc.sqlserver.SQLServerDriver
    /RIU:sa
    /RIP:password
    
  5. Run the Outline Load utility with the .properties file created in the previous step.

    For example, running the following command line will import data from the relational table Data_Table1 located in database Test_300A into the Planning form in Planning application Test_300:

    OutlineLoad /CP:c:/myprop_relational.properties

    The resulting Planning application form:


    Example of a Planning application form after importing data from a relational data source.
  6. Check Essbase log files and validate the results of the import operation.