ODI Loading MetaData and Data Into Planning and Essbase

www.oracle.
com Loading Metadata and Data into Planning and Essbase Leveraging ODI
Loading Metadata and Data into Planning and Essbase Leveraging ODI
Prepared by: Steven Nichols Date: May 22, 2008
Oracle Confidential Internal Use Only Authored By: Steve Nichols Page 1 of 41
www.oracle.com Loading Metadata and Data into Planning and Essbase Leveraging ODI
Table of Contents
PURPOSE..........................................................................................................................................3 INTENDED AUDIENCE...........................................................................................................................3 VERSION...........................................................................................................................................3 LOADING PLANNING METADATA..............................................................................................................4 Planning Classic Metadata Load using ODI............................................................................4
Step 1 Define a Logical Schema for Planning ..................................................................................................... 5 Step 2 Define a Physical Schema for Planning ................................................................................................... 6 Step 3 Define a Logical Schema for Files ........................................................................................................... 9 Step 4 Define a Physical Schema for Files......................................................................................................... 10 Step 5 Define a Logical Schema for the Sunopsis Memory Engine .................................................................15 Step 6 Define a Physical Schema for the Sunopsis Memory Engine.................................................................16 Step 7 Create a Project........................................................................................................................................ 20 Step 8 Create the Models.................................................................................................................................... 23 Flat File Model................................................................................................................................................. 23 Hyperion Planning Model................................................................................................................................ 29 Step 9 Create Interface........................................................................................................................................ 33 Step 10 Execute Interface................................................................................................................................... 37 Step 11 Validate Interface Execution................................................................................................................. 38
LOADING PLANNING DATA...................................................................................................................41 LOADING ESSBASE METADATA.............................................................................................................41 LOADING ESSBASE DATA....................................................................................................................41
Purpose
This document will cover the different methods in which to load metadata into a Hyperion Planning application managed through the Classic Administration interface. This document will also cover how to load metadata and data into Essbase. Oracle Data Integrator (ODI) is the primary product utilized throughout the examples. The topics to be covered in this document include the following: Loading metadata into a Planning Classic application using the ODI Knowledge Module (KM) for Hyperion Planning Loading Data into a Planning Classic application using the ODI Knowledge Module (KM) for Hyperion Planning Loading metadata into an Essbase application using the ODI KM for Essbase Loading data into an Essbase application using the ODI KM for Essbase
Intended Audience
The intended audience for this document includes the following: Planning application administrators Essbase application administrators
Version
VMImage: Version: ODI: Planning: Essbase: hyperion planning vm 1.0 10.1.3 9.3.1 9.3.1 Host Name: HYPERIONVM
Loading Planning Metadata

Planning Classic Metadata Load using ODI Log into the ODI Designer and access the Topology Manager
Step 1 Define a Logical Schema for Planning
Click in the Logical Architecture tab (bottom left pane) and then right-click on Hyperion Planning and select Insert Logical Schema
Enter/Select the following Name: Context: Click OK ODI_How_To_Plan Global
Step 2 Define a Physical Schema for Planning
Click in the Physical Architecture tab (bottom left pane) and then right-click and select Insert Data Server
Enter/Select the following Name: ODI_Planning_Target Server (Data Server):localhost:11333 User: admin Password: password Note: The server name represents the same server name you would enter when Leveraging Hyperion Application Link (HAL). The port represents the RMI port number. The ID and Password represents a Planning application administrator type role.
Click OK and the following window will appear.
Enter/Select the following on the Definition tab Application (Catalog): Application (Work Catalog): SKWNApp SKWNApp
Note: These names represent the name of the application you plan to load metadata into.
Click the Context tab
Click the Add Context button Enter/Select the following Context: Global Logical Schema: ODI_How_To_Plan Click OK
Step 3 Define a Logical Schema for Files
Select the Logical Schema tab (bottom left pane) and right-click on File and select Insert Logical Schema
Enter/Select the following Name: Context: Click OK ODI_How_To Global
Step 4 Define a Physical Schema for Files
Click in the Physical Architecture tab (bottom left pane) and then right-click on File and Select Insert Data Server
On the Definition Tab enter Enter/Select the following Name: ODI_How_To Host (Data Server): localhost
Click the JDBC Tab
Click on the next to JDBC Driver
The following window appears.
Enter/Select the following Name: Click OK For the JDBC URL enter jdbc:snps:dbfile Sunopsis File JDBC Driver
Open the Physical Schema Directory for the File
Enter/Select the following Directory (Schema): Directory (Work Schema): valid folder name valid folder name
Note: These represent the folder where the text file reside that you plan to use.
Click on the Context Tab
Click the Add Context button Enter/Select the following Context: Physical Schema: Click OK Global ODI_How_To
Step 5 Define a Logical Schema for the Sunopsis Memory Engine
From the Logical Architecture panel, right-click on the Sunopis Engine and select Insert Logical Schema
Enter/Select the following Name: Context: Click OK ODI_How_To_SME Global
Step 6 Define a Physical Schema for the Sunopsis Memory Engine
From the Physical Architecture panel, right-click on the Sunopis Engine and select Insert Data Server
Enter/Select the following on the Definition tab Name: ODI_How_To_SME
Click on the JDBC tab
Enter/Select the following JDBC: JDBC Url: Click OK oracle.jdbc.driver.OracleDriver jdbc:oracle:thin:@localhost:1521:sandbox
The following window appears
Click on the Context tab
Click the Add Context button Enter/Select the following Context: Global Logical Schema: ODI_How_To_SME Click OK
Step 7 Create a Project Once you have created the Logical and Physical Schemas, it is time to create a project and import the Knowledge Modules (KM). To create a Project, you need to access the ODI Designer. Once in the Designer tool, click on the Projects tab and then click on the Insert Project button.
Enter the following Name: Click OK ODI_Class_SKWN
To insert the Hyperion Planning KMs, expand the Knowledge Modules folders and right-click on any of folders under Knowledge Modules and select Import Knowledge Modules,
Browse to the appropriate File import directory Select the desired KMs to import Click OK
You will now notice there are KMs related to the Hyperion products.
Step 8 Create the Models
Flat File Model
From the Topology Manager, click the Designer button, this will open the ODI Designer module. To create a folder, click the Insert Model Folder button.
Enter/Select the following Name: ODI_How_To_Model
Click the OK button
After creating the Model folder, you can create a model folder for flat files you plan to use and a model folder for the Hyperion Planning application you plan to update. To create flat file Model folder, right-click on the ODI_How_To_Model folder and select Insert Model
Enter/Select the following Name: ODI_How_To_Files Technology: File Logical Schema: ODI_How_To
Click the Reverse tab
Select/Enter the following Context: Click OK Global
After creating the File Model folder, right-click on the ODI_How_To_Files model and select Insert DataStore
Enter/select the following on the Definition tab Name: STS_OH_Entity Resource Name: Click the browse button and select the dimension metadata file
Click the Files tab
Select/Enter the following File Format: Delimited Heading: 1 Field Separator: Other, enter comma (,) Text Delimiter: Double quote ()
Click the Columns tab
Click the Reverse button You should now see the columns that are in the file Click the OK button
Hyperion Planning Model
Right-Click on the ODI_How_To_Model folder and select Insert Model
Enter/Select the following Name: Technology: ODI_How_To_Plan Hyperion Planning
Click on the Reverse tab
Enter/Select the following Type: Context: Select your KM: Customized Global RKM Hyperion Planning.ODI_Class_SKWN
Click the Reverse button The Execution window appears
Accept the defaults and click OK. An informational window appears indicating a Session was started.
Click OK
You can click the Refresh button to determine if the session has completed. Once it does, you will notice there are dimensions and columns within the dimensions.
Step 9 Create Interface
Once the Models have been created, it is time to create an Interface. Access the Project you created in Step 7. Expand the ODI_Class_SKWN Project to the Interface folder and right-click on the Interface folder and select Insert Interface
Enter/Select the following Name: Context: Enable ODI_How_To_Load_STSOH_Entity Global Staging Area Different From Target and Select the ODI_How_To_SME (Sunopsis Memory Engine)
Click the Diagram tab
Click on the Models tab and expand the ODI_How_To_Model Drag the STS_OH_Entity file into the Source area of the Diagram Drag the Entity dimension into the Target area of the Diagram
Click Yes for Automatic Mapping Connect the remaining columns between the Source and Target
Click on the Flow tab
Click on the first box in the flow, this will remove the Yellow X from the upper left-hand corner. Click on the Target box and enter/select the following Log_Enabled: Yes Log_File_Name: c:\odi_how_to.log Log_Errors: Yes Error_Log_Filename: c:\odi_how_to_errs.log (this will contain the kick-outs from the metadata load) Refresh_Database: Yes (this will execute a Refresh between Planning and Essbase) Click the Apply button
Step 10 Execute Interface
To execute the Interface, click the Execute button (bottom right)
Click OK
Click OK
Step 11 Validate Interface Execution
To validate the dimension load and Refresh, click the Operator button from the Designer tool.
Once in the Operator Tool, Expand the Sessions folder until you see your session.
Double-Click on the Statistics folder and click on the Execution tab and examine the contents of the Message window If rows are rejected, you should access the *.log files defined in the Flow tab for details. The following entries from the ODI_How_To.log indicate the Planning Refresh ran successfully. 2008-05-22 18:58:45,312 INFO [DwgCmdExecutionThread]: Planing cube refresh operation initiated. 2008-05-22 18:59:04,359 INFO [DwgCmdExecutionThread]: Planning cube refresh operation completed successfully.
Below are sample entries from the error log defined in the Flow diagram of the Target ODI_How_To_Errs.log Entity,Parent,Alias: Default,Data Storage,Two Pass Calculation,Description,Plan Type (Plan1),Aggregation (Plan1),Plan Type (Plan2),Aggregation (Plan2),Error_Reason US - No Dept,US,UK Senior - (US),Store,0,,1,+,0,+,Cannot load dimension member, error message is: java.lang.RuntimeException: Unable to locate specified parent member: US dim id: 33 U160,US,U160 - LM UK STS Senior Lab,Store,0,,1,+,0,+,Cannot load dimension member, error message is: java.lang.RuntimeException: Unable to locate specified parent member: US dim id: 33 U200,US,U200 - LM UK STS Senior Lab,Store,0,,1,+,0,+,Cannot load dimension member, error message is: java.lang.RuntimeException: Unable to locate specified parent member: US dim id: 33
Loading Planning Data

To be completed
Loading Essbase Metadata

To be completed
Loading Essbase Data

To be completed

ODI Loading MetaData and Data Into Planning and Essbase

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ODI Loading MetaData and Data Into Planning and Essbase

Hochgeladen von

Copyright:

Verfügbare Formate

www.oracle.

Prepared by: Steven Nichols Date: May 22, 2008

Loading Planning Metadata

Step 1 Define a Logical Schema for Planning

Enter/Select the following Name: Context: Click OK ODI_How_To_Plan Global

Step 2 Define a Physical Schema for Planning

Click OK and the following window will appear.

Click the Context tab

Step 3 Define a Logical Schema for Files

Enter/Select the following Name: Context: Click OK ODI_How_To Global

Step 4 Define a Physical Schema for Files

Click the JDBC Tab

Click on the next to JDBC Driver

The following window appears.

Open the Physical Schema Directory for the File

Click on the Context Tab

Step 5 Define a Logical Schema for the Sunopsis Memory Engine

Enter/Select the following Name: Context: Click OK ODI_How_To_SME Global

Step 6 Define a Physical Schema for the Sunopsis Memory Engine

Enter/Select the following on the Definition tab Name: ODI_How_To_SME

Click on the JDBC tab

Enter/Select the following JDBC: JDBC Url: Click OK oracle.jdbc.driver.OracleDriver jdbc:oracle:thin:@localhost:1521:sandbox

The following window appears

Click on the Context tab

Enter the following Name: Click OK ODI_Class_SKWN

Step 8 Create the Models

Flat File Model

Enter/Select the following Name: ODI_How_To_Model

Click the OK button

Click the Reverse tab

Select/Enter the following Context: Click OK Global

Click the Files tab

Click the Columns tab

Hyperion Planning Model

Right-Click on the ODI_How_To_Model folder and select Insert Model

Enter/Select the following Name: Technology: ODI_How_To_Plan Hyperion Planning

Click on the Reverse tab

Click the Reverse button The Execution window appears

Step 9 Create Interface

Click the Diagram tab

Click on the Flow tab

Step 10 Execute Interface

To execute the Interface, click the Execute button (bottom right)

Step 11 Validate Interface Execution

Loading Planning Data

Loading Essbase Metadata

Loading Essbase Data

Das könnte Ihnen auch gefallen