UDA Data Load Columns

Oracle Hyperion Planning 22-35 Column Description Data Load Cube Name Takes the name of the plan type to which data is being loaded. The value is passed as a string. Valid values are any plan types specified in the Planning application. For example: ■ Plan1 ■ Plan2 ■ Plan3 ■ Wkforce ■ Capex Driver Member Takes the name of the driver member that is selected when the Planning, Oracles Hyperion® Workforce Planning, or Oracles Hyperion® Capital Expense Planning application is set up for loading data. You can have one driver dimension per load. The Driver Dimension and Driver Dimension Members are defined in the Data Load Administration page in Planning. The driver members are the members into which the data is loaded. The number of driver member columns depends on the number of driver members you select in Oracles Hyperion® Planning - System 9. The value is passed as a string representing a numeric value or, if a Smart List is bound to the member represented on this column, a Smart List value. Note: The Smart List field on this load method does not affect this column. Point-of-View Takes the names of all the other dimensions that are required to determine the intersection to load the data. The value is passed as a string. The data load automatically performs cross-product record creations based on dimension parameters defined in the POV. For example, an employee’s Smart List attribute values that are constant over time such as full time status for all twelve months need only be supplied once in the data feed and the load file will create and load that data record for each relevant cell intersection. 22-36 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator 23 Oracle OLAP 23-1 23 Oracle OLAP This chapter describes how to work with Oracle OLAP in Oracle Data Integrator. This chapter includes the following sections: ■ Section 23.1, Introduction ■ Section 23.2, Installation and Configuration ■ Section 23.3, Setting up the Topology ■ Section 23.4, Setting Up an Integration Project ■ Section 23.5, Creating and Reverse-Engineering an Oracle Model ■ Section 23.6, Working with Oracle OLAP KMs in Integration Interfaces

23.1 Introduction

Oracle Data Integrator ODI seamlessly integrates data in an Oracle OLAP. All Oracle Data Integrator features are designed to work best with the Oracle OLAP cubes, including reverse-engineering and integration interfaces. Oracle Data Integrator uses Java Database Connectivity JDBC to connect to the Oracle database instance containing the Oracle OLAP cubes.

23.1.1 Concepts

The Oracle Data Integrator Knowledge Modules for Oracle OLAP provide integration and connectivity between Oracle Data Integrator and Oracle OLAP cubes. Oracle Data Integrator is able to handle two different types of cubes with the Oracle OLAP KMs, depending on the storage mode of these cubes: ■ ROLAP Relational OnLine Analytical Processing cubes are based on a relational storage model. ROLAP cubes can handle a large amount of data and benefit all features of the relational database. ■ MOLAP Multidimensional OnLine Analytical Processing data is stored in form of multidimensional cubes. The MOLAP model provides high query performance and fast data retrieval for a limited amount of data. Note: Only Analytic Workspaces containing OLAP 10g Cubes are supported. Relational OLAP ROLAP support is limited to CWM 1 only. 23-2 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator The Oracle Data Integrator KMs for Oracle OLAP use mature integration methods for Oracle OLAP in order to: ■ Reverse-Engineer Oracle OLAP data structures all tables used by a ROLAP or a MOLAP cube. ■ Integrate data in an Oracle Analytical Workspace target in incremental update mode.

23.1.2 Knowledge Modules

Oracle Data Integrator provides the Knowledge Modules KM listed in Table 23–1 for handling Oracle OLAP data. The KMs use Oracle OLAP specific features. It is also possible to use the generic SQL KMs and Oracle Database KMs with the Oracle OLAP. See Chapter 4, Generic SQL and Chapter 2, Oracle Database for more information.

23.2 Installation and Configuration

Make sure you have read the information in this section before you start using the Oracle OLAP Knowledge Modules: ■ System Requirements and Certifications ■ Technology Specific Requirements ■ Connectivity Requirements

23.2.1 System Requirements and Certifications

Before performing any installation you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the products you are installing. The list of supported platforms and versions is available on Oracle Technical Network OTN: http:www.oracle.comtechnologyproductsoracle-data-integrator index.html . Note: The Oracle Data Integrator Oracle OLAP KMs are similar to the standard Oracle Database KMs. This chapter describes the Oracle OLAP specificities. See Chapter 2, Oracle Database for a description of the Oracle Database KMs. Table 23–1 Oracle OLAP Knowledge Modules Knowledge Module Description RKM Oracle OLAP Jython Reverse-engineering knowledge module to retrieve the tables, views, columns, Primary Keys, Unique Keys and Foreign keys from Oracle Database, which are used by a ROLAP or a MOLAP Cube. This KM provides logging Use Log Log File Name options. IKM Oracle AW Incremental Update This KM is similar to the IKM Oracle Incremental Update. It has additional options for handling MOLAP cubes. Oracle OLAP 23-3

23.2.2 Technology Specific Requirements

There are no connectivity requirements for using Oracle OLAP data in Oracle Data Integrator. The requirements for the Oracle Database apply also to Oracle OLAP. See Chapter 2, Oracle Database for more information. The RKM Oracle OLAP Jython uses in addition Oracle OLAP libraries. Copy the awxml.jar and olap_api.jar from the ORACLE_HOMEolapapilib folder into the additional drivers folder for ODI.

23.2.3 Connectivity Requirements

There are no connectivity requirements for using Oracle OLAP data in Oracle Data Integrator. The requirements for the Oracle Database apply also to Oracle OLAP. See Chapter 2, Oracle Database for more information.

23.3 Setting up the Topology

Setting up the Topology consists of: 1. Creating an Oracle Data Server 2. Creating an Oracle Physical Schema

23.3.1 Creating an Oracle Data Server

This step consists in declaring in Oracle Data Integrator the data server, as well as the physical and logical schemas that store the Oracle OLAP cubes.

23.3.1.1 Creation of the Data Server

Create a data server for the Oracle technology as described in Section 2.3.1, Creating an Oracle Data Server .

23.3.2 Creating an Oracle Physical Schema

Create an Oracle physical schema using the standard procedure, as described in Creating a Physical Schema of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. Create for this physical schema a logical schema using the standard procedure, as described in Creating a Logical Schema of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator and associate it in a given context.

23.4 Setting Up an Integration Project

Setting up a project using the Oracle OLAP features follows the standard procedure. See Creating an Integration Project of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. It is recommended to import the following knowledge modules into your project for getting started with Oracle OLAP: ■ IKM Oracle AW Incremental Update ■ RKM Oracle OLAP Jython Import also the Oracle Database knowledge modules recommended in Chapter 2, Oracle Database .