Conformed dimensions

Hi,
I have two conformed dimensions across two fact tables across two subject areas. When the two dimensions are selected from subject area A and looking at the OBIEE query, the fact from subject area B is also joined. How do I avoid the join to the fact table that exist in subject area B?
Thank You,
AK

In your RPD Admin tool, go to the properties of subject area A.
On the "General" tab, set the "Implicit Fact Column" property to use fact from subject area A.
This will ensure that only the fact from subject area A is used, even if no fact columns are in the query.

Similar Messages

Using two facts of two different star schemas and conformed dimensions

Hi,
I've been working as developer and database designer for years and I'm new to Business Objects. Some people says you can not use two facts of two different star schemas in the same query because of conformed dimensions and loop problems in BO.
For example I have a CUSTOMER_SALE_fACT table containing customer_id and date_id as FK, and some other business metrics about sales. And there is another fact table CUSTOMER_CAMPAIGN_FACT which also contains customer_id and date_id as FK, and some other business metrics about customer campaigns. SO I have two stars like below:
DIM_TIME -- SALE_FACT -- DIM_CUSTOMER
DIM_TIME -- CAMPAIGN_FACT -- DIM_CUSTOMER
Business metrics are loaded into fact tables and facts can be used together along conformed dimensions . This is one of the fundamentals of the dimensional modeling. Is it really impossible to use SALE_FACT and CAMPAIGN_FACT together? If the answer is No, what is the solution?
Saying "you cannot do that because of loops" is very interesting.
Thank you..

When you join two facts together with a common dimension you have created what is called a "chasm trap" which leads to invalid results because of the way SQL is processed. The query rows are first retrieved and then aggregated. Since sales fact and campaign fact have no direct relationship, the rows coming from either side can end up as a product join.
Suppose a customer has 3 sales fact rows and 2 campaign fact rows. The result set will have six rows before any aggregation is performed. That would mean that sales measures are doubled and campaign measures are tripled.
You can report on them together, using multiple SQL passes, but you can't query them together. Does that distinction make sense?

OBIEE 11g: Non conformed dimension filter

Hi,
I have two fact tables and some confromed and non conformed dimensions between the fact tabels.
The hiearchies being built and proper levels were set for the fact tables. The measures of the fact were set to the total level of the non confromed dimension tables.
The fact also hold some non aggregated columns (baseline columns), all the base line columns where moved to a logical dim table.
The report involves both the fact tables, conformed and non conformed dimension columns.
When we built the report with all these columns the report is showing fine. But when we add the filter with the non conformed dimension the report is throwing some error.
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
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: 14023] None of the fact sources for D01 Date.Date are compatible with the detail filter [D05 Non Confrm Dimension.Code = 'AFS']. (HY000)
The above functionality was working fine with OBIEE 10g and have implemented it many times before.
There is one patch available for this issue but it is available only for windows 32 bit enironment.
Patch details
Patch 14210864: OBIEE 11G: CONFORMING DIMENSION SETTINGS FROM 10G NOT WORKING IN 11G
Can anyone give some suggestion or workaround? I can't do any change in Datamodel.
Thanks,
Vino

Hi Vinod,
In OBIEE 10g, we are running into similar error when we add filter from non conformed dimensions in a report, so can you please share patch download details like where to download or if we have to raise a SR for the Patch 14210864.
Thanks in Advance!!

Obiee 11g non-conforming dimensions and nQSError 14025

Does anyone know how to configure the 11g repository for non-conforming dimensions? This worked fine in 10g. I have upgraded the repository to 11g and it doesn't work anymore. I am receiving the error [nQSError: 14025] No fact table exists at the requested level of detail. I have tried building a simple test subject area and testing different configurations, but I have not had any success.
Edited by: user10715047 on Jan 27, 2011 12:33 PM

Ah, I love answering my own questions. :/
The only way I could make this work was a follows...
1. Make sure you have a level-based dimension for each of your logical table dimensions (both conforming and non-conforming).
2. For the fact table measures, set the levels as you did in 10g with the non-conforming dimensions at the Grand Total logical level for each measure.
3. For the fact table LTSs, set the logical level in the Content tab to the dimension's lowest level for each conforming dimension (leave the non-conforming dimensions level blank).
Unfortunately, the query generated in 11g will add an additional sub-query to the mix even though it doesn't appear to have any benefit. Therefore in 10g, if you have two logical fact tables with non-conforming dimensions, three sub-queries were required to create the result set. Two queries for the facts and their related dimensions and a final full outer join to stitch the results together. In 11g, you have one query without the measures, two queries with the measures, and the final outer join.
I am talking to Oracle support about this issue, but I haven't made much progress yet. I asked development to confirm my repository design and they say it checks out. They indicated that the additional query is a design change/enhancement. I am not getting a warm and fuzzy on this one. I'll post back if I make any progress.
Oh, did I mention that this change has broken queries where I attempt to combine fields from two non-conforming dimensions?!? This worked fine in 10g.

Non-conforming dimension filters

Hi,
Here how my join looks
FACT1>>product(dim)<< FACT2>>ledger(dim)>>RPT(dim)
Here RPT(dim) is non conforming dimension for FACT1 and product(dim) is common for both FACT1 and FACT2
I have set content level(LTS) only for conformed dim.( to detail)
When i drag fact1 and RPT(dim) ,my result is fine
but when i drag only FACT1 and use (USING filter) of RPT(dim) columns
i get error No fact table exists at the requested level of detail: [,,,,,,,,,,,,,,,,,,,,].
FYI: Re: obiee 11g non-conforming dimension filters
can i know how to set content level for nON conformed dim? will tht solve problem
Regards
Sabeer
Edited by: 944346 on Sep 20, 2012 12:54 AM
Edited by: 944346 on Sep 20, 2012 12:55 AM
Edited by: 944346 on Sep 20, 2012 12:56 AM

I resolved this issue a while ago, but I hadn't posted back the results. Here is what happened...
I talked to Oracle support about my design and issues. They created a patch for me that would re-enable the 10g functionality so that my model/queries would work again. From their perspective, 10g's non-conforming code design was flawed and 11g was fixed to correct the flaw. This flaw was what allowed my model and queries to work in 10g.
NOTE: I have not tested the patch (bug# 11850704)
The only way to get things working on 11g without the patch is to find a common fact that all dimensions can join. After some consideration and testing, I decided that it would be possible to join all the dimensions to one fact with some backend design changes. I could have proceeded with the patch, but I doubt that the 10g functionality will be maintained in the coming releases. Therefore, I would only be delaying the inevitable redesign.
I have to admit that the final results have been positive and I have eliminated many of the 10g issues that I had with the design.

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 non-conforming dimensions

Hi, I have a question re: using multiple facts in a report, where one of the facts has a non-conforming dimension.
I have two metrics: "PAYROLL" and "UNRECONCILED DIFFS". The payroll metric is at the employee level, but the "UNRECONCILED DIFFS" is not. Here's what I've done so far:
1. Set up a single logical fact table in the business layer
2. Created 2 LTSs. One has "employee" level, one has "all employees" (i.e. the grand total level)
3. Created metrics for PAYROLL and UNRECONCILED DIFFS, each pointed to the proper LTS
4. Set the "employee" hierarchy level for "UNRECONCILED DIFFS" to the "all employees" level
This is working...kind of. If I have three employees with a payroll amount of $1000, and there is a $500 unreconciled diff, the report shows up like:
Employee Payroll UnrecDiff
Emp1 $1000 $500
Emp2 $1000 $500
Emp3 $1000 $500
Total $3000 $500
Here's what I'm wondering...instead of having the unreconciled difference repeated for each employee...is there any way it can just be $0 or (even better) NULL, but then still show up as $500 in the total line?
Thanks!
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...

Drill Across Essbase/Multidimensional cubes with a conformed dimension

Hi Guys,
Does anyone have any ideas/pointers on how to implement drill across on Essbase cubes or Multidimensional sources in general.
For Eg:
Cube 1 with aggregate data at Country Level
Cube 2 with detail data at City Level
Geography is the conformed dimension here.
I need to implement drill across from the Country level in the Geography Hierarchy to go to the City level, across cubes. Facing a problem desinging it in the BMM.
Any help would be appreciated.
thanks,
jboy

We're discussing this already in your other thread? Different drill paths for a common Essbase Dimension with varied depth
Close this one please...not necessary.
Cheers,
C.

Non-conformed dimension [nQSError: 14020]

Hi,
I have linked two cubes in a report, which have some conformed and some non-conformed dimensions. I have set the LTS of the non-conformed dimensions to the total level.
This creates a warning in Administrator when doing the Global Consistency check:
*[39054] Fact table "ORACLE_BUSINESS_INTELLIGENCE_1"."CubeXXX" is not joined to logical dimension table "ORACLE_BUSINESS_INTELLIGENCE_1"."DIM_XXX". This will cause problems when extracting project(s).*
What does 'extracting projects' mean here ???
And when I run a report on the two fact tables I get an error in the logs
*...converted to NULL because [nQSError: 14020] None of the fact tables are compatible with the query request*
Am I missing something or is this related to the rumor that non-conformed dimensions are broken in 11.1.1.3 ?
Regards,
Knut

Below is some useful and related information from oracle about OBIEE 11g warnings during consistency check:
Warning: [39055] Fact table "HR"."FACT - HC Budget" is not joined to tables in logical dimension "HR"."DIM - HR EmployeeDim". This will cause problems when extracting project(s).
Description: Even though this fact logical table source has an aggregate grain set in this dimension, no valid physical join was found that connects to any logical table source in this dimension.
This means that either no join exists at all, or it does exist but is invalid because it connects a higher-level fact source to a lower-level dimensional source. Such joins are invalid and ignored by the Oracle BI Server because, if followed, they would lead to double counting in query answers.
For example, consider Select year, yearlySales. Even if a join exists between monthTable and yearlySales table on yearId, it cannot be used because such a join would overstate the results by a factor of 12 (the number of months in each year).
All three of the given validation rules are related to the same issue.
Please read through the above text to see if it will help with your issue.
Thanks,
-Amith.l

Conformed dimension and query multiple fact tables

Hello,
Please if someone can guide me on this requirement.
Requirement - I have a conformed dimension D1 and two fact tables F1 and F2. Both fact tables have many columns so I cannot merge
the two fact tables into one logical table. Currently both these fact tables have logical tables F1 and F2 respectively.
As per design the conformed dimension is a simple logical table in the rpd and not a dimension.
Can someone guide me how should i proceed so that i'll be able to fetch information from both the fact tables?
Edited by: 930542 on Apr 26, 2012 12:28 PM

Hi,
Currently the dimension table is taken as a simple logical table in rpd as it does not have have any levels or hierarchy.
Its a flat dimension. Can you guide me how can I implement a flat dimension in OBIEE? Because this dimension is taken as simple logical table
I am not able to set appropriate level for fac tables. This dimension does not appear in the list of dimensions.

Modelling 2 Fact Tables with Non-Conforming Dimension in OBIEE 11g

Hi all,
I have two fact tables (Fact 1 and Fact 2) and two dimension tables (Product and Rule). The Product dimension table is a conforming dimension and is used in both fact tables, but the Rule dimension is a non-conforming dimension which is used only one fact table. I'm using OBIEE 11g (11.1.1.6.0).
====
Fact 1
====
Sales ID | Product ID | Quantity | Sales Description | Sales Status
S001 | P001 | 100 | bla bla bla bla bla | N
S001 | P002 | 200 | bla bla bla bla bla | N
S002 | P001 | 200 | lab lab lab lab lab | Y
S002 | P003 | 250 | lab lab lab lab lab | Y
Notes for Fact 1:
- One Sales ID can have multiple Product IDs
- Sales Description and Sales Status are the same for one Sales ID (repeating Sales Description and Sales Status for the same Sales ID)
====
Fact 2
====
Sales ID | Product ID | Rule ID | Score
S001 | P001 | R001 | 2
S001 | P001 | R002 | 3
S001 | P002 | R003 | 1
S002 | P001 | R003 | 1
S002 | P003 | R002 | 2
S002 | P003 | R004 | 5
Notes for Fact 2:
- One combination of Sales ID and Product ID can have multiple Rule ID
I'm wondering how best to model these tables so that I can create this report (number of the dimension and fact tables created in the business model, level mapping, aggregation rule, etc)? Any suggestion/advice on how to achieve this?
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
S001 | P001 | 100 | bla bla bla bla bla | N | R001 | 2
S001 | P001 | 100 | bla bla bla bla bla | N | R002 | 3
S001 | P002 | 200 | bla bla bla bla bla | N | R003 | 1
S002 | P001 | 200 | lab lab lab lab lab | Y | R003 | 1
S002 | P003 | 250 | lab lab lab lab lab | Y | R002 | 2
S002 | P003 | 250 | lab lab lab lab lab | Y | R004 | 5
Thank you very much!

Hi Dhar, thanks for the suggestions.
I tested what you suggested, but the result is not as per my expectation mentioned above. Here's what I did:
1. In physical layer:
- I joined Fact 1 table with Product dimension table only
- I joined Fact 2 table with Product and Rule dimension tables
2. In business model layer:
- I created 3 logical tables: Fact, Product, and Rule
- The Product table contains the Product ID and Product Name from the Product dimension table in the physical layer
- I created the hierarchy (logical dimension) for Product with only ProductTotal level (as the grand total level) and ProductDetail level that contains Product ID and Product Name
- The Rule table contains the Rule ID and Rule Name from the Rule dimension table in the physical layer
- I created the hierarchy (logical dimension) for Rule with only RuleTotal level (as the grand total level) and RuleDetail level that contains Rule ID and Rule Name
- The Fact table contains 2 logical tables sources: Fact 1 (which logical level in the Content tab is mapped to ProductDetail and RuleTotal) and Fact 2 (which logical level in the Content tab is mapped to ProductDetail and RuleDetail)
- The Fact table contains Sales ID logical column (mapped to both Fact 1 and Fact 2 logical table sources)
- The Fact table also contains Sales Description and Sales Status logical columns (mapped to only Fact 1), which aggregation rule is the default to None
- The Fact table also contains Quantity logical column (mapped to only Fact 1), which aggregation rule is set to Sum
- The Fact table also contains Score logical column (mapped to only Fact 2), which aggregation rule is set to Sum
OBIEE returns the expected result when I retrieve the report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status
However, OBIEE returns an error when I retrieve the reports:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID
or
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
The error is:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
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 FACT.SALES_STATUS. (HY000)
And the Score column is blank when I retrieved this report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Score
Any suggestion anyone? Please help. Thanks a lot!
Edited by: stewartlife on Nov 29, 2012 4:01 PM

Report on non conformed dimension

Hi All,
I am using OBIEE 11.1.1.5
We have 2 facts and 4 dimensions out of which only 1 dimension is conformed. We have a report requirement of using the conformed dimension and filtering based on 2 non conformed dimensions and include the measure from both the facts. When the report is created it is throwing error as
"None of the fact tables are compatible with the query request"
for eg : Let say
F1 --> d1,d2
F2 --> d1,d3,d4
the report has d1.c1,d2.c2,d3.c3,F1.M1,F2.M2 and filter by d2.c2 and d3.c3
Thanks in advance.

Check out patch (bug# 11850704)
Also have you set the level for the non conforming dimension at the highest level of granularity

Again: two facts and one conformed dimension

Dear all,
I know this has been asked quite often but I haven't found a solution for my problem here. Believe me I have done a lot of searching across the net ..
What I want to do is the following:
I have two fact tables with a number of common dimensions. A report should show the two facts across these common dimensions.
To keep it simple I start with only one common dimension.
Here's what get's to the db from OBIEE:
*SELECT Revenue."Date (YYYYMMDD)" saw_0, Sales."Day Day Code" saw_1, Revenue."TPV (Total Payment Volume in Millicent [€])" saw_2, Sales.DEBIT_AMOUNT saw_3 FROM "Company KPIs" ORDER BY saw_0, saw_1, saw_3*
Note that *Revenue."Date (YYYYMMDD)"* and *Sales."Day Day Code"* are the same field from the common time dimension. I just put them in different presentation tables for the end users.
TPV and DEBIT_AMOUNT are facts from the two different cubes.
Everything fine, right?
Now I look at the nqquery.log:
RqList
Dim Time.Day Day Code as c1 GB,
Dim Time.Day Day Code as c2 GB,
*Tpv:[DAggr(Cube Revenue.Tpv by [ Dim Time.Day Day Code, Dim Time.Day Id, CUBE_SALES.DEBIT_AMOUNT] )] as c3 GB,*
CUBE_SALES.DEBIT_AMOUNT as c4 GB,
Dim Time.Day Id as c5 GB
OrderBy: c1 asc, c2 asc, c4 asc
now the bold thing looks odd to me. Is he trying to aggregate one cube based on the other? Could be the problem, but where to influence this?
And finally this translates into this query:
WITH
SAWITH0 AS (select distinct T4110.DEBIT_AMOUNT as c1,
T281.DAY_DAY_CODE as c2,
T281.DAY_ID as c3
from
DIM_TIME T281,
CUBE_SALES T4110
where ( T281.DIMENSION_KEY = T4110.DIM_TIME ) ),
SAWITH1 AS (select distinct SAWITH0.c2 as c1,
SAWITH0.c2 as c2,
*cast(NULL as DOUBLE PRECISION ) as c3,*
SAWITH0.c1 as c4,
SAWITH0.c3 as c5
from
SAWITH0)
select SAWITH1.c1 as c1,
SAWITH1.c2 as c2,
SAWITH1.c3 as c3,
SAWITH1.c4 as c4
from
SAWITH1
order by c1, c2, c4
As you see, the tpy ist gone and a NULL appears. That's what I see in the report. TPV is always NULL.
So where did I miss a configuration ???
Thanks, Knut

You only need to set the content levels on the measures themselves when you want non-conformed dimensions in the report, as your working with fully conformed dims just make sure your levels are set on the content tab for each Logical Table source in the Logical fact table. Leave the non-conformed dim hierarchies as blank.
Remember - You should put a hierarchy on each logical dim , even if there is no real hierarchy, just have a total -> Detail.
You should always always always set your content levels for logical table sources, both in Dimensions and Logical fact LTS's.
If they are greyed out, make sure your not in read only, have checked the object out if on-line mode, failing that, perform the changes off-line then re-start your BI Server.

Single Fact with Multiple Conformed Dimensions

Hi,
I have a fairly simple report:
Dim A and Dim B are joined with Fact 1
Now, I want all rows from Dim A and Dim B along with Fact 1 values. If there are no matching values of Dim A and Dim B in Fact 1, I should get NULL or some message "No Data Available".
If I make left outer join from Dim A to Fact 1 and Dim B to Fact 1 (to consider all rows from dimension tables), I dont get matching records. Because Fact 1 may not have all records for Dim A or Dim B.
I dont want to make Full outer joins between Dim A and Fact 1 and DIme B and Fact 2. Do I have any other solution?

Hi,
ok let's assume,
I have something like voucher used flag in one fact table, this is not a measure, it's a degenerated dimension entry.
What to do with this one? My model is at the moment clear, we have managed to have 15 facts and 10 conformed dimensions, without issues.
Now they want to analyze over this flag "voucher used" in best case over all facts and dimension combinations.
This is the main requirement
regards,

OBIEE Conformed dimension with Bridge Table

Hi,
I have an issue and tried all the links from Mark and Gerad regarding bridge tables. But probably this is a bit different.
I have to extend the OOB data model for OBIA - where the relationship between group account and gl account dimensions are 1 to many. In my case its many to many and hence bridge table.As this is not a standard customization, so posting this thread here.
Although its out of the box, a short description of the scenario.
Account Dimension levels -
total --->Group account---->Gl account
The logical table has two LTS - GL account and Group account forming a conformed dimension using column mapping.
Earlier(OOB) there was no join the physical layer between these tables ,as I had to use the Bridge table , so I joined these two with the bridge table in physical layer.
But the problem is, if I try to use standard technique to include the bridge table into the LTS of the group account table (i.e. Group account---->bridge<-------Gl account),
there is a problem of over counting ,as the group account level is also connected to summary fact tables - the query will include the bridge table and hence over count.
So my requirement is this -
When only Group account is selected it will hit the summary fact tables (content level is already set in OOB), but it shouldn't use the bridge table - so no overcount.
If we drill from Group account level or when Both Group account and Gl account is selected, it would use the bridge table and hit the detail fact table (content level is already set in OOB).
I am using OBIA 7963 with OBIEE11g.
This is the model - Summary facts <-------Group account ------>Bridge<-------Gl account-------->Detail Facts
Please help.
Regards,
Krish
Edited by: Krish on Aug 7, 2011 9:48 AM
Edited by: Krish on Aug 7, 2011 9:50 AM

Anybody please any i/p?

Non-Conforming Dimension Model Question 14020

Guys
I have two fact tables combined into a single Logical Fact Table. There is a single conformed dimension for both fact tables, and each fact also has its own non-conformed dimension.
So effectively I have:
D1---<F1>---D2---<F2>---D3
but (F1) and (F2) are combined into single Logical table.
I have set the logical levels for the measures F1 to be Total (D3) and the measures F2 to be Total (D1).
If I select D1, D3 and F1/F2 measures then all works well. If I remove one or both of the measures I then get the dreaded 14020 error. I have tried setting the implicit fact measure for the Presentation Folder but this has no effect.
Is it possible with my current setup to select from the Dimension tables without selecting measures?
Thanks in advance

Hello Matt,
Please follow the below link
http://obiee-blog.info/administration-tool/importance-of-defining-dimensional-hierarchies/
Is this helpful to you.
Thanks

Conformed dimensions

Similar Messages

Maybe you are looking for