OBIEE Repository Metadata Development

Table of contents Process for bringing data into OBIEE.............................................................................2 Dimensions............................................................................................................2 Physical Layer......................................................................................................2 Connection Pool....................................................................................................3 Create Primary Keys..............................................................................................3 Create the Physical Diagram...................................................................................3 Business Layer ....................................................................................................4 Presentation Layer................................................................................................4 Denormalized tables..............................................................................................4 Repository Documentation Utilities...............................................................................5 Rename Wizard.......................................................................................................5 Generating and Deploying a Metadata Dictionary........................................................5 Generating Documentation of Repository Mappings.....................................................5 Verify Data Type.....................................................................................................5 Change the Date Data Type...................................................................................5 Where are system-wide changes stored?.................................................................6 Create Hierarchies...................................................................................................6 Hierarchy Aggregation...........................................................................................6 Hierarchy Errors...................................................................................................6 Building Hierarchies With Columns In Different Tables.....................................................7 Changes Applied Through Answers...............................................................................8 Formatting Data Values...........................................................................................8 Request Filters......................................................................................................10 Protect Filters Passed through Dashboard...............................................................10

/var/www/apps/conversion/tmp/scratch_2/177529883.doc Page 1

Process for bringing data into OBIEE (from remarks by Mike Jelen. 5/13/2008) General: Perform an operation. then immediately save and check integrity. This saves a lot of troubleshooting time.world /var/www/apps/conversion/tmp/scratch_2/177529883. Dimensions Physical Layer • • Use File.> Import from Server with OCI 10g/11g selected (avoids need to change the Connection Pool later) TNS Name = Data source name on Connection Pool dialog o TNS Name = polydata.doc Page 2 . BICG.

enrolled_date. select Properties Select the Keys tab If primary key is not marked or the wrong one is selected. Create the Physical Diagram • • Click Foreign Join button. then click Dimension table and drag to Fact table For various DATES in the fact table.doc Page 3 . If not. add them. then join to 3 different dates in the fact table (e. Right-click table.Connection Pool • Require fully qualified table names on connection pool (needed for proxy account since it has only read access to tables) Create Primary Keys • • • • Verify that primary keys were imported and identified in the tables. withdrawn_date.. modify the keys accordingly. dropped_date) /var/www/apps/conversion/tmp/scratch_2/177529883. copy the TIME dimension 3 times with different alias names.g.

Business Layer • • • Use Complex Joins to join new items created in the Business Layer.Program Plan End --o o Check "Use existing logical column as the source" Enter the number 1 in the formula box Presentation Layer • Group columns with subfolders o o Create new Presentation Table as "– [Name]" (that's hyphen space name) Creates a subfolder under the parent folder  It is also possible to do this with "->" in the Description. but this is less desirable because it is not visible in Administrator unless you are looking at the column's Properties • For Administrator convenience. (While this would not be allowed in Answers.doc Page 4 . if any Aggregate items that can be summed Use Rename Wizard to rename fields and tables o o • One table at a time (in on-line mode) Rules must be ordered. use a simple join from the original table to the alias The alias becomes the "fact" table Business Layer o Delete columns from the "fact" table that are not used for measures (all but the join column in most cases) • Presentation Layer o o Delete alias table (assuming it does not contain measures) Create different folders (subject areas) for different denormalized tables so that people don't try using them together.) /var/www/apps/conversion/tmp/scratch_2/177529883. --. trying to do so returns an error message that is confusing for the user. use icons to relate items in Presentation and Business Model layers Denormalized tables • Physical layer o o o o • Several subject-related denormalized tables may be pulled in together Create an alias of each denormalized table In the Physical Diagram. e. or perform one rule at a time Group columns with dummy columns.Program Plan Begin ----.g.

Change the Date Data Type Most date columns come into OBIEE with a Data Type of DATETIME which produces a date format that includes the date and the time.Repository Documentation Utilities • • BI Administration Tool > Tools menu > Utilities For more information search Help Rename Wizard • • • Rename columns Remove underscore character Change all column names so that first letter of each word is uppercase and rest is lowercase. • • DOUBLE = 19000225. OBIEE may define the column as a different data type than what was intended or used in the Warehouse. Keys. Produces csv or tab-delimited file. This change will push through from the Physical Layer through the Business Model and Presentation Layers.doc Page 5 . To remove the time from the field change the Data Type to DATE. Generating Documentation of Repository Mappings • • • • • Use this tool to document the tables. Verify Data Type Before moving tables to the Business Model or Presentation Layer verify that the Data Type is correct for the columns. Only columns that are in the Presentation Layer will be included in the report. Run the utility after ALL columns are brought to the Presentation Layer and after running the Rename Wizard. Run the utility before fields (ex. etc in the repository file. If this is incorrect for the column select INTEGER.00 INTEGER = 19000225 /var/www/apps/conversion/tmp/scratch_2/177529883. Generating and Deploying a Metadata Dictionary • Web-based XML file of information in the repository file. Extract Date. • • DATETIME = 1900/02/25 00:00:00 DATE = 1900/02/25 Columns defined as Number will come into OBIEE as DOUBLE which includes two decimal places. columns. Dates are brought in as DATETIME. Maint Date) are deleted from the Presentation Layer.

right-click and select New Logical Level Key. 2. starting from the top and moving down. The Detail level will contain all of the columns of the dimension. Right-click on the Total level and select Properties. 3. The Keys tab should be grayed out. right-click. Highlight and delete Detail Key. Create child levels using names that match your hierarchy.doc Page 6 . but a more detailed child level has associated columns from that same table or a more detailed table. /var/www/apps/conversion/tmp/scratch_2/177529883. Right-click this key column and remove the checkmark next to Use for drilldown. 5. 7. click the Keys tab). Delete any unneeded columns from any level. Hierarchy Errors OBI Tool Metadata Errors and Solutions [nQSError: 15001] Could not load navigation space for subject area Student Enrollment. Move other columns to their respective levels. right-click and remove the checkmark next to Use for drilldown. This message occurs when either a key is in the Total level or when the first child level below the Total level contains two keys. 10. In the field Number of elements at this level: enter 10 and increase in increments of 10 through all levels in the hierarchy. Where are system-wide changes stored? System-wide changes are stored in the Web Catalog and must be moved from development to production servers along with requests and dashboards. 4. Create Hierarchies 1. 6. Hierarchy Aggregation In the hierarchy. Column Format. Data Format and Conditional Format are applied in Answers. Right-click the Detail level. double-click the level. 8.Note: Column Properties which include Style. At level two check for a Detail key that was automatically created. At each level below the Grand Total level. Select all columns as keys if you want to see them in drilldown. For any levels that should be skipped in the drill-down. [nQSError: 15019] Table Student Class Section is functionally dependent upon level Institution Code. If it is selectable. select New Object. These files are stored in folders separate from requests and dashboards. select all columns in the level. Create a child level below the lowest child level (this will contain the dimension key.) Move the dimension key to this level. A Grand Total level and Detail level will be created. Properties. check to see what is there and delete it. Child level. 9. Only one Key should appear. A Hierarchy is created using the name of the dimension table followed by the word Dim. (Right-click level two. Select columns within each level. Delete the key that does not belong. Go to the next level down. select the Keys tab. Right-click dimension table and select Create Dimension at the bottom of the shortcut menu.

3.doc Page 7 . Click the New Foreign Join button.html Building Hierarchies With Columns In Different Tables This first step is needed if columns for hierarchy reside in multiple dimension tables or a dimension table and fact table or because the data model contains only one dimension table and no fact table.com/technology/products/bi/index. No changes are made on the Logical Join window. Create an alias of the table in the physical layer. 11. Expand Sources for B table (click + ) then double-click on the B table source. 15. 7. /var/www/apps/conversion/tmp/scratch_2/177529883. 4. 13. Click Yes. Save repository. 16. Cleanup on tables • • Remove all “Fact” columns from the new dimension table. Select the data model. Hold down the CTRL key and click the next key on the left and the matching key on the right. Join the new dimension in the Physical diagram. Click the first key in the table on the left. Drag the new dimension (Alias) table from the Physical Layer to the Business Model. 8. Check in changes. right-click Physical Diagram > Object(s) and All Joins. 10. Close the Diagram Window. Check in changes. Find the matching key in the table on the right. Click OK. Right-click on table in Physical layer. Remove all dimension columns that don’t belong in the “Fact” table. Use the Complex Join button between the two tables. Create a new or second dimension table from an already existing table 2. Assuming an item in the newly created dimension A that needs to be used for a hierarchy in a different dimension B: Select items from physical layer table corresponding to A and drag to the B dimension in the Business Model.http://www. Continue until all keys are identified in the Expression box at the bottom of the Physical Foreign Key window. 12. If you are joining a new dimension table to itself then create joins between all of the keys in both tables. The new dimension table now has a dimension table icon. 6. 1. Click the OK button. Select the data model. 5. A message “ a matching table key doesn’t exist…” will appear. 9.oracle. then click the Fact table. Click the new dimension table. select New object > Alias. 14. right-click Business Model Diagram > Whole Diagram.

Click the Add button on the General tab. /var/www/apps/conversion/tmp/scratch_2/177529883. Then move Items that you want in the B dimension from the Physical layer to the A dimension Source name. Column Format. Data Format and Conditional Format are applied in Answers. When a certain format is desired for a column everytime the column is used then system-wide changes can be applied. Changes Applied Through Answers Formatting Data Values Column Properties which include Style. This creates a join between those two dimensions. This forces a logical join from the physical join between the dimension table and Fact table. In the box below name click the B table then click the Select button.doc Page 8 . System-wide changes can be saved at the column level or the data type level.

The field is defined with a Data Type of DOUBLE which gives you two decimal places but you need three decimal places in Answers and Dashboards. 2. Select the Data Format tab.A perfect example for a system-wide change is the GPA (Grade Point Average). 1.doc Page 9 . Select the GPA column in Answers. 4. 6. Click the Override Default Data Format checkbox 5. Click the Save button and choose "as the system-wide default for "Student. Select the Column Properties button. 3.GPA" /var/www/apps/conversion/tmp/scratch_2/177529883. Change the number of Decimal Places.

This option is only available if a value has been specified in the filter.doc Page 10 . If the filter item is set to "is prompted" then the Protect Filter option if not available.Request Filters Protect Filters Passed through Dashboard On the filter in the Answers Request. /var/www/apps/conversion/tmp/scratch_2/177529883. This ensures that the filter used in the request is not lost or overwritten by another filter or dashboard prompt that may supersede the request. select Filter Options button > Protect Filter.

Sign up to vote on this title
UsefulNot useful