Click the New Join button on the Administration Tool toolbar: In the Physical Diagram, left-click the first table in the join the table representing Move the cursor to the table to which you want to join the table representing one Select the joining colum

7-36 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition Figure 7–7 Joins for Fragmented Tables Example Defining Physical Joins with the Physical Diagram You can define foreign keys and complex joins between tables, whether or not the tables are in the same data source. When you use the Physical Diagram to create joins, the Administration Tool determines what type of join to create based on the selected object types and the join expression. If you do not want the Administration Tool to automatically determine what type of join to create, use the Joins manager to explicitly create the join. See Defining Physical Joins with the Joins Manager for more information. To define a physical foreign key join or a complex join with the Physical Diagram: 1. In the Physical layer of the Administration Tool, select one or more tables and choose one of the Physical Diagram commands from the right-click menu.

2. Click the New Join button on the Administration Tool toolbar:

3. In the Physical Diagram, left-click the first table in the join the table representing

many in the one-to-many join to select it.

4. Move the cursor to the table to which you want to join the table representing one

in the one-to-many join, and then left-click the second table to select it. The Physical Foreign Key dialog appears. Although physical foreign key joins are the default join type, the object type might change to a complex join after you define the join and click OK, depending on the join information.

5. Select the joining columns from the left and the right tables.

The SQL join conditions appear in the expression pane. The driving table option is shown in this dialog, but it is not available for selection because the Oracle BI Server implements driving tables only in the Business Model and Mapping layer. See Specifying a Driving Table for more information about driving tables.

6. For complex joins, you can optionally set the cardinality for each side of the join

for example, N, 0,1, 1, or Unknown. Note: Avoid adding join conditions where they are not necessary for example, between Sales A to M and Customer N to Z in Figure 7–6 . Extra join conditions can cause performance degradations. Working with Physical Tables, Cubes, and Joins 7-37 To set the cardinality to unknown, you only need to select Unknown for one side of the join. For example, choosing unknown-to-1 is equivalent to unknown-to-unknown and appears as such the next time you open the dialog for this join. 7. If appropriate, specify a database hint. See Using Hints for more information. 8. If you are creating a complex join for ADF Business Component ViewObject or ViewLink instances, specify the ViewLink instance name or the ViewLink definition name in the ViewLink Name field. 9. To open Expression Builder, click the button to the right of the Expression pane. The expression displays in the Expression pane. The default join expression for ViewObject or ViewLink instances is arbitrary and has no meaning.

10. Click OK to apply the selections.