www.oracle.com Loading Metadata and Data into Planning and Essbase Leveraging 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 49
49
Embed
ODI Loading MetaData and Data Into Planning and Essbase
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
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 NicholsDate: May 22, 2008
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 1 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
Planning Classic Metadata Load using ODI...........................................................................4Step 1 – Define a Logical Schema for Planning..................................................................................................5Step 2 – Define a Physical Schema for Planning................................................................................................6Step 3 – Define a Logical Schema for Files........................................................................................................9Step 4 – Define a Physical Schema for Files.....................................................................................................10Step 5 – Define a Logical Schema for the Sunopsis Memory Engine...............................................................15Step 6 – Define a Physical Schema for the Sunopsis Memory Engine.............................................................16Step 7 – Create a Project....................................................................................................................................20Step 8 – Create the Models................................................................................................................................23
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 2 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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: hyperion planning vm
Host Name: HYPERIONVM
Version: 1.0
ODI: 10.1.3
Planning: 9.3.1
Essbase: 9.3.1
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
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.
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 6 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 17 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
The following window appears
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 18 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
Click on the Context tab
Click the Add Context button
Enter/Select the following
Context: GlobalLogical Schema: ODI_How_To_SME Click OK
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 19 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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: ODI_Class_SKWN
Click OK
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 20 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 21 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
You will now notice there are KMs related to the Hyperion products.
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 22 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 23 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 29 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
Click on the Reverse tab
Enter/Select the following
Type: CustomizedContext: GlobalSelect your KM: RKM Hyperion Planning.ODI_Class_SKWN
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 30 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 31 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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.
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 32 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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: ODI_How_To_Load_STSOH_EntityContext: GlobalEnable “Staging Area Different From Target” and Select the
“ODI_How_To_SME” (Sunopsis Memory Engine)
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 33 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 34 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
Click “Yes” for Automatic Mapping
Connect the remaining columns between the Source and Target
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 35 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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: YesLog_File_Name: c:\odi_how_to.logLog_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
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 36 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
Step 10 – Execute Interface
To execute the Interface, click the Execute button (bottom right)
Click OK
Click OK
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 37 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
Step 11 – Validate Interface Execution
To validate the dimension load and Refresh, click the Operator button from the Designer tool.
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 38 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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.
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 39 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
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
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols
Page 40 of 41
www.oracle.com
Loading Metadata and Data into Planning and Essbase Leveraging ODI
Loading Planning Data
To be completed
Loading Essbase Metadata
To be completed
Loading Essbase Data
To be completed
Oracle Confidential – Internal Use OnlyAuthored By: Steve Nichols