Conforming and Non-Conforming Dimensions

Hi,
How do we identify conforming and non-conforming dimensions in our OBIEE 11g repository? There are so many of each so was wondering if there is a simple rule i can follow while browsing my repository

To identify them as you are browsing it's not really possible.
From a logical digram you could right click the dimension and select "add joins"... if it adds any facts to the diagram then obviously the dimension is conformed.
Use the Query Repository functionality in the admin tool to identify logical tables that are dimensions, and related to more than one logical table which is a fact.

Similar Messages

Filter and non-conforming dimensions

I have a model design which includes three fact tables with non-conforming dimensions. This causes BI to create multiple queries for a report and finally bring the results together using a full outer join at the end. When I attempt to filter on a field from one of the non-conforming dimensions, that filter is not applied at the full outer join step but during an earlier step related to the chosen filter field. This results in more data returning then desired. I need to move the filter to the full outer join step. Here are two sub-optimal methods that I have found to work around the issue.
1. Build the logical query in answers. Then, wrap that query with an outer query and apply the filter to the outer query.
2. Build a minus query in answers that removes the records you don't want to see.
I have seen this issue discussed in other threads, but I haven't found a good solution. Does anyone have any recommendations?
Thank you,
Edited by: user10715047 on May 21, 2010 7:13 AM
Here is a decent description of the problem
http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/two-fact-tables-and-nonconforming-dimensions-3297052
and this is a better solution than the two I stated above. However, even this solution is not going to be very intuitive for the users
http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/two-fact-tables-and-nonconforming-dimensions-3298529

i know this is a bit old thread but thought it might be helpful to someone who came across the same issue...
when using Degener@teDimen$ion ( this is !nner joned to FACT tables in BMM) and if any of the dimensions {other than theDegener@teDimen$ion (Let us say Dim X) } have an ()uter join to any of the fact tables, and you were doing your analysis using Degener@teDimen$ion, Dim X, Measure value you will face the following issues.
when filtering the analysis on the ()uter join dimension ( Dim X), the IN filter will not work. Reason is that the filter is getting applied to both the Dimension and FACT tables and the values that exist in Dimension Dim X but not in FACT table wont show up.
The above issue can be fixed by changing the join between the fact and Degener@teDimen$ion from inner to outer.
Please mark if you found this helpful.

Schedule line allocation to GR and non conformance

Hi,
1 - How can schedule lines be allocated to Good Receipts. We are looking for visibility in BW.
2 - How can we link non-conformance in a supplied item that is discovered on
receipt of goods to Purchase Order, Within SAP R/3 Procurement monitors Non-Conformance using Q2 and F2 Notification Types
Thanks,
Antoinette
[email protected]

Hi,
You can't really link the GR to the schedule line.
By flagging the "GR based IV" flag you can capture individual; receipts against the PO item but NOT against the schedule line.
It is also difficult to manage non-conformance fully in the way that you mention. The QM module provides the only real monitoring.
But both of these types of data are at a far too detailed level for BW reporting.
these types of enquiries and reports belong in R3 and not BW. If the link is not there or vague to say the least, then you have no way of being able to create a cube that would hold this data.
Steve B

Re: Working with Confirmed and Non Confirmed Dimensions

I want to make a report with columns from Lot_D, Lot_Grade_D dimensions and measures from Lot_Quantity_F and Stock_F facts, did the following steps but unable to get the required result
- two facts Stock_F and Lot_Quantity_F, Lot_D dimension is conformed whereas Lot_Grade_D is connected with Lot_Quantity_F only.
- made the joins on physical layer between Stock_F and Lot_D and than among Lot_Quantity_F, Lot_D and Lot_Grade_D.
- dragged all the four objects in BMM (now four BMM objects with relevant source in physical)
- created level-based hierarchies for Lot_D and Lot_Grade_D in BMM
- set the Stock_F measure column under Levels tab to Total level for Lot_Grade_D dimension
- set the Logical Level in the Content tab of Stock_F to Detail level for Lot_D dimension
- set the Logical Level in the Content tab of Lot_Quantity_F to Detail level for Lot_D and Lot_Grade_D dimensions
- dragged all the BMM objects in presentation layer
created the report based on flat dimensions (not Hierarchical dimensions)
Looking for a quick response
regards
Farooq

Follow The Below Steps
1) Add the Stcok_F and LOT_Q_F as LTS in BMM .
2) Join this LTS to both the dimensnons Lot_d and Lot_Grade_D
3)Open the Stock_F in LTS and go to Content tab.Set the Lot_Grade_d to total and Lot_d to Detail
4)Open the LOT_Q_F LTS and set the levels to detail.
5)Open the Individual columns coming from Stock_F and set the level for lot_grade_d to Detail.

Two FACT Tables, Some Common and Non-Common Dimensions

Hello all, a question i am sure you have faced in the past but still wanted to get your feedback.
I have a few FACT tables and some dimensions that are shared (common dimensions). Rest of the dimensions are related to one or the other FACT tables.
What is the best way to present a view where users can pull information from both the FACT tables?
I am successful in pulling the shared (common) dimensions across BOTH FACT tables having the same grain but this view breaks down when i pull information from one Dimension that has not much to do with the other FACT.
What is the best way to present this? Should this be broken in three subject areas?
Subject Area 1 --> Some Dims --> FACT Table A
Subject Area 2 --> Some Dims --> FACT Table B
AND
Subject Area 3 --> ***Only Common Dims*** --> FACT Table A & FACT Table B?
Your feedback is always appreciated.
Regards,
Edited by: user10679130 on Oct 12, 2009 3:27 PM

Please check the forum first for similar threads/questions.
Joining two fact tables with different dimensions into single logical table
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
This solution keeps both fact tables in the same subject area in the single logical fact table, with common and not-common dimensions.
Regards
Goran
http://108obiee.blogspot.com

Working with Confirmed and Non Confirmed Dimensions

The actual need for my situation is I have two facts F1 and F2 and Four Dimensions D1, D2, D3, D4
D1 is a confirmed Dimension
D2, D3 are joined to F1 and D4 to F2 according to the star schema . I need a report which has D1, D2, D3, D4 , F1. Is this possible ?
Method applied : I added a new logical table source to F1 and pointed it to F2. I pulled in all the required dimensions and created a new logical folder with F1, D1,D2,D3,d4 . I created a logical join from D4 to F1 in BMM layer . The rest of dimensions are already connected to F1.
Now when i run the report the i get null values when i pull in D4 and F1 which is logically correct but when i try to run the report D1,D2,D3,D4,F1 it returns an error ? Should i need to include even F2 in my report ?

I actually have an out of box RPD which has defined hierarchies only for certain dimensions. Is it a good practice to define hierarchies for all the dimensions ?
can't we establish the report D1,D2,D3,D4,F1 without the hierarchies ?
For the present RPD we have hierarchy defined only for D3 . Reports running on the present subject areas are working perfectly fine even without the hierarchies. Only when i am trying to span across different subject areas i get errors.
Could you throw more light on the difference it would make if i defined hierarchies for all the dimensions.

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.

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!!

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.

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...

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

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.

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

Conforming and Non-Conforming Dimensions

Similar Messages

Maybe you are looking for