Report based on 2 different Fact tables

Hi all
Is it possible to make a report based on 2 Fact tables wich are not linked to exactly the same dimensions?
FactTable1 : linked to Time,Product,Geography
FactTable2: linked to only Time
The FactTable2 will contain only one measure which is a constant value per year and It will be used to be compared to the FactTable2's measure (It's a kind of reference).
So do FactTable2 need to be linked to Geography and product to be able to create this report??
Regards.

I tried to set the level for the metrics...now it doesn't make the CAST anymore, but i get a result set bigger than i need...
BI Server seems to make the union of 2 instead of the intersection...
For example, if i have 5 customers, but only 2 customers have a service request (order) associated, then the server returns the following report
Customer Code | Service Request Code | # asset(Fact 1) | # order (Fact2)
0000001_________NULL_______________ 5____________ 0
0000002_________NULL_______________ 4____________ 0
0000003_____ 700000930______________ 3___________ 1
0000004_____ 700000930______________ 3___________ 1
0000005_________NULL_______________ 3____________ 0
while my goal is to get just the list of customers having at least a service request (order)...
I tried to create a filter on the column "Serve Request Code", but it doen't have effect, cuz the server lunchs 2 different sql queries to create the report:
select D1.c3 as c1,
D1.c2 as c2,
D1.c1 as c3,
D1.c4 as c4
from
(select D1.c1 as c1,
D1.c2 as c2,
D1.c3 as c3,
D1.c4 as c4
from
(select count(distinct T111689.ROW_ID) as c1,
T112015.SR_NUM as c2,
T111844.OU_NUM as c3,
T111844.ROW_ID as c4,
ROW_NUMBER() OVER (PARTITION BY T111844.ROW_ID, T112015.SR_NUM ORDER BY T111844.ROW_ID ASC, T112015.SR_NUM ASC) as c5
from
CW_CASE T112015 /* Dim_CW_CASE_Case_Order */ ,
CW_CUSTOMER T111844 /* Dim_CW_CUSTOMER_Customer_Order */ ,
CW_ORDER T111689 /* Fact_CW_ORDER_Order */
where ( T111689.ACCNT_ID = T111844.ROW_ID and T111689.SR_ID = T112015.ROW_ID and T111844.ROW_ID = T112015.CST_OU_ID )
group by T111844.ROW_ID, T111844.OU_NUM, T112015.SR_NUM
) D1
where ( D1.c5 = 1 )
) D1
+++Administrator:330000:330001:----2009/02/04 14:42:22
-------------------- Sending query to database named WBIP (id: <<901676>>):
select D2.c2 as c1,
D2.c1 as c2,
D2.c3 as c3
from
(select D1.c1 as c1,
D1.c2 as c2,
D1.c3 as c3
from
(select count(distinct T149849.ROW_ID) as c1,
T111844.OU_NUM as c2,
T111844.ROW_ID as c3,
ROW_NUMBER() OVER (PARTITION BY T111844.ROW_ID ORDER BY T111844.ROW_ID ASC) as c4
from
CW_CUSTOMER T111844 /* Dim_CW_CUSTOMER_Customer_Order */ ,
CW_ASSET T149849 /* Fact_CW_ASSET_Asset */
where ( T111844.ROW_ID = T149849.OWNER_ACCNT_ID )
group by T111844.ROW_ID, T111844.OU_NUM
) D1
where ( D1.c4 = 1 )
) D2
thanks in advance,
Nazza

Similar Messages

  • OBIEE-can we link two dimension tables belonging to different fact tables?

    Hi ,
    I have just started with OBIEE concepts....need your views on this issue:
    Fact 1 -> Dim 1, Dim2,Dim3 and so on..
    Fact 2 -> Dim a, Dim b,Dimc and so on...
    If I link Dim1 and Dim a with a valid key ,would that distort the star schemas to slowflake in BMM layer?
    Thanks in advance!
    Neha

    I don't see this that would make it snowflake more like what I think as conforming dimensions. You need to make sure the grain of the measures is at what level , the they are same grain then you should be good however if they are different then you would start seeing null values.
    Fact Measures use the same, conformed dimensions like Dim1 and Dim a if you trying to generate from multiple facts, the BI server was able to automatically stitch them together into a single result set. If they came from the same fact table that's easy as its only one single table, but if you are pulling from different fact tables, the conformed dimensions would allow them to be stitched into the same report
    Conformance means that these sources can be mapped to a common structure – the same levels – and also the same data members.
    Mark if helps.
    Thanks,
    SVS

  • How to handle 3 different fact tables and measures within a DAX query?

    I am writing a DAX query in DAX studio in Excel against a tabular model that has 4 different Fact tables, but they share the same dimensions. (There's some long story I can't get into here, but unfortunately this is the structure) I want to
    include measures from the 4 fact tables, summarize by the dimensions in a single query output that can be used for a pivot table.  So far I have something like this:
     EVALUATE
    FILTER
        SUMMARIZE
            FactTable1,
            DimensionTable1[Value],        DimensionTable2[Value],
            DimensionTable3[Value],
            Dimensiontable4[Value],
            'dimDateTime'[Month PST],
            DimDateTIme[FiscalYear PST],
            "Measure Score",
            FactTable1[Measure 1],
            "Measure Score 2",
            FactTable1[Measure 2],
        ,Company[CompanyName]="Company ABC" 
    What I want to do is summarize the 3 fact tables by the same dimensions, but I am not sure how to do that within a DAX query.  I am getting an error if I try to include another table statement in the original SUMMARIZE function, even though the FACTS
    do share the same dimension.  Is there an easy way to do this?

    You can use ADDCOLUMNS to add the data from other tables, but you need to use within the SUMMARIZE the fact table that determines the cardinality of the output. If you are not sure (e.g. you project cost and revenues from two fact tables by month and there
    could me months with cost and no revenues, but also months with revenues and no costs), then you should use CROSSJOIN and then FILTER.
    You query might be written as (please note CALCULATETABLE instead of FILTER to improve performance):
    EVALUATE
    CALCULATETABLE (
        ADDCOLUMNS (
            SUMMARIZE (
                FactTable1,
                DimensionTable1[Value],
                DimensionTable2[Value],
                DimensionTable3[Value],
                Dimensiontable4[Value],
                'dimDateTime'[Month PST],
                DimDateTIme[FiscalYear PST]
            "Measure Score", FactTable1[Measure 1],
            "Measure Score 2", FactTable1[Measure 2]
        Company[CompanyName] = "Company ABC"
    Marco Russo http://www.sqlbi.com http://www.powerpivotworkshop.com http://sqlblog.com/blogs/marco_russo

  • Single Crystal Report based on Five different SAP BEx Quries.

    Hi,
    I need to create 5 different Charts (in a single report)  based on five different SAP BW BEx Queries. These are charts with 3- axes i.e. X,Y,Z.
    The example requirement is to create Line charts (Vertical Mixed Line Charts) and deatils are as follows: The chart should show CPU Utilization % for different servers (eg. Servers1,2,3,4,5) for each day in a particular month.
    Axes details:
    X- Axis - Date eg: 01 /09/2010 to 30/09/2010
    Y-Axis - CPU Utilisation Percent
    Z-Axis - Servers from 1 to 5
    The above detailed chart comes from a BEx Query . In this way there are four more BEx queries which should give four other charts.
    My queries are:
    1. Is this possible to create a single report using five different BEx queries and Create 5 different charts(one chart from each BEx Query) in a single tab as in the current manual report.(All the five Line charts should be downloadable to a single sheet in Excel)
    2. One more, should I use Crystal Reports only? The charts are of high format natute so Web Intelligence will not produce the same.  Is any other tool that helps for this requirement.
    3. I can create five different Universes based on BEx Queries. Is this possible to create a single report from five different Universes.
    Please advise.
    Nanda Kishore.
    Edited by: Nanda Kishore B on Oct 21, 2010 8:05 AM

    To start with you cannot use SAP BW universes in Crystal Reports., YOu have to use the BW MDX driver.
    For performance reasons I would suggest to add 4 subreports into your main reports containing each on of the 4 remaining charts.
    Regards,
    Stratos

  • Same dimension in two different fact tables

    Hi,
    I have one same dimension in two different fact tables. I would like to know how BI server choose the fact table when I do a request in this dimension.
    I know that is always using the same fact table, but I would like to know why choose this table and not the other.
    Thanks

    Sorry,
    But it doesn't seem to me.
    I reorded the tables in the BMM layer and it continues to use the same table, regardless this table is in last.
    After, I droped that table in the BMM layer and it continued to use the same.
    Thanks for your reply

  • Cubes with different dimensions based on the same fact table

    I have a fact table (f_a) with three dimensions (dim_a, dim_b, dim_c) and a one measure (m_a).
    Is it possible to create cube with only one dimension (dim_a)?
    Data for other two dimensions (dim_b, dim_c) should be aggreagated together.
    Of course i can create second fact table with only one dimension, and then creating that cube would be no problem.
    But is it possible doing this directly from the primary fact table (without creating second fact table)?
    Raf
    PS:i use AWM 9.2 to create target cubes. Source cubes i create with OEM 9.2

    At the beginning i was confused by the numberous kind of cubes...
    for example when i created cube in MS i just designed cube, picked fact table, and that's all. In Oracle firstly i create project of cube (first cube) in OWB. Then i export it to the OLAP Catalog (second cube). That cube in OLAP catalog is a source cube for the AW cube (third cube). Then i need to enable AW cube for OLAPI by creating another cube in OLAP Catalog (i use 9iR2, so OLAPI doesn't have direct access to AW cubes).
    I spent much time until i could see my first sample cube in Discoverer or Excel as a final user should see it. :-)
    Now i'm facing another problem - when you redesign cube (for example add another dimension), you can't just "refresh" it as it was in MS. You have to delete old cube and create new one. And deleting cube isn't so simple (i'm not sure which elements i should delete).
    For testing and learning purposes i just create every cube in seperate AW. deleting whole AW is much simplier that deleting one cube.
    Raf

  • Issue with Crystal Report based on 2 different data sources

    Hi there,
    I am having a frustrating problem with a report I've designed and I'm hoping someone might be able to assist please.
    The report has 3 different prompts, each of which is based on a dynamic list of values retrieved via views within a SQL server db.
    We are wanting to introduce the use of Universes as much as possible, so the data returned is based off a BO Universe data source query.
    I have uploaded the report into BO and have provided the necessary database logon information for the report (in the "Process" > "Database" settings in the CMC) for both the direct db datasource connection (for the views) and the BO Universe query connection.
    When the report is run however, the report still prompts for the database user name & password credentials. I have triple checked my db connection settings, and also have "Use same database logon as when report is run" set to true. I also tested a cut-down version of the report without the Universe connection with the same db logon credentials I provided and there was no credentials prompt when it was run, proving those values are accepted.
    Does anyone know why this is happening & if there is a way around it? Alternatively, is there some way that a report prompt may be based on a dynamic list of values retrieved via a Universe connection? This way I'd be able to remove the db connection for the views and have the report solely based on the Universe.
    Another issue that occurs is out of the 3 prompts, a user can select a User Name OR Number, and also must select a Period. However if the User Name or Number is left blank the message "The value is not valid" is shown. So I tried a cut-down version of the report with only the BO Universe as a data source (static prompts) and this didn't occur, i.e. I was allowed to leave either the User Name or Number empty.
    I hope this all of makes sense - let me know if not. If anyone is able to help out with any of this it would be very much appreciated.
    Cheers,
    Marco

    Please re-post if this is still an issue to the Business Objects Forum or purchase a case and have a dedicated support engineer work with you directly

  • Reporting off of three main fact tables

    Hello all, we're starting work on a new universe and have run into some headaches.
    Here's some background : Our datawarehouse splits our charges, payments and adjustments into three separate tables.  Previously we've used a materialized view to join these three for Universe and reporting needs.
    We'd like to get away from using this mview, hence the new Universe.
    The issues we're running into are incorrect details and data aggregation.
    Have any of you successfully gotten around a similar issue without using a materialized view?
    Thanks!

    Hi Stratos, thanks for your suggestion but using derived tables isn't really an option for us as performance is critical and our BO Admins don't like the amount of proc time they use.
    We think we've found another option, I'll post back if it works.
    Thanks

  • Report based on two fact tables

    Hi,
    i've the same issue, of thread
    report based on 2 different Fact tables I've read reply marked as "CORRECT" but I don't understand what to do precisely. Can you explain better?
    How Can I create an alias?
    What about "If the dimensions are directly linked then mention detailed level else mention the total level which has no direct join b/w fact and dimension... "???
    I hope in your help. Thanks
    Thanks
    Giancarlo

    HI Daan,
    thanks for reply. Can you explain better point number 2?
    I have created an alias for my table (because i use MOLAP approach, i haven't a table but a cube view generated by View Generator Plug-in). Now what i must do with my alias table? Furthermore can you explain better point 2? Finally how i must create complex joins of my new fact table ?
    I am newbye of Administration Tool, so i would need of a visual explanation or of a step by step explanation. Can you give me it?
    I need of your help, because I must finish a project for my customer
    All regards
    Giancarlo
    Edited by: user5380662 on 27-mag-2010 5.07

  • Report based on fact tables that don't have the same dimensionality

    Hi all
    I want to combine in the same report different measures from different fact tables that doesn't have the same dimensionality,for example:
    measure 1 linked to dimensions : time geography and product
    measure 2 linked to dimensions : time and geography
    Currenctly when I create a report like:
    time----gepgraphy---product------measure 1-----measure 2 I don't have any data for measure2 because it's not linked to the product dimension.
    The exact report is year---store name---product area name----- store sales-----number of visitors : the number of vistors doesn't have any relation with the product dimension.
    Is there a way to create this kind of report??
    Regards

    Don't take this the wrong way guys, but I feel compelled to say this before the answers start coming in:
    This issue had been discussed already many times. Stijn, John, Kishore etc. have all answered this question for the one or the other user. This forum has a search functionality for a reason. To first look for information and then ask your question. Why wait - potentially - a couple of hours for an answer that's one search away?
    Seriously people. It's not like forums magically appeared in 2k7...they've been around for quite a while now and netiquette and common sense with regards to posting should become normal.
    Cheers,
    C.

  • Problems working with different types of aggregation in two facts table

    Hello every Body!! Greetings from Brazil..
    At fisrt I'd like to say that I've tried to find some thead with the same problem, but I've foud no answere. That is why I'm typing this new post.
    Here we go ...
    I've a Fact table with one metric and two degenerate dimensions..
    For exemple:
    Invoice_number
    Puschase_Date
    Purchase_Value$
    When I model it at Business Model Mapping, I used the Aggregation's type below:
    Invoice_number - None
    Puschase_Date - None
    Purchase_Value - Sum
    So far it works fine at Answeres area.. Since I use only values from this Fact..
    But... if I try to join values from two different Facts Table (both of them sharing the same Dimensions) and the Second Fact has an aggregated value, it does'nt work... I get 'null' as values (metrics) of the second Fact Table...
    I think that it is caused because I'm working whith different types of aggregation, but I don't know the solution.
    By the wat, the second Fact I've told has only one metric, aggregated whith 'SUM'.
    Is there a solution? Any hint?
    Tks.
    Vettore

    int x = (int)(7 + 3.0 / 4.0 * 2); //the variable will do the math bracket first. then the va type will still be an int because int was never changed.
    Following the standard order of operations, 3.0/4.0 will result in a double, then 2 will be converted to a double before being multiplied to the result, then 7 is converted to a double before being added to the result, and then the (int) cast will force a conversion
    back to an int.
    Console.WriteLine((1 + 1) / 2 * 3); // 1 + 1 will be done first then 1 / 2 then * by 3
    Correct.
    I THINK THATS ALL WRONG ^ =/ like the comments
    Why?

  • Re Joining two fact tables.

    Hi Experts,
    We have a requirement for a report to display columns from two different fact table.
    We have a Order Table W_ORDER_D dimension table,a Order item table W_ORDERITEM_F fact table & a INVOICE table W_INVOICE_F fact table.
    The requirent is that Order attribute information such as Order Id & order number is coming from the W_ORDER_D dimension table,The Quantity requested is coming from the W_ORDERITEM_F fact table & the Quantity Invoiced is coming from the W_INVOICE_F fact table.
    When we display such a report the report is displaying the OrderID,ORDERNUM,Quantity Invoiced,but the Quantity requested is coming as blank.
    and the following query is getting fired at the back end.
    select distinct T536200.QTY as c1,
    T31759.INTEGRATION_ID as c2,
    T31759.ORDER_NUM as c3
    from
    W_ORDER_D T31759 / Dim_W_ORDER_D */ ,*
    W_INVOICE_F T536200 / Fact_W_INVOICE_F */*
    where  ( T31759.ROW_WID = T536200.ORDER_WID and (T31759.ORDER_NUM in ('1-10016611', '1-10017512', '1-10019361')) ) )
    if you go through the query it is not picking the W_ORDERITEM_F fact table,but there are joins dified in the RPD between the W_ORDER_D & W_ORDERITEM_F table & the W_ORDER_D & W_INVOICE_F TABLE.
    Kindly suggest on the same.
    Thanks & Regards,

    Hi Goran,
    Thanks for your response I've already set the Order Logical Level to  Order Detail.
    Actually we have imported a new table in the repository W_INVOICE_F & defined the relationships between Various dimensions.One of the Dim is Order.
    My Question is that if Order is the common dimension between both the fact table W_ORDERITEM_F & W_INVOICE_F,then the Answers Result should display columns from both the Fact table based on the Concept of confirmed dimension..right??
    Please let me know if any other setting is required to define a dimension as confirmed dimension??
    We are using the Core business model
    Thanks & Regards,

  • Problem creating hierarchy based on 2 physical dimension tables

    I'm having a problem creating 1 logical dimension with a drill-down hierarchy, based on two separate physical dimension tables. The errors I receive when navigating the drill-down hierarchy is:
    "Cannot find logical table source coverage for logical columns" &
    "Missing join between logical tables".
    I'm using OBIEE 10.1.3.4
    Here are the details of what I have setup sofar:
    Physical layer:
    Dimension table DIM_ORG with columns:
    -dimension_key
    -org_total_code
    -org_total_description
    -org_detail_code
    -org_detail_description
    Dimension table DIM_DEPT with columns:
    -dimension_key
    -dept_total_code
    -dept_total_description
    -dept_detail_code
    -dept_detail_description
    Fact table FACT_SALES with columns:
    -fk_org
    -fk_dept
    -sum_sales
    Physical Joins:
    FACT_SALES.fk_org = DIM_ORG_dimension_key
    FACT_SALES.fl_dept = DIM_DEPT.dimension_key
    Business Model & Mapping layer:
    I created a logical dimension ORG_DEPT. It contains two logical table sources (DIM_ORG & DIM_DEPT) and the following logical columns:
    - All Departments (mapped to dept_total_code)
    - Organisation (mapped to org_detail_description)
    - Organisation Number (mapped to org_detail_code)
    - Department (mapped to dept_detail_description)
    - Department Code (mapped to dept_detail_code)
    The business logical key is based on the combination of Organisation Number & Department Code
    The hierarchy I need is: All Departments -> Organisation -> Department so I created the following hierarchy for ORG_DEPT:
    - Total Level containing: All Departments
    - Organisation Level containing: Organisation Number (defined as the Logical level key) & Organisation (defined als the Drill level key)
    - Detail Department Level containing: Department Code (defined as Logical level key) and Department (defined as Drill level key).
    In the LTS of the dimension ORG_DEPT I've set the Content levels for the sources:
    DIM_ORG : Organisation Level
    DIM_DEPT: Detail Department Level
    In the LTS no -inner- joins have been added against related physical tables.
    I created a logical fact table SALES (based on the physical fact table) and joined it against the logical dimension table ORG_DEPT.
    In the LTS the Content level for ORG_DEPT is set against the Detail Department Level. No - inner- joins have been aded against related physical tables.
    When I create a report in Answers to test the hierachy and select only 'All Departments' I get the correct dimension value returned. When I try to drill to the next level I get the following ODBC error:
    "Cannot find logical table source coverage for logical columns: [All Departments]. Please check more detailed level keys are mapped correctly".
    When I create a report in Answers and select both 'All Departments' and 'Sales' I get the correct result. When I try to drill to the next level I get a different ODBC error:
    "Missing join between logical tables DIM_DEPT and DIM_DEPT: There must be at least one physical join link between the underlying physical tables".
    Any suggestions are welcome!
    Thanks!

    Hello Robert,
    Your suggestions were known to me but I still wanted to combine the two physical dimension tables in one logical dimension. So I've played around a bit more and found the solution: In my original setup I had two seperate logical table sources (one for each physical dimension table). The solution was to combine the two logical table sources in one logical table source. I achieved that by logical joining the DIM_DEPT table to the FACT_SALES table and subsequently to the DIM_ORG within the 1 LTS and using inner joins.
    Then I created the logical table key (a combination of org_detail_code & dept_detail_code). After that I could create the hierarchy with no problem.
    Edited by: The_Dutchman on Nov 4, 2011 9:43 PM

  • Two Filter on Two dimensions without constraining the fact table

    Hi All,
    does anybody know how to avoid the fact constraint when creating a report with two filters on different dimensions?
    I have a big fact table with more than 10 Million rows. In the starmodel the is the dimension customer and products. I create a filter on the customer atrribute "Status" and choose the value "Active". Now I add the column "Product Type" from the dimension "Product" to the filter section. When I want to choose a value OBIEE executes a select statement within the fact table. So I have to wait very long to select a value. Is there any way to say OBIEE only to select the dimension table without joining the fact table?
    Thank you very much in Advance.
    Regards,
    Stefan

    Hi Stefan,
    Generally queries on the dimensions (across dimesions also) always go through a fact. In case, you would like the queries not be through fact table, but just the dimension tables right away, you can set up a separate subject area for them.
    You can create a separate subject area based on a dummy fact table to get these prompt values.
    Please refer to http://gerardnico.com/wiki/dat/obiee/presentation_service/obiee_parameter_prompt_subject_area for more details on this setup.
    Hope this helps.
    Thank you,
    Dhar

  • Best way to combine multiple fact tables in single mart

    Hi, quick question that I think I know the answer to, just wanted to bounce it off everyone here to make sure I'm on the right track.
    I have a HR datamart that contains several different fact tables. Some of the facts are additive across time (i.e. compensation - people get paid on different days, when I look at a month I want to see the total of all pay dates within that month). The other type of fact is more "status over a set of time" - i.e. a record saying that I'm employed in job X with a salary of Y from a given start date to a given end date.
    For the "status over time" type facts, if I choose January 2009 (month level) in the time dimension, what I'd really like to see is the fact records that were in place "as of" the last day of the month - i.e. all records where the start date is on or before 1/1/2009, and whose end date is on or after 1/1/2009. Note that my time dimension does go down to the day level (so you could look at a person "as of" the middle of the month, etc. if you're browsing on a day-by-day basis)
    I've set up the join between the time dimension and the fact table as a complex join in the physical layer, with a clause like "DIM_DATE.DATE >= FACT.START_DATE AND DIM_DATE.DATE <= FACT.END_DATE". This seems to work perfectly at the day level - I have no problems at all finding the proper records for a person as of any given day.
    However, I'm not quite sure how to proceed at the month level. My initial thought is:
    a) create a new LTS for the fact table at the month level
    b) in the new LTS, add the join to the time dimension
    c) in the new LTS, add a where clause similar to LAST_DAY_IND = 'Y' (true for the last day of each month).
    Is this the proper way to do this?
    Thanks in advance!
    Scott

    Hi Scott,
    I think you're on the right track but I don't think you need the last part. Let me generalize the situation to the following tables
    DAILY_FACT (
    DAILY_FACT_KEY NUMBER, -- PRIMARY KEY
    START_DATE_KEY NUMBER, -- FOREIGN KEY TO DATE DIMENSION FOR START DATE
    END_DATE_KEY NUMBER, -- FOREIGN KEY TO DATE DIMENSION FOR END DATE
    DAILY_VALUE NUMBER); -- FACT MEASURE
    MONTHLY_FACT(
    MONTHLY_FACT_KEY NUMBER, -- PRIMARY KEY
    MONTH_DATE_KEY NUMBER, -- FOREIGN KEY TO DATE DIMENSION, POPULATED WITH THE KEY TO THE LAST DAY OF THE MONTH
    MONTHLY_VALUE NUMBER); -- FACT MEASURE at MONTH LEVEL. DATE_KEY is at END of MONTH
    DIM_DATE(
    DATE_KEY NUMBER,
    DATE_VALUE DATE,
    DATE_MONTH VARCHAR2(20),
    DATE_YEAR NUMBER(4));
    DIM_DATE_END (ALIAS OF DIM_DATE for END_DATE_KEY join)
    Step 1)
    Make the following three joins in the physical layer:
    a. DAILY_FACT.START_DATE_KEY = DIM_DATE.DATE_KEY
    b. DAILY_FACT.END_DATE_KEY = DIM_DATE_END.DATE_KEY
    C. MONTHLY_FACT.DATE_KEY = DIM_DATE.DATE_KEY
    Note: The MONTHLY_FACT DATE_KEY is joined to the same instance of the date dimension as the START_DATE_KEY of the DAILY_FACT table. This is because these are the dates you want to make sure are in the same month.
    Step 2)
    Create a business model and drag DIM_DATE, DAILY_FACT and DIM_DATE_END into it.
    Step 3)
    Drag the physical table MONTHLY_FACT into the logical table source of the logical table DAILY_FACT.
    Step 4)
    Set DAILY_VALUE and MONTHLY_VALUE to be aggregates with a "SUM" aggregation function
    Step 5)
    Drag all required reporting columns to the Presentation layer.
    Step 6)
    Create your report using the two different measures from the different fact tables.
    Step 7)
    Filter the report by the Month that joined to the Start Date/Monthly Date (not the one that joined to the end date).
    Step 8)
    You're done.
    The act of combining the two facts into one logical table allows you to report on them at the same time. The strategy of joining the START_DATE_KEY and the MONTH_DATE_KEY allows you to make sure that the daily measure start date will be in the same month as the monthly fact table.
    Hope that helps!
    -Joe
    Edited by: Joe Bertram on Jan 5, 2010 6:29 PM

Maybe you are looking for