Siebel Business Analytics Server Administration Guide > Creating and Administering the Business Model and Mapping Layer in a Repository > Creating and Administering Logical Table Sources (Mappings) >

Defining Content of Logical Table Sources

To use a source correctly, the Analytics Server has to know what each source contains in terms of the business model. Therefore, you need to define aggregation content for each logical table source of a fact table. The aggregation content rule defines at what level of granularity the data is stored in this fact table. For each dimension that relates to this fact logical table, define the level of granularity, making sure that every related dimension is defined. For more information, see Example of Creating Sources for Each Level of Aggregated Fact Data.

Use the Content tab of the Logical Table Source dialog box to define any aggregate table content definitions, fragmented table definitions for the source, and Where clauses (if you want to limit the number of rows returned).

NOTE:  For examples of how to set up fragmentation content for aggregate navigation, see Setting Up Fragmentation Content for Aggregate Navigation.

Verify Joins Exist From Dimension Tables to Fact Table

This source content information tells the Analytics Server what it needs to know to send queries to the appropriate physical aggregate fact tables, joined to and constrained by values in the appropriate physical aggregate dimension tables. Be sure that joins exist between the aggregate fact tables and the aggregate dimension tables in the Physical layer.

One recommended way to accomplish this is to select a fact logical table and request a Business Model Diagram (Selected Tables and Direct Joins). Only the dimension logical tables that are directly joined to this fact logical table appear in the diagram. It does not show dimension tables if the same physical table is used in logical fact and dimension sources.

Figure 12 is an example of how the Fact - Asset fact logical table appears in a Business Model Diagram (Selected Tables and Direct Joins) view.

Figure 12. Diagram of Direct Joins for a Fact Table

Table 19 contains a list of the logical level for each dimension table that is directly joined the Fact - Assess fact table shown in Figure 12.

To create logical table source content definitions

1. In the Business Model and Mapping layer, double-click a logical table source.
2. In the Logical Table Source dialog box, click the Content tab and perform the following steps using Table 20 as a guide.
3. If a logical source is an aggregate table and you have defined logical dimensions, perform the following steps:
   1. Select Logical Level from the Aggregation content, group-by drop-down list.

      CAUTION:  Although you have the option to specify aggregate content by logical level or column, it is recommended that you use logical levels exclusively.

   2. In the Logical Level drop-down list, select the appropriate level for each dimension logical table to which the fact logical table is joined.

      You should specify a logical level for each dimension, unless you are specifying the Grand Total level. Dimensions with no level specified will be interpreted as being at the Grand Total level.

4. If a logical source is an aggregate table and you want to define content for columns, do the following:
   1. Select Column from the Aggregation content, group-by drop-down list.

      CAUTION:  Although you have the option to specify aggregate content by logical level or column, it is recommended that you use logical levels exclusively.

   2. In the Table pane, select each logical dimension table that defines the aggregation level of the source.
   3. In the Column pane, select the logical column for each dimension that defines how the aggregations were grouped.

      When there are multiple logical columns that could be used, select the one that maps to the key of the source physical table. For example, if data has been aggregated to the Region logical level, pick the logical column that maps to the key of the Region table.

      NOTE:  Do not mix aggregation by logical level and column in the same business model. It is recommended that you use aggregation by logical level.

5. To specify fragmented table definitions for the source, use the Fragmentation content window to describe the range of values included in the source when a source represents a portion of the data at a given level of aggregation.

   You can type the formula directly into the window, or click the Expression Builder button to the right of the window. In the Fragmentation Content Expression Builder, you can specify content in terms of existing logical columns. For examples of how to set up fragmentation content for aggregate navigation, seeSpecify Fragmentation Content.

6. Select the following option:

   This source should be combined with other sources at this level

   NOTE:  This option is only for multiple sources that are at the same level of aggregation.

7. (Optional) Specify Where clause filters in the Where Clause Filter window to limit the number of rows the source uses in the resultant table. For more information, see About WHERE Clause Filters.
   1. Click the Expression Builder button to open the Physical Where Filter Expression Builder.
   2. Type the Where clause and click OK.
8. Select the option Select distinct values if the values for the source are unique.

About WHERE Clause Filters

The WHERE clause filter is used to constrain the physical tables referenced in the logical table source. If there are no constraints on the aggregate source, leave the WHERE clause filter blank.

Each logical table source should contain data at a single intersection of aggregation levels. You would not want to create a source, for example, that had sales data at both the Brand and Manufacturer levels. If the physical tables include data at more than one level, add an appropriate WHERE clause constraint to filter values to a single level.

Any constraints in the WHERE clause filter are made on the physical tables in the source.