Click Next. The Select Metadata Objects screen appears. Select the objects you want to import in the Available list and move them to the Click Finish.

Importing Metadata and Working with Data Sources 4-13 ■ See Importing Metadata from Multidimensional Data Sources for Essbase, XMLA , Oracle OLAP, Hyperion ADM, and SAP BW Native. This section also describes importing from Oracle RPAS data sources over ODBC 3.5. ■ See Importing Metadata from XML Data Sources for XML. ■ See Chapter 5, Working with ADF Business Component Data Sources for OracleADF_HTTP . When you have finished providing information in the Select Data Source screen, click Next. The Select Metadata Types screen appears. 3. Select the options for the types of objects that you want to import for example, Tables , Keys, and Foreign Keys. Some options are automatically selected. Different types of data sources have different default selections, based on what is typical for that data source. If you want to import joins, select both Keys and Foreign Keys. If you want to import system tables, you must have the system privilege for your data source. To import from Customer Relationship Management CRM tables, select Metadata from CRM tables .

4. Click Next. The Select Metadata Objects screen appears.

5. Select the objects you want to import in the Available list and move them to the

Selected list, using the Import selected or Import all buttons. You can also move objects from the Selected list back to the Available list, using the Remove selected and Remove all buttons. To search for a particular item, enter a keyword in the Find box and then click Find Down or Find Up. Select Show complete structure to view all objects, including those that have already been imported. Deselecting this option shows only the objects that are available for import. When this option is selected, objects that have already been imported appear grayed out.

6. Click Finish.

If some objects could not be imported, a list of warning messages appears. In the dialog displaying the messages, you can perform the following actions: – To search for specific terms, click Find and then Find Again. – To copy the contents of the window so that you can paste the messages in another file, click Copy. After you import metadata, you should check to ensure that your database and connection pool settings are correct. In rare cases, the Oracle BI Server cannot determine the exact database type during import and instead assigns an approximate type to the database object. See Setting Up Database Objects and Creating or Changing Connection Pools for more information about working with these objects. It is also a good practice to visually inspect the imported data in the Physical layer, such as physical columns and tables, to ensure that the import completed successfully. About the Map to Logical Model and Publish to Warehouse Screens The Map to Logical Model and Publish to Warehouse screens in the Import Metadata Wizard are reserved for a future release. Check the Oracle Business Intelligence chapter in Oracle Fusion Middleware Release Notes for updates about the functionality in these two screens. 4-14 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition Importing Metadata from Multidimensional Data Sources You can use the Administration Tool to import metadata from a multidimensional data source to the Physical layer of the Oracle BI repository. The ability to use multidimensional data sources enables the Oracle BI Server to connect to sources such as Essbase, Oracle OLAP, Hyperion Financial Management, Microsoft Analysis Services, and SAPBW SAPBusiness Warehouse to extract data. Data from these sources can be displayed on dashboards. The primary differences between setting up multidimensional data sources and relational data sources are in the Physical layer. The setup in the Business Model and Presentation layers for multidimensional data sources and relational data sources is almost identical. During the import process, each cube in a multidimensional data source is created as a single physical cube table. The Oracle BI Server imports the cube metadata, including its metrics, dimensions and hierarchies. After importing the cubes, you need to ensure that the physical cube columns have the correct aggregation rule and that the hierarchy type is correct. See Working with Physical Hierarchy Objects for more information. It is recommended that you remove hierarchies and columns from the Physical layer if they will not be used in the business model. This eliminates maintaining unnecessary objects in the Administration Tool and might result in better performance. To import metadata from a multidimensional data source: 1. In the Administration Tool, select File, then select Import Metadata. The Import Metadata Wizard appears. Figure 4–2 shows the Import Metadata Wizard. Caution: Manually creating a physical schema from a multidimensional data source is labor-intensive and error prone. Therefore, it is strongly recommended that you use the import method. Note: If you have already defined an existing database and connection pool, you can right-click the connection pool in the Physical layer and select Import Metadata. The Import Metadata Wizard appears with the information on the Select Data Source screen pre-filled. You can also use this method to perform incremental imports. Importing Metadata and Working with Data Sources 4-15 Figure 4–2 Import Metadata Wizard: Multidimensional Data Source Note that the Map to Logical Model and Publish to Warehouse screens in the Import Metadata Wizard are reserved for a future release. Check the Oracle Business Intelligence chapter in Oracle Fusion Middleware Release Notes for updates about the functionality in these two screens.

2. In the Select Data Source screen, in the Connection Type field, select the type of