Two facts with joins to all dimensions

I have two dimension tables say D1, and D2 and they are joined to two facts F1 and F2. Now I need a report from one column of d1 and other column of d2 how obiee server will perform query by only one fact or two facts if only one fact which fact it will go through.

OBI will select one fact....I think it's based on the order of the facts in the business model.
But, you can set an implicit fact columns in the presentation layer...this gives you the possibility to add implicitly the fact table that must be used when only dimension objects are selected.
Hope this answers your question.
Kr,
A

Similar Messages

Query across two facts with filter on unconformed dimension

Hi
This question is actually regurgitated from another post as I wrongly tagged it onto the end of an already answered question.
Anyway, I am trying to query across 2 fact tables which have a dimension in common (conformed) and also some dimensions that are not directly joined to BOTH fact tables (seemedly referred to as 'unconformed' in OBIEE).
So in it's simplest form
Fact1, measure1 linked to dim1 & dim2
Fact2, measure2 linked to dim2 only
I have followed the recommended method advertised here and elsewhere of adding the second fact as a LTS of the first in the BMM layer and setting logical levels on measure2 to Total for all dimensions that fact2 is not joined to (in this case dim1).
When a basic query is issued in Answers that filters on the unconformed dimension (dim1), a spurious result set is returned that includes all records for the second fact.
This is quite a standard warehousing reporting query whereby 2 sets of data are queried independently and then joined on their common attributes but in this scenario the BI server seems to always generate a FULL OUTER JOIN and return an unrestriced data set.
Has anyone else come across this strange behaviour?
thanks
Tony

adding the second fact as a LTS of the first in the BMM layer
Could you try without this step? Just have separate facts and separate LTSs and set
Fact1 LTS to lowest for Dim1
Fact1 LTS to lowest for Dim2
Fact2 LTS to Total for Dim1
Fact2 LTS to lowest for Dim2
?

Best way to connect two fact tables when no conformed dimension exists

Can anyone please elaborate how would I connect two fact table without any conformed dimension. Let say FACTA, FACTB. FACTB is related to a dimension "StatusDim". I want to select the count of all FACTA item which are related to FACTB items with
a particular status. I have found the following article but just wondering whether it is the best practise to connect two fact tables directly.
http://bifuture.blogspot.com/2011/11/ssas-selecting-facts-with-reference.html
Thank you

Hi Ahsan,
After read the blog you posted, I think it's a pretty good solution to create a view in the relational database or a named query in the Data Source View containing as the the columns in FACTA and FACTB. Then build a dimension from it, setting the "Null processing"
property (you have to click the "plus" two times for the "Key Columns" property of the attribute in BIDS to access this property) to "UnknownMember". And then use this dimension for the many-to-many relationship. Dimensions from FactA can benefit of the reference
relationship between FactA and FactB and therefore a powerful solution it is.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Joining Two facts with one dimension

hi,
Hello Experts,I am reporting out of 2 fact groups.
Mailing History and Booking.
The only common dimension between the 2 is the Person Dimension. I have created the hierarchies and defined the aggregation content in the LTS.This helps me in reporting using any column from the Facts or any one dimension from either of the fact groups. But if i select 2 or more dimensions , one or more from each fact group , then the report gives and error. A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: MailingHistory Campaign.Campaign Name. Please fix the metadata consistency warnings. (HY000)
For Example : BookingDim--BookingFact-MailingHistoryFact (ok) MailingSourceDim--BookingFact-MailingHistoryFact works (ok) but BookingDim--BookingFact-MailingHistoryFact - MailingsourceDim (Fails ).
When i am applying the filter from the fact 1 . i am getting this error.(which is the column in the second fact table 2).I checked all the joins in the BMM layer.
Please help me!!!
Thanks,
Surya

Surya did you set the levels properly for two fact tables and also for metrics.
When ever you are using two fact groups with non confirmed dimensions you have to make sure all the content levels set for the fact tables and as well as for metrics.
in your fact tables/ metrics - For related dimensions set the level to Detail. and for the non related dimension set the level to Total. This way obiee server will understand what is related dimension and whats not related..
hope this works for you.

Unable to join two fact tables via one common dimension in RPD(Repository)

I have created two fact tables F1 & F2 and one dimension D.
F1 is joined to D and F2 is also joined to D in Physical layer as well as in BMM layer.
I created one report in OBI Answers using these three tables.It Showed me the following error.
**Error Details**
**Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P**
**State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table dfghdfh) does not contain mapping for [Dashboard_Fact.Period_Sgt_Key]. (HY000)**
**SQL Issued: SELECT dfghdfh.Period_Sgt_Key saw_0, "Period Dim".Period_Sgt_Key saw_1, Dashboard_Fact.Period_Sgt_Key saw_2 FROM service_delivery ORDER BY saw_0, saw_1, saw_2**
How to cope up with the issue or can anyone tell me the alternate workaround for this?

That is what i have tried.
I have made a logical table TEST and dragged two fact tables f1 & f2 in source.
Now when i drag different columns from different fact tables(that are in TEST logical table) in report, it gives an error and not making any joins that you are mentioning.
ERROR MESSAGE:--
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Test) does not contain mapping for [Test.SurveyName_Id, Test.SurveyHead_Id, Test.Respondent_Id, Test.SDBusiness_Area_Id, Test.Period_Sgt_Key, Test.OBS_Id, Test.VOCBusiness_Area_Id, Test.Question_Sgt_Key]. (HY000)
The columns mentioned in the error message are all from test logical table..some are from F1 & some from F2.

Two facts with conformed dimension

Starting new thread per Alistair's request :)
I have two facts
Class Enrollment (who is enrolled in which classes)
External Test Scores (who got what score on what exam)
The only dimension they have in common is "Person".
Is it possible to build a presentation layer that includes both facts, the Person dimension, and dimensions that related to one fact but not the other (e.g. dimension "External Test Type" or dimension "Course")?
How would I set up the BI metadata to answer the question:
What was the average grade for Course ABC for students who scored above a 50 on test XYZ?
So far, for External Test Scores fact, I have created hierarchies(/dimensions) for any related dimension tables that didn't already have hierarchies defined. I then went to the Content tab for External Test Scores and set aggregation levels (lowest level for everything related to the fact, "total" level for everything NOT related to the fact).
I put both facts and the "Person" dimension into a presentation folder. I can query test scores ok, but when I add in a simple "Row Count" column from class enrollment, I get no data back.
Do I now go back and do the same Content tab settings for the Class Enrollment fact? My initial attempts at this yielded consistency check warnings of "Logical table source does not join to any fact source".
Huge thanks for suggestions.
-John

Hi John,
I tend to harp on a lot about the need for a hierachy on every logical dim, even just total -> detail. It allows this (non-conformed) approach for starters, also allows another developer to quickly ascertain the relationship between objects.
About the complex joins, I meant do as you will have done for a normal star with just the conformed dims, so thats Foreign keys where applicable in the Phyiscal layer, and Complex joins where applicable in the BMM layer. I just wanted to make a point that you should do this as per a normal normal star schema with fully conformed dimensions, and merely that the none-conformed dimension will only be connected to its relevant fact table - probably didnt need to say it as it may be more confusing!
Your correct with aggregation rules, ideally all objects in a logical fact should have an aggregation rule - otherwise it should be in a logical dimension.
As to the approach, this is the way i've always handled non-conformed dimensions when the requirement is to see both facts on the same report. Our Peak Indicators OBIEE training material on this subject is as follows :
"order" fact table, dimensioned by Date, Customer, Product.
"inventory" fact table dimensioned by Product only.
Report requirement - Show me all orders where the order_qty (order fact) is greater than the total qty in stock (inventory fact)
So like your example, we sum up both qty's and use a where clause to filter only rows where one fact measure is greater than another measure.
Whats the ideal approach ??
If you had control of the ETL perhaps you could seed an 'unknown' record in the non-conforming dimensions, and then reference this on the other fact table, but I'd say the majority of the time, the customer who wants everything by everything in their subject area needs a little education, its really not good for end users having 10's of folders with 10's of columns - we should be creating analysis subject areas to enable the answering of business questions, theres no reason why we cant combine reports from different subject areas on one dashboard page, all using a common set of prompts, but there really isnt a need to give an end user the whole BMM / DW etc in one go.......unless they are paying of course, and after you've tried to educate them they want it there way :-)

How to Link two Facts with Different Time Granularity (Year, Quarter) to a Single Time Dimension

Hello All,
I have the below scenario where i have Two Facts Fact Quarterly and Fact Yearly but one Time Dimension which has Quarter grain.
So my question is how do i Establish relationship from Fact Yearly to Time Dimension??
Ex:

Hi naveej,
According to your description, you want to know how to build the relationship with time dimension and fact tables. Right?
Based on your screenshot, it's better to have only one fact table for sales and build the relationship with time dimension. To determine quarterly or yearly data only depends on how you slice the time dimension. However, I notice that the Revenue for year
is different from the aggregated Profit for quarters. If the Revenue and Profit are different measure, you need to have two fact tables. And you should build the relationship (Regular) between TimeDim and FactYearly on YYYY attribute.
Reference:
Defining a Fact Relationship
Best Regards,
Simon Hou
TechNet Community Support

Multiple facts with shared/non shared dimensions

Hello All,
I have a scenario where we are using multiple facts in OBIEE. Fact1(Inventory Onhand) is joined to all shared dimensions, and Fact2( Forecasting Values) is joined to few shared dimesnions so the joins are like:
Fact1 with Dim1, Dim2, Dim3, Dim4, Dim5, Dim6..
Fact2 with Dim1,Dim3, Dim5
I have given the physical joins in the physical layer, later in the logical layer I pulled the fact2 in to to the fact1(multiple LTS) and then set the aggregattion levels for the non conformed dimensions. This was working fine for me but the customer was not happy with this. He doesnt want to have different levels of data in to a single fact.
What are the allternate possible solutions to implement this in the busines layer?
Any ideas/inputs are highly appreciated.
- Abhi

Hi,
I have done the same as explained above. But here the issue is we are getting duplicate data.
For Ex: if i have one common dimmension attribute and two non confirmed dimension attributes with a measure. For non confirmed dimension have different value and for all these values the common dimension attribute is same. Then the common attribute will repeat for all non confirmed dimensions.so, here automatically the Corresponding measures also repeating.
Common Attr non-Confirm Attr1 non-Cnfirm Attr2 measure
123 abc xyz 1000
123 bac yzx 1000
123 pqr mno 1000
If you observe the above exapmple the confirm dime attr is same for both non confirm dime attrs, so the measure values also repeating here. If i see the data base i have measure data only for ABC record. For Remaining two records it is 0, but here the value 1000 is showing for remaining two records as well.
Please let me know if any one face this issue earlier.
Regards,
Aari

"Semi/Non additive measure with" : "LastChild Across All Dimension" OR "LastChild Across Time and MAX across All Other Dimension"

Hey All
I am using the SQL SERVER 2008R2 standard edition so please be mindful when posting any suggestion if that will work on this edition or not.
Here is the situation: I have Cube with one fact table "Positions". Measure I am querying is "AUM" and Dimensions across user can query are combinations of {"Portfolio", "Security" and "Time"}.
I am receiving the "AUM" values at "portfolio+Security+Time" level. AUM is actually the Portfolio level value. so sample data I receive would like this.
PORTFOLIO SECURITY TME AUM
A SEC1 JAN-1 100
A SEC2 JAN-1 100
B SEC1 JAN-1 200
B SEC3 JAN-1 200
A SEC1 JAN-2 300
A SEC2 JAN-2 300
B SEC1 JAN-2 400
B SEC3 JAN-2 400
So, as shown in above example , we received same "AUM" value for a given portfolio and time. (regardless of what security value is).
And as AUM is the snapshot values, we can not sum across time as well, so if user is looking across time we need to pick Last values.
Now when user wants to view this data from cube, two different ways s/he wants to look at it.
option one: AUM at port+sec+time level. that is same as shown above in example.
option two: AUM at portfolio level only, (notice that this is across time so results are picking values for time=JAN-2)
PORTFOLIO AUM
A 300
B 400
GRAND TOTAL 700
I have applied the "LastChild" aggregation property to measure to achieve "Do no Sum across Time "behavior. but with this I also get "SUM Across Except time" and hence my AUM values get summed across Portfolio and security as
well. I have also enable Time Intelligence to enable MTD, YTD calculations.
I tried to add SCOPE statement for Security before and after the "time calculations" yet I am not able to achieve expected behavior.
here is the calculated member definition, and scope statement i have tried.
CREATE MEMBER
CURRENTCUBE.[MEASURES].[AUMNetBaseCurrency] AS
[Measures].[AUMNetBaseCurrency_Raw_Max],
FORMAT_STRING = "#,##0.00 ;( #,##0.00 )",
VISIBLE = 1 , DISPLAY_FOLDER = 'Position';
After this I have MTD and YTD time calculation for few measures including AUM.
I tried placing the following SCOPE for AUM before and after the Time calculations but it no difference in result, in fact it seems like it has no affect of scope at all due to the "LastChild" aggregate property applied on measure.
SCOPE([MEASURES].[AUMNetBaseCurrency]);
SCOPE([Security].[Symbol].[All]);
THIS = MAX([Measures].[AUMNetBaseCurrency_Raw_Max]);
END SCOPE;
END SCOPE;
so options I am thinking of but do not have clear idea how to implement those are:
0) why my Security Scope Statement are not showing any effect, and can we do something about it?
1) Can be change "SUM" behavior to "MAX" / "MIN" across all Dimension except time.
2) Is there a way to implement "LastChild" across all dimension instead only across Time.
3) Should I need to make any changes at Fact table level to achieve this ? I refer one Q&A in this forum that suggested to create such measure in different measure group but it doesn't have any clarification.
Any help would be appreciated.
Thanks
Anup Shah

hi,
you will have to enable cache in your nqsconfig.ini file under the section
# Query Result Cache Section
[ CACHE ]
ENABLE = YES;
cache seeding is also a mechanism through which the data would be updated in the cache.

Problem: two fact tables and one conformed dimension

Hi everyone!
I need to solve this situation:
I have two fact tables, let's say F1 and F2, that are both linked to D1, my conformed dimension
I just need to select fields from D1 but I know that, when querying, OBIEE links it to a fact table anyway..how does it choose the fact table? That is, if I only want fields from D1, does the system queries also from F1 or F2? Is it a random choice?
Is there a way to "force" this choice, telling the system for example to choose only from F1?
Is there a workaround to solve this situation? Remember, I only need fields from D1.
Thanks!!

The solution of your problem is "Implict Fact Column"
Go to presentation layer and double click on your subject area. then you will see Implict fact column option. click on set. give corresponding fact column there( in your case give F1 fact column)
references: http://oracle-bi.siebelunleashed.com/articles/implicit-fact-column/
Thanks
GSR
Edited by: GSR on Mar 20, 2012 3:22 PM

Multiple facts with some non-conforming dimensions

Hi, in our datamart, I have several fact tables. The JOBS fact table includes dimensions of time, employee, org, and job.
Other fact tables include those 4 base conformed dimensions, plus dimensions specific to the fact. For example, BENEFITS includes a "plan type" dimension, etc.
When reporting, I want counts from the basic JOBS fact table to always show up - even if other data in the report contains the "non-conformed" dimensions. For example, I'd like a report that lists time periods, employee counts (from JOBS fact), and enrolled employee counts (from BENEFITS fact), something like this:
Month Benefit Plan Emps Enrolled Emps
Jan 2009 Health Insurance 10,000 8,000
Jan 2009 401k Plan 10,000 4,000
Jan 2009 AD&D 10,000 1,000
When I try to produce this report, because "benefit plan" is not a dimension tied to the JOBS data, the EMPS column comes out blank. Yes, I can add a total row at the bottm to show it...but I really want the 10,000 to show up on each row (also because I want to calculate a % of people enrolled out of the total population).
What's the best way to accomplish this? Also given that I have 4 or 5 other fact tables, and each of them have their own "personal" dimensions in addition to the conformed ones.
Thanks in advance!
Scott

Hi
The problem you describe is similar to mine (I wrote several threads ago).
That is, if there is a non-conformed dimension in a report then the column from the fact table which is not connected with those non-conformed dimensions containes zeros or blanks.
Was this problem solved? I didn't quite catch one of previuos messages... If you can please repeat it more detailed.
What I tried to do is to set Total level in the Content tab (LTS properties). In this example - I could set Total level to JOBS in the plan type dimension. But it didn't help.
So if you know what to do then please describe it here...

Confirmed Dimensions. OBIEE Not able to pull data from two fact tables.

Hi Experts,
I have a very simple set up of Star Schema with two fact tables and 1 dimension. Both fact tables joined to the dimension at the same level.
When i pull a column from both fact tables and the dimension table in OBIEE, it has to create simple SQL like below:
select FACT1.column1,
Fact2.Column1,
Dim.Column1
from FACT1, FACT2, DIM
where FACT1.ID = DIM.ID and FACT2.ID = DIM.ID
but instead it creating a query in a very complex way:
select case when D1.c2 is not null then D1.c2 when D2.c2 is not null then D2.c2 end as c2,
     D1.c1 as c3,
     D2.c1 as c4
from
     (select FACT1.Column1 as c1,
               DIM.Column1 as c2
          from
               DIM T1287863,
               FACT1 T1287945
   where (DIM.ID = FACT1.ID)
       ) D1 full outer join (
        select FACT2.Column1 as c1,
               DIM.Column1 as c2
          from
               DIM,
               FACT2
          where ( DIM.ID = FACT2.ID)
     ) D2 On isnull(D1.c2 , '1') = isnull(D2.c2 , '1') and isnull(D1.c2 , '2') = isnull(D2.c2 , '2')
I even tried setting the levels for both the fact tables and it still creates the query in avove way. Any thoughts on this will be vary helpful.

Subramanian,
see below the code we're using for the RFM.
on the ct_containers table i'm passing a line, and its getting updated after the call.
on the ct_errors table i just want to receive the errors and i only receive the line, we add manually there ('Serious error with validation code').
kr, achim
FUNCTION zbapi_ra_validations .
*"*"Local Interface:
*" IMPORTING
*"     VALUE(IS_RA_SCREEN) TYPE ZBAPI_S_RA_SCREEN
*" CHANGING
*"     VALUE(CT_ERRORS) TYPE ZRA_T_ERRORS
*"     VALUE(CT_CONTAINERS) TYPE ZRA_T_CONT_IP
DATA:
    lo_badi_handle TYPE REF TO zra_validation_rule,
    ls_error       TYPE zra_s_error.
GET BADI lo_badi_handle.
TRY.
      CALL BADI lo_badi_handle->validate_rules
        EXPORTING
          is_screen_flds = is_ra_screen
        CHANGING
          ct_containers = ct_containers
          ct_errors      = ct_errors.
    CATCH zcx_ra.
      ls_error-message = 'Serious error with validation code'.
      APPEND ls_error TO ct_errors.
ENDTRY.
ENDFUNCTION.
if i call this rfm in SE37 the ct_errors table is populated with all errors and the manually created line.
Message was edited by: Achim Hauck

Joining two fact tables for subject area

When I tried to use two simple fact tables joined by a dimension, I am getting the “ No fact table exists at the requested level of detail” error in the answer when I try to pull the columns from Fact 1 and Fact 2 tables. I have set the content in both the fact table to lowest granularity of dimension with CUST_ID, RAT_ID, ACT_ID keys. We have one to many relationships between dimension and both the fact tables. Any feedback is highly cherished.
Fact1: keys are: CUST_ID, RAT_ID, ACT_ID, YEAR
Fields are CUST_ID, RAT_ID, ACT_ID, YEAR , Rev1, Transaction Date
Fact2: keys are: CUST_ID, RAT_ID, ACT_ID, YEAR
Fields are CUST_ID, RAT_ID, ACT_ID, YEAR , Rev2, CreationDate
Dimension keys are CUST_ID, RAT_ID, ACT_ID
Thanks,
uday

Hi LC,
We have to add two fact tables F1 AND F2 to an existing bmm. These fact tables have history tables F11 AND F22 and we have to use partition logic for this.How you did partition ? you should be using Fragmentation logic for that any how you will add the F11/F22 tables to F1 and F2 LTS , so when you join F1 & F2 to the common dimension then it should work for the calucluated measures but dont forgot to create hierarchies and specify the content levels for the fact tables
Thanks,
Saichand

Joining Facts with Different Grains

Hello
We have a requirement where we have two facts with different grains
DEPT_FACT - Contains (Dept_Id, Dept_Name, Revenue)
EMP_FACT - Contains (Emp_Id, Dept_Name, Is_Current_Employee)
Here is some sample data
DEPT_FACT
========
1 Sales_Dept 100,000
2 Manufacturing_Dept 200,000
EMP_FACT
========
100 Sales_Dept Y
200 Sales_Dept Y
300 Sales_Dept N
400 Manufacturing_Dept N
500 Manufacturing_Dept Y
600 Manufacturing_Dept N
Our requirement is to create an OBIEE report that shows the *"Revenue/ Number of current employees in department BY Department"*
The above example must show
Sales_Dept => $50,000 (100,000 / 2 current employees)
Sales_Dept => $200,000 (200,000 / 1 current employee)
Any suggestions on how this can be done ?

For me,
DEPT_FACT is not a fact. It's a dimension table because you have a one-to-many relationship and you have a measure in the dimension table (it's an aggregated measure).
And EMP_FACT is also not a fact because you don't have any measure on it.
But if we say that EMP_FACT is a fact. DEPT_FACT is an aggregated table from EMP_FACT.
I will :
* create a logical dimension for the employee with three levels (all, departement and detail)
* create a logical fact table with :
- one logical column for the revenue in the level all departement
- one logical column for the employee
and two physical source :
* DEPT_FACT with the departement level
* EMP_FACT with the level to detail
Success
Nico

Multiple fact - outer join

Hi all,
let's say that I created two facts
1) ALL_RELATIONS_FACTS: two dimensions
      d1: START_POINT
      d2: END_POINT
START_POINT END_POINT
1            2
3            4
1            3
A row in this fact means that the relationship exists, not all relationships will be measured
2) ALL_MEASURE_FACTS: three dimensions
      d1: START_POINT
      d2: END_POINT
      d3: DATE
      MEASURE1
      MEASURE2
START_POINT END_POINT DATE       MEASURE1    MEASURE2
1            2          20121023   100         200
3            4          20121023   300         400
A row in fact gives us measures on a certain date for a certain relationship.Now I would like to merge these two facts (with an OUTER JOIN).
START_POINT END_POINT DATE       MEASURE1    MEASURE2
1            2          20121023   100         200
3            4          20121023   300         400
1            3          20121023Could someone point me to a standard solution?
Riccardo

I don't get why you are telling me "ONE" confirmed dimension.
My current BMM is
ALL_RELATIONS_FACTS
    |           |
start_point   end_point
    |           |
    D1         D2
    |           |
start_point   end_point
    |           |
ALL_MEASURE_FACTS -------- DATE

Two facts with joins to all dimensions

Similar Messages

Maybe you are looking for