How can you model this in the RPD?

An organization has re-implemented one of its systems but has not moved history. One database
has data for all years up to 2010 and the other has data for years from 2011 to the present. The
organization needs data from the years 2010 and 2011 on a single report. How can you model this
in the RPD?

An organization has re-implemented one of its systems but has not moved history. One database
has data for all years up to 2010 and the other has data for years from 2011 to the present. The
organization needs data from the years 2010 and 2011 on a single report. How can you model this
in the RPD?

A.
By creating two Logical Fact Tables for each database

B.
By creating joins in the physical model so it looks like a single table

C.
By creating two logical table sources, that specify in Content tab using the Fragmentation
content areas to specify the years for each source

D.
By creating two logical table sources and checking the �This Source should be combined with
other sources at this level� box leaving the Fragmentation content area blank.

E.
By creating one logical table sources and checking the �This Source should be combined with
other sources at this level� box

Explanation:
Note: This source should be combined with other sources at this level (check box)
Description: Check this box when data sources at the same level of aggregation do not contain
overlapping information. In this situation, all sources must be combined to get a complete picture
of information at this level of aggregation.
Note 2: 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.
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).
Reference: 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



Leave a Reply 3

Your email address will not be published. Required fields are marked *


Mike Dill

Mike Dill

I think this should be a combination of C and E.

Leo Yu

Leo Yu

Adding one further step in C) like “check ‘This source should be combined with other sources at this level'” would make C) perfect