Fact Join Issue

I am having star schema,Fact1 and dim1,dim2,dim3
Now i am bringing one more fact table(fact2)..... common table between both fact i hav currency column like AED,INR,USD,other thn this i dont hav any common table to join with other dimension table
so my join look like this
fact2<<<<<fact1>>>>>>dim1
After joining this if i try to drag column from dim1 and fact2,i do not get any result from fact2,
I get below error
Error:None of the fact tables are compatible with the query request
so can i know how to make this work,is it possible?

To fix your issue.. without looking at your data.. follow as below
In BMM layer to the existing fact1->source properties-> General Tab
Click on Add button and add the fact2 and pull required columns to existing logical fact table.
Appreciate if you mark as correct/helpful

Similar Messages

AP - WLC joining issue

We have 3 WLC's(5500) in our network and about 150 AP's. Only 4 AP's register to 1 controller, over 70 to 2nd and about 50 to 3rd. On checking & comparing few of the AP's this is what i concluded.
1. 4 AP's that registered to the first WLC did not have that AP in the primary, secondary or tertiary list. If it was there then it was either secondary or tertiary or the device name entered is not resolvable by DNS but the device name is correct. Management IP was not configured on any of the 4 AP's for any of the WLC's
2. AP's registered to second and third WLC's have similar config. First WLC as Primary, Second as secondary and third Tertiary with correct DNS name in the field but wrong device name. Also all have Management IP's entered as well.
CAPWAP Join Taken Time for 4 AP's varies from 6to10 mins while for other AP its few seconds. DNS for cisco-capwap-controller points to WLC with4 AP's. I donot see any use of option in DNS for WAP's.
How can i make AP's join this WLC.
Should I get the DNS and device name discrepancy corrected?
What is the selection process for AP's to choose WLC, as I see AP's not joining WLC in there building but joining a WLC in other adjacent building? Is there a way for me to influence this decision?

What is the selection process for AP's to choose WLC, as I see AP's not joining WLC in there building but joining a WLC in other adjacent building? Is there a way for me to influence this decision?
Best way to do this is configure AP High Availability of APs with primary,secondary,tertiary WLC name & IP (both fields required). This is taking precedence over any other methods.
http://mrncciew.com/2013/04/07/ap-failover/
If you have AP join issue, try to configure DHCP option 43 & see if that helps
http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/97066-dhcp-option-43-00.html
If this is one off case, you can try static or broadcast forwarding as a interim solution
http://mrncciew.com/2013/03/17/ap-registration/
http://mrncciew.com/2013/05/04/wlc-discovery-via-broadcast/
HTH
Rasika
*** Pls rate all useful responses ***

Outer join issue

Hi all,
I have a question regarding to Outer joins. This is my situation:
Sales (fact table)
id_company
id_product
yearmonth
units
dollars
Products (dimension table)
id_company
id_product
The 2 tables joins by id_company and id_product.
For a month, I need to get the units and dollars of all the products, if a product is not sold in that month the units and dollars will be zero.
The following query doesn't retrieve the correct results, because a product that is not sold in a month could be in another.
select
p.id_company, p.id_product, sum(s.units), sum(dollars)
from
products p, sales s
where
p.id_company = s.id_company(+)
and p.id_product = s.id_product(+)
and s.yearmonth = 200805
group by p.id_company, p.id_product
So this query gives the correct results:
select
p.id_company, p.id_product, sum(s.units), sum(dollars)
from
products p,
(select * from sales where yearmonth = 200805) s
where
p.id_company = s.id_company(+)
and p.id_product = s.id_product(+)
group by p.id_company, p.id_product
My question is, how can I implement the 2nd query in OBI? Is there an easier way to perform the select without sub-select?
Thanks in advance.

You need to bring in the yearmonth from the product table itself for this to work.
e.g. if you product has 100 rows and you have 10 yearmonths, then your new product table will have 100*10 = 1000 rows. You can achieve this by snowflaking in physical layer (time --> product on 1=1 complex join) . keep the time-fact join in physical layer.
(If you don't want above, then create a view in db or physical layer with time full outer join product and joinng the resultant view to fact on yearmonth, id_companyand id_product )
Then bring the yearmonth column in product logical table in the same LTS with outer join specified.
In answers, use p.id_company, p.id_product, sum(s.units), sum(dollars)where p.yearmonth is filtered.

Fact joins in Physical ayer

Hello All,
I recently joined in a project, I was going through the RPD and I can see there are Fact to Fact joins in Physical layer..however there are no Fact joins in BMM layer.
I'm trying to understand why these joins are created and how it will impact in BI query's. Thanks...

It is Fact to Fact Extension they have joined i guess.
http://satyaobieesolutions.blogspot.com/2012/07/implementing-multiple-fact-tables-in.html
Mark if helps.

Join issues with Multicube reports

I experts,
We have a Multicube M with a Real time cube A and Basic Cube B. Cube B was added to the Multicube recently.
Cube A contains Phasing data ( like Forecast) for Opportunities. See some eg records below.
Oppt PERIOD KF1
001   001       10
001   002       20
001   003       30
002   001       40
002   002       20
002   003       30.
Cube B containes Opportunities and Customer ( with Nav Attr). The Customer master data looks like below. Here both TYPE and GROUP are Nav attr of Customer.
Customer Type Grp
C1            T1     G1
C2            T2     G2
Cube B contains records as shown below
Oppt Customer KF2
001   C1           100
002   C2           300.
Now when we ran our Report on MultiCube, we expect to see below
Oppt Period Customer Type Grp KF1
001     001       C1        T1    G1   10
001     002       C1        T1    G1   20
001     003       C1        T1    G1   30
002     001       C2        T2    G2   40
002     002       C2        T2    G2   20
002     003       C2        T2    G2   30.
But in place Customer, Type, Grp, we get 'Not assinged" .
I have checked teh identification for all KFs and Chars, they are identified.
Can anyone help??
Thanks,
DV

Can you check for the data inside the infoproviders in the cubes with the manage option. It possible when the grouping is not done properly. Check for the Master date entry of the customer. I dont think its because of the join issue..
Good Luck..
Sandhya

Does not join to any fact source issue in 10g

HI,
I am getting below issue while compiling rpd.
Logical Dimension Table Dim-XX has a source xx_aa that does not join to any fact source.
Let me describe situation here.
In physical layer , i have one xx_v table . there is no join condition physical layer. But in BMM layer we have created two logical tables for single xx_v table and providing join in bmm layer. When am compiling it i'm getting an error.
The one which i have using current rpd, same rpd in production with out any warnings(Logical Dimension Table Dim-XX has a source xx_aa that does not join to any fact source) and they don't have any logical level mapping in content tab. But i am using same rpd in dev instance getting warnings.
Thanks,
Mal
Edited by: user10675696 on Feb 11, 2013 3:08 AM

Hi Srini,
Please find the below warning here and we don't have an hierarchy for MTL_SYSTE_ITEMS_B
[39008] Logical dimension table Mtl System Items B has a source MTL_SYSTEM_ITEMS_B that does not join to any fact source.
I am getting this in Dev instance only but not in Production. But one rpd can be used in dev and production instances.
Thanks,
Mall

Fact - dimension and Fact Join

Hi ,
I have a issue in OBIEE 11g here ,
I am trying to query two columns from 2 different fact tables F1 and F2
the join between these tables is F1 - D - F2 , where D is the confirmed dimension.
so when i am querying for
f1.c1 , d.c1 , f2.c1 , its throwing me up with error
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request
Can you please help me with this issue , am i doing the correct join ??, can we query two columns from two diff fact tables?
Thanks in advance.

Hi All,
Thanks for your responses , I have tried creating hierarchy dimension and assgned levels to the fact sources but i still see the error
and
Combining 2 facts will resolve the issue but its not the case here as each fact table has about 25 dimensions connected to it , but there are only 2 confirmed dimensions between both facts and the problem here is user wants to see both the fact tables in the same subject area
I have been trying but unable to get the solution.
Can you guys please suggested any other way of achiving this task
Thanks a lot

Joins issue in query - OBIEE 11g

Hi all,
I have created a new repository with a simple star schema, and also have created ragged hierarchy. Now when i select any dimension field and a measure from the fact, the query generated by BI has 2 physical queries i.e. one for dimension and other for fact. but when it joins these 2 subqueries it does not consider any common column to join on , and results in incorrect data.
Not able to figure out what is going wrong. Pls. let me know hw to resolve this issue if any one has faced a similar one.
rgds,
Shruti

RqList <<184070>> [for database 3023:147018:DEVFRC,57] /* FETCH FIRST 1000001 ROWS ONLY */
0 as c1 [for database 3023:147018,57],
D2.c1 as c2 [for database 3023:147018,57],
D1.c1 as c3 [for database 3023:147018,57]
Child Nodes (RqJoinSpec): <<184109>> [for database 3023:147018:DEVFRC,57]
RqJoinNode <<184107>> []
RqList <<184082>> [for database 3023:147018:DEVFRC,57] distinct
sum(FCT_LEDGER_STAT.N_VALUE) as c1 [for database 3023:147018,57]
Child Nodes (RqJoinSpec): <<184085>> [for database 3023:147018:DEVFRC,57]
RqJoinNode <<184084>> []
FCT_LEDGER_STAT T147426
) as D1
RqJoinNode <<184108>> []
RqList <<184088>> [for database 3023:147018:DEVFRC,57] distinct
DIM_FINANCIAL_ELEMENT.V_FINANCIAL_ELEM_NAME as c1 [for database 3023:147018,57]
Child Nodes (RqJoinSpec): <<184099>> [for database 3023:147018:DEVFRC,57]
RqJoinNode <<184098>> []
DIM_FINANCIAL_ELEMENT T147109
) as D2
OrderBy: c2 asc NULLS LAST [for database 3023:147018,57]
=========================================================
PHYSICAL
==================================================
WITH
SAWITH0 AS (select sum(T147426.N_VALUE) as c1
from
OFSAAATOMIC.FCT_LEDGER_STAT T147426),
SAWITH1 AS (select distinct T147109.V_FINANCIAL_ELEM_NAME as c1
from
OFSAAATOMIC.DIM_FINANCIAL_ELEMENT T147109)
select D1.c1 as c1, D1.c2 as c2, D1.c3 as c3 from ( select 0 as c1,
D2.c1 as c2,
D1.c1 as c3
from
SAWITH0 D1,
SAWITH1 D2
order by c2 ) D1 where rownum <= 1000001

Join issue OBIEE (BMM Layer)

Hi All -
1. I have following tables:
D1 - Dimension Table
D2 - Dimension Table
D3 - Dimension Table
F1 - Fact Table
We have join between - D1 - F1, D2, F1 & D3 - F1
2. We have some more tables :
D4 - dimension Table
F2 - Fact Table
We have join between - D4 - F2
3. We have some more tables :
D5 - Dimension Table
F3 - Fact Table
We have join between - D5 - F3
Now the scenario is we need to enable joins between all these tables in the logical layer. i created dimensional hierarchies and assigned at the total level for the fact tables. but it is not working.
can anybody please lookinto this issue?
Thanks

I noticed that if you create the FK in the physical layer BEFORE moving the columns into the Business Model layer it will keep them when you bring them over, but if you create the columns in the BM layer then made the physical joins you have to go back and join in the BM layer.
Unfortunately if you'll lose anything in the Presentation or Business Model layer if you remove it from the BM and want to re-join.

RPD: Wrong Fact join when utilizing Level Based Measures (TOTAL Level)

I have 2 Facts and 3 Dimensions (Customer, Customer Emails, Time) being used in the RPD. The Dimensions are all set with TOTAL and DETAIL hierarchies.
Physical Layer:
Fact 1 joined to all 3 Dimensions
Fact 2 joined to all 3 Dimensions
Business Layer:
Fact 1 joined to all 3 Dimensions and Content Level set to DETAIL for all 3 Dimensions
Fact 2 joined to all 3 Dimensions and Content Level set to DETAIL for all 3 Dimensions
Metrics:
Fact 1 Metric: SUM set to TOTAL Level for Customer Emails Dimension
Fact 2 Metric: SUM set to TOTAL Level for Customer Emails Dimension
Issue:
I run a query pulling the metric from Fact 1 along with Dimension columns Email Address and Customer Name (2 Dimension Tables).
2 Physical queries are generated one against Fact 1 to get the Metric total by Customer. The 2nd query to get the Customer and Email Address that hits the Fact 2 table.
Expectation:
I would expect both queries from above to hit the SAME fact table (Fact 1). I understand the 2nd query would NOT contain the metric (Due to it set to TOTAL), but a relationship exists between the Fact 1 table and the Email Dimension, since the metric is pulled from this table I'd expect the Dimension value to be pulled from this table as well.
I look forward to any thoughts.

Merging Customer and Customer Email will not work as a Customer can have multiple Email Addresses and changes the grain of that Dimension (Customer Level).
Implicit fact would make no sense here, since each Fact has different sets of data.
The basic issue here is that we have a Customer Email table that is NOT at the grain of the Fact or even the Customer Dimension. I would have loved to snowflake off the Customer Email from the Customer Dim but then the metrics get inflated when returned and total on.
Hence we built the Email dimensions to join off the Fact and set all the metrics in each Fact (That joins to Customer) to TOTAL. So the metrics do not get inflated, the metrics repeat (Customer request) for each email per Customer.
I hope that clarifies.

BISE1 Outer Join issues

Hi, another issue I'm running in to using BISE1. I've got a simple star-schema relational model, basically copying it straight into the business layer without any adjustments.
I have a dimension (DIM_MEASURES) that I need to have outer join - i.e. on any report, I ALWAYS want to see every value of DIM_MEASURES, even if no data exists in the fact tables for some of the values.
I've gone in to the business model and changed the complex join to LEFT OUTER, RIGHT OUTER, and FULL OUTER - and I can't get ANY of these to return all rows of the dimension.
Am I doing something wrong, or is this a bug?
Thx,
Scott

Hi Scott,
My guess is that it should work that way. Maybe you can inspect your Query log file and find out which select statement is produced.
Good Luck,
Daan Bakboord

Fact to Fact join in Obiee

Hi
I am new in OBIEE, I have an scenario where in we need to join two fact tables and the condition is F1.date is between F2.valid from date & F2.valid To date
I have tried using confirm dimension. Is it possible to map such scenario in OBIEE 11g
Thanks
Sameer

Hi Venkat,
I am coming from the basics of a star schema here, so hope it helps
What is a fact?
A fact is something that has all measures which can be aggregated (Units, Dollars, # of Orders) etc with keys to different dimensions.
What is a dimension?
It is the context with which we understand/record/retrieve the measures in the fact. We understand "# of Orders" for a product/By a customer etc.
So joining a dimension and a fact helps to answer the Who/What/When kind of business questions. Ex : Who bought these products? What was the product type? When these products were sold kind of...
Now just imagine tying up fact to another fact. With this kind of model, you can never answer any business question.
I have never tried joining a fact with another fact in OBI (But do not think it will allow it though :) )
Hope I am clear.
Thank you,
Dhar

2 Dimensions and a Fact - Join Paths

I have a scenario and I have been racking my brains out as to if what I am looking for could be set up. I have two dimenisions - Region and System - each System belongs to a Region. So the System Dimenison contains a Region_Key.
I have a Fact table that contains both the Region_Key and the System_Key allowing each dimension above to be joined directly to the Fact table.
Is there any way of creating a model where I could set it up where if someone pulls a column from just the System and Region it only pulls from these two tables (The join doesn't go through the Fact Table). And when a metric is pulled that it uses the direct joins to the Fact table for each table.
I'd appreciate any feedback, thanks alot!

If I am understanding what you are saying, you are saying to duplicate the Region Dim in the Business Layer then join this newly created Logical Table off of the System Dim? So snowflaking it out. But how would that allow me to present the Region column as one column in the Presentation layer? If the user just selected the Region column and a Fact I was hoping the path would just go between that direct join. If they selected only Region and System just have it utilize the dimensional join. Thanks for your response by the way!

Ap authentication/join issue

i am having issues joining new 1242LAP's to my controller. i am receiving the follwing error on my controller:
AAA Authentication Failure for UserName:5475d01144f0 User Type: WLAN USER
username is the MAC of my new 1242LAP. older 1242LAP's have no issue. i have 70 of the newer ones that i have just installed and fail to join the controller with the above error message. i'm not sure how to resolve. any help would be appreciated. thanks.
Brandon

Hi Brandon,
Good question. Sounds like your WLC may be authorizing LAPs via an Auth-list or AAA. You can view these settings here:
Web GUI --> Secuirty --> AAA --> AP Policies
If you do not wish to authorize the APs via an auth-list or AAA, simply uncheck the following option:
Authorize MIC APs against auth-list or AAA
Cheers.
Drew

Outer Join issue in SSRS

Symptom description:
I have a Department table and an Employee table. In Department table, Deptno is the primary key. In Employee table, Empid is the primary key and Deptno is a foreign key pointing to Deptno of Department table.
Using BIDS, I have created a Data Source View (DSV) incorporating the above two tables and a relationship is also formed where Employee is the source and Department is the destination. I have then autogenerated a Report Model (.smdl) using the DSV.
Now, when I select attributes from both Department entity and Employee entity in Report Builder 3.0, the query generated by Report Builder fetches only those records from Department for which an employee exists.
My objective is to fetch all records from Department when Department is joined with Employee irrespective of whether an employee exists or not for that department. How can this be achieved?
Given below is the query generated by Report Builder:
SELECT DISTINCT
    "DEPT"."DepartmentNo" "DepartmentNo",
    "DEPT"."DepartmentDepartmentName" "DepartmentDepartmentName",
    "DEPT"."City" "City",
    "EMP"."EMPID" "EmployeeID",
    "EMP"."EMP_NAME" "EmployeeName",
    "EMP"."SALARY" "Salary"
FROM
    "CLINICOPIA_REPORTS"."EMP" "EMP"
    LEFT OUTER JOIN (
        SELECT /*+ NO_MERGE */
            "DEPT"."DEPTNO" "DepartmentNo",
            "DEPT"."DEPT_NAME" "DepartmentDepartmentName",
            "DEPT"."CITY" "City",
            "DEPT"."DEPTNO" "DEPTNO"
        FROM
            "CLINICOPIA_REPORTS"."DEPT" "DEPT"
    ) "DEPT" ON "EMP"."DEPTNO" = "DEPT"."DEPTNO"
WHERE
    CAST(1 AS NUMERIC(1,0)) = 1
ORDER BY
    "DepartmentNo", "DepartmentDepartmentName", "City", "EmployeeID", "EmployeeName", "Salary";
Environment: SharePoint 2010 serves as the Web Front-End Server and also hosts Reporting Services Add-in. SQL Server 2008 R2 SP2 is the Back-End Server hosting Sql Server Reporting Services
(SSRS) in SharePoint Integrated mode. The data is fetched in the Report Builder 3.0 reports from an Oracle database.
Environment details-
Web Front-End Server: SharePoint Server 2010 with Enterprise Client Access License features. Operating System is Microsoft Windows Server 2008 R2 Standard - 64 Bit.
Back-End Database Server: SQL Server 2008 R2 Enterprise SP2. Operating System is Microsoft Windows Server 2008 R2 Standard - 64 Bit.
Oracle Database Server: Operating System is Red Hat Enterprise Linux Server release 5 (Tikanga). Oracle Database version is Oracle Database 10g R2 Enterprise Edition Release 10.2.0.2.0 - Production.

Setting the Cardinality of Department > Employee role to OptionalOne
gives rise to cartesian join (which is a bigger issue).
Therefore, the Cardinality of Department > Employee role should remain as
OptionalMany (default).
This means, the outer join problem still remains unsolved. I have, therefore,
unmarked the above answer by me.
The question is - why has Report Builder been designed in such a way that the primary entity is always the child entity when attributes are selected from both parent and child entities?
Most people desire that all the rows of the parent entity be fetched irrespective of whether there are corresponding rows in the child entity or not. Report Builder tool should not dictate what the user wants to get, meaning it is not right to assume
that the focus of the report is Employee when attributes are selected from both Department and Employee. Report Builder should not make the child entity (i.e., Employee) as the primary entity when the user selects attributes from the child entity after
having selected attributes from the parent entity.
I am sorry to say that clients may not accept the Report Builder tool as this does not fetch the records as desired.
I hope there is someone who can suggest how the outer join problem can be solved by just tweaking the properties of the report model (SMDL).
Besides, the end users are business users and are not tech savvy. They are not expected to modify queries. They would simply drag and drop attributes from entities to create adhoc reports.

Fact Join Issue

Similar Messages

Maybe you are looking for