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

Similar Messages

  • 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

  • Querying against two fact tables with non conformed dimension

    I have two fact tables and I have this set up in RPD :
    Fact1 joined to DimA and DimB
    Fact2 joined to DimA
    On Front end I build two analysis:
    Analysis 1:
    DimA.A, Fact1.1, Fact2.2
    Analysis 2 :
    DimA.A, DimB.B, Fact1.1, Fact2.2
    In the results of Analysis 1 , I am seeing correct values for Fact2.2
    In the results of Analysis 2, I am seeing Fact2.2 as empty column. I think the reason is that Fact2 is not joined to DIMB.
    Is it possible that I should be able to report against both dimension tables (DIMA and DIMB) columns for FACT1 and FACT2 measures.... Even though I don't have join between DIMB and FACT2.
    Any response would be helpful!!!
    Regards,
    Annu

    Hi,
    Go to the LTS-- Content Level of the fact which does not have join with Dimension and put Total level for that Dimension and total level on Column(Measure also)(Double click --Levels)(Assume Dim Hierarchy is  already set up)
    Pull everything(D1,D2,F1,F2) You will see results.
    Update Me
    Thanks
    NK
    Edited by: DNK on Mar 20, 2013 1:35 PM

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

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

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

  • 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

  • Filters on non-conforming dimensions when fetching data from multiple facts

    Hi,
    I would like to confirm my understanding about how OBI fetches data from multiple facts. I have set up the BMM layer. Through Answers I am getting data from multiple facts as expected. However, is it necessary to base filters only on the conforming dimensions? If I do so, I am getting the correct data. But if I filter data on non-conforming dimensions, then I am getting more data which I am not expecting.
    Suppose, Fact1, Fact2 and Fact3 share a CommonDim dimension. If I have a filter on CommonDim, then the filter is used on the three fact tables. However, if I filter data based on Fact1's DimTwo which is not shared by Fact2 and Fact3 and I have measurements from all the fact tables, then from the SQL generated, it seems that OBI is fecting all data from Fact2 and Fact3 and data from Fact1 where DimTwo = 'SomeValue'. Then it seems to be merging the data from the three result sets.
    Is this expected, esp. a scenario where a filter is based on a non-conforming dimension (DimTwo in the example)? Have I missed anything? What do I need to do, if I want to return rows from Fact1 based on DimTwo's filter and then if there is data on Fact2 and Fact3 based on the value in CommonDim corresponding to DimTwo's filter?
    Please let me know.
    Thanks and regards,
    Manoj.
    PS.: I have got a link now which is http://obibb.wordpress.com/2010/06/06/multiple-fact-reporting-on-non-conforming-dimensions-part-ii/
    Edited by: mandix on 25-Oct-2011 12:01

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

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

  • 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

  • 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

  • Non-conforming Dimensions modelling

    Hi
    I am using BIEE version 11.1.1.6
    I am struggling to model a situation where I do have 2 fact tables F_1 & F_2 and 3 dimensions D_1, D_2, D_3
    D_3 is the only conformed dimension
    D_1 is only connected to F_1, D_2 is only connected to F_2.
    Content levels for measures in F_1 are set to Total for D_2.
    Content levels for measures in F_2 are set to Total for D_1.
    In Answers I can't create a report where I filter on one or both of the non-conformed dimensions.
    I assume it's still possible to use non-conforming dimensions in analysis
    and filter the analysis on values from the non-conforming dimension? (The part of the analysis that can be filtered by these values, measures not connected to the non-conforming dimension will of course not be filtered).
    Are there any rules to follow in 11.1.1.6 modelling non-conforming dimensions besides setting measure content level to Total for the non-conforming dimension?
    Thanks for your help
    Andy

    Hi Andy
    Please find the blogs it will resolve ur issue.
    http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
    http://www.kpipartners.com/blog/bid/83120/What-To-Do-When-OBIEE-Fact-Tables-Do-Not-Join-to-All-Dimension-Tables
    Thanks
    NK

Maybe you are looking for

  • Unable to log into Portal

    i was trying to add a new branding image to my portal yesterday by modifying an existing frame. i tried adding the theme to the default portal desk thru -->portal content -- portal users --> standard portal users. double clicked default portal deskto

  • Error writing to install cache

    For testing (of a product using the web server) purposes, I've had occassion to deinstall and reinstall the iPlanet Web Server v6.0 SP 5. I'm also using the iPlanet Directory Server v5.1 and am careful to install it before the web server. The first t

  • Problems installing opscenter 12.1.2.2161

    Hi, I have problems installing opscenter. Solaris 11.1 is used. OCDoctor.sh --check-connectivity works fine. Has anyone seen this problem? Ops Center Enterprise Controller Installer (version 12.1.2.2161 on SunOS) 1. Check for installation prerequisit

  • Airport or Time Machine

    I'm not sure what Airport does, besides it being a wi-fi router. Is it also a hardrive? What is it exactly? Same for Time Machine, is this a hardrive or a wi fi router? What is it exactly? I'm a bit confused. What I need is a good quality hardrive, w

  • CD Burning from store downloads?

    I just started using iTunes 7.2 on my 10.3.9 system and now see that I can no longer burn anything downloaded from the Music Store. Even thou the "Help" section tells me I have 7 burns for personal use, everytime I try to burn a cd I get the message