To remove a column mapping, click the Delete button. You might need to scroll to In the Logical Table Source list, select a source and click Unmap. Click OK.
7. To remove a column mapping, click the Delete button. You might need to scroll to
the right to locate the Delete button. 8. After you map the appropriate columns, click OK. Unmapping a Logical Column from Its Source In the Logical Column dialog, the Column Source tab contains information about the logical column. You can edit the logical table sources from which the column derives its data, or unmap it from its sources. To unmap a logical column from its source: 1. In the Business Model and Mapping layer of the Administration Tool, double-click a logical column. 2. In the Logical Column dialog, click the Column Source tab.3. In the Logical Table Source list, select a source and click Unmap.
4. Click OK.
Defining Content of Logical Table Sources To use a source correctly, the Oracle BI 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. See Setting Up Aggregate Navigation by Creating Sources for Aggregated Fact Data for more information. If a logical table is sourced from a set of fragments, it is not required that every individual fragment maps the same set of columns. However, the server returns different answers depending on how columns are mapped. ■ If all the fragments of a logical table map the same set of columns, than the set of fragmented sources is considered to be the whole universe of logical table sources for the logical table. This means that measure aggregations can be calculated based on the set of fragments. ■ If the set of mapped columns differ across the fragments, than the Oracle BI Server assumes that it does not have the whole universe of fragments, and therefore it would be incorrect to calculate aggregate rollups since some fragments are missing. In this case, the server returns NULL as measure aggregates. Managing Logical Table Sources Mappings 10-7 Use the Content tab of the Logical Table Source dialog 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. See Setting Up Fragmentation Content for Aggregate Navigation for additional information. Verifying that Joins Exist from Dimension Tables to Fact Table This source content information tells the Oracle BI 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 verify joins is to select a fact logical table and open 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 10–3 shows an example of how the Fact - Assess fact logical table appears in a Business Model Diagram Selected Tables and Direct Joins view. Figure 10–3 Business Model Diagram of Direct Joins for a Fact Table Table 10–1 contains a list of the logical level for each dimension table that is directly joined the Fact - Assess fact table shown in Figure 10–3 . Note: It is recommended that all the fragments map the same set of columns. Table 10–1 Dimension and Logical Level as Shown in Content Tab Dimension Logical Level Account Geography Postal Code Detail Person Geography Postal Code Detail 10-8 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition To create logical table source content definitions: 1. In the Business Model and Mapping layer of the Administration Tool, double-click a logical table source. 2. In the Logical Table Source dialog, click the Content tab and perform the following steps using Table 10–2 as a guide. 3. If a logical source is an aggregate table and you have defined logical dimensions, select Logical Level from the Aggregation content, group-by list. Then, in the Logical Level list, select the appropriate level for each logical dimension table to which the logical fact 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 are interpreted as being at the most detailed level.4. To specify fragmented table definitions for the source, use the Fragmentation
Parts
» Oracle Fusion Middleware Online Documentation Library
» Click OK when you are finished setting preferences.
» Select Set Icon. Oracle Fusion Middleware Online Documentation Library
» Select the appropriate DSN and click OK.
» Click OK. Oracle Fusion Middleware Online Documentation Library
» Without opening a repository, select File Multiuser History.
» In the ODBC Data Source Administrator dialog, click the System DSN tab, and
» In the Select Data Source screen, in the Connection Type field, select the type of
» Click Finish. Oracle Fusion Middleware Online Documentation Library
» In the Administration Tool, select File, then select Import Metadata.
» Provide the Data source name for the primary database. Click OK.
» In the Select Data Source screen, select OracleADF_HTTP for Connection Type.
» Select the objects you want to import in the Available list and move them to the Click Finish.
» In the Database dialog, click the Features tab. In the Features tab, use the information in
» Specify or adjust the properties as needed, then click OK.
» In the Persist connection pool area, click Clear. Click OK.
» To add tables to the display folder, click Add. Then, in the Browse dialog, select Click OK.
» Click OK in the Hierarchy dialog.
» Select View Members. Click Query to display results. When finished, click Close.
» Click OK. Select Create Columns for Alias Table. Then, from the sub-list, select the alias
» Type the text of the hint in the Hint field and click OK.
» In the shortcut menu, select Update Row Count. Click Yes to check out the objects.
» If you want to provide a dynamic list of currency options, create a table in your
» Click OK. Click OK or Cancel to close the Dimensions dialog.
» From the right-click menu, select Create Logical Dimension, then select either
» In the Check Out Objects dialog, click Yes to check out the objects that appear in
» If the values for the source are unique, select the option Select distinct values.
» Click OK. To move a table, in the Name list, select the table you want to reorder. Then, use
» In the Finish Script screen, the complete path and file name appears. Click Finish.
» Click OK, then click OK again to return to the Identity Manager.
» On the General tab, in the Data source definition: Database field, ensure that the
» Click OK. Open the user.sh file. You can find this file at:
» Click Select next to Patch File. Browse to select the patch file you want to apply, Click Finish.
» Select Tools, then select Query Repository. Click Query.
» When you have finished mapping columns between the selected physical tables, Click Finish.
» In the Choose Directory dialog, click Browse to locate and select the location Click OK.
» To remove the selected objects, click Yes.
» Repository initialization blocks only In the Schedule area, select a start date and
» In the [Repository|Session] Variable Initialization Block dialog, click Edit Data
» Click Edit Data Target. Click OK.
» Check out the branch project using File Multiuser Checkout. You can check
Show more