Logical Fact Column -Urgent

Hi All,
I have a measure in my production reporsitory which is working fine & giving expected results. I have one more environment which is similar to production, and in that environment the repository is pointing to Production Database.
One Measure is working fine in production but giving different values in another environment. Whereas both the environmnets are pointing to same Production database.
I have checked the calculation of the measure in both the environmnets..its matching. Also i have checked all the Physical & BMM layer joins. Its seems to be same in both the environment.
Please suggest, what else i need to check to identify the issue?
Please reply its really urgent for me.
Regards,
Ashish A.

Hi All,
I figured out the issue. One of the logical column was wrongly mapped.
Thanks anyways.
Regards,
Ashish A.

Similar Messages

  • Implementing Logical FACT & Logical dimension from 2 different data sources

    Hi Gurus,
    Here is my situation. We have 2 Different Data sources. One is SRMW and the other one is a different source. What we are trying to implement here is we wanted to create logical dimensions and logical facts as well in the BMM layer. For ex: w_day_d from SRMW and other time dimension from another source makes a logical table. And similarly a fact from SRMW and and another similar fact (Same data types though) will make a logical fact in the BMM.
    I have done the POC of it, but the only problem is that i was able to fetch the data from only one data source not the other source.
    Any suggestions ??
    Thanks in Advance.

    What I already mentioned is that you have to create multiple logical table sources and set the fragmentation content on each logical table source.
    When you have two physical tables for the product dimension, for example DIM_PRODUCT_A and DIM_PRODUCT_B, you must add them to your logical table Products as two separate logical table sources and map all columns to the corresponding logical table columns on the Column Mapping tab.
    Hereafter you should go to the Content tab of each logical table source and describe what content is in the logical table source.
    For example for the logical table source of DIM_PRODUCT_A:
    "BM"."Product"."Product Name" <= 'Product 2'
    and for the logical table source of DIM_PRODUCT_B.
    "BM"."Product"."Product Name" >= 'Product 3'
    Then you must also check "This source should be combined with other sources at this level"
    When you run a query in Answers only on the product table, two queries will be generated to get values from both tables.
    Regards,
    Stijn

  • How to determine the logical Keys of logical fact table in BMM layer?

    Hello guys
    I'd like to know more about how to know what columns of the logical fact table should be used as key in BMM layer. How OBIEE behaving differently when different keys are selected?
    In my situation, I have 1 fact table that physically joins to 20 dimensions in physical layer. Therefore, in physical layer, this fact table has about 20 foreign keys but no primary keys..
    In the logical layer, this fact table is logically joined to the same group of dimension tables. So in this case, how do I know what columns in logical fact table I should use as keys?
    Please advice
    Thanks

    thanks for the reply...
    The interesting thing I notice is that, when I start using fragmentation with the fact tables in its LTS, if not primary key is defined in the logical fact table, then I will be getting errors:
    [nQSError: 10058] A general error has occurred. [nQSError: 14023] None of the fact sources for columns are compatible with the detail filter []. (HY000)
    When I create the key by choosing random columns from the fact table as the logical key columns, this error goes way and the correct SQL is generated according to the frag..
    Because of such behavior, I'd really like to know how logical key really works in BMM layer.

  • Filter on Fact columns at report level- obiee 11g

    Hello,
    The error I am getting in my report is : Incorrectly defined logical table source (for fact table SUMM) does not contain mapping for [LEDGERFACT.CD, LEDGERFACT.YEARID].
    The Model(Physical and BMM Layer) is as follows: DIM_LF_B is joined to 2 fact tables LEDGERFACT and SUMMARY
    DIM_RPT_PARAM -> DIM_LF_B -> LEDGERFACT
    DIM_RPT_PARAM -> DIM_LF_B -> SUMMARY
    Note that the aggregation is not set for any of the Fact columns. (I am aware that all measures have to be set some aggregation type , but Client restrictions as not to edit the rpd :( )
    Now on the report front, i have pulled following columns:
    >> Col name: Description ||| Forumla: DIM_RPT_PARAM.ITEM_DESC
    >> Col name: Actual Amt ||| Formula: case when SUMMARY.MONTHID=3 and SUMMARY.YEARID=2012 then sum(SUMM.AMT_1) else 0 end
    >> Col name: Plan Amt ||| Formula: case when LEDGERFACT.YEARID=2012 and LEDGERFACT.CD=300 then sum(LEDGERFACT.AMT_1) else 0 end
    I am not able to understand as to why the BI server is throwing the error.
    I tried removing the case condition and just applying the sum(as below), and the report comes up.
    Col name: Description ||| Forumla: DIM_RPT_PARAM.ITEM_DESC
    Col name: Actual Amt ||| Formula: sum(SUMM.AMT_1)
    Col name: Plan Amt ||| Formula: sum(LEDGERFACT.AMT_1) Also for the following combination the report works
    1)
    >> Col name: Description ||| Forumla: DIM_RPT_PARAM.ITEM_DESC
    >> Col name: Actual Amt ||| Formula: sum(SUMM.AMT_1)
    >> Col name: Plan Amt ||| Formula: case when LEDGERFACT.YEARID=2012 and LEDGERFACT.CD=300 then sum(LEDGERFACT.AMT_1) else 0 end
    2)
    >> Col name: Description ||| Forumla: DIM_RPT_PARAM.ITEM_DESC
    >> Col name: Actual Amt ||| Formula: case when SUMMARY.MONTHID=3 and SUMMARY.YEARID=2012 then sum(SUMM.AMT_1) else 0 end
    >> Col name: Plan Amt ||| Formula: sum(LEDGERFACT.AMT_1)
    Any help appreciated.
    Thnks,
    Shruti
    Edited by: 970002 on Mar 28, 2013 7:18 AM

    Hi Shruthi,
    To be clear you have one table 'DIM_LF_B' and its separated out as FACT and DIM in BMM layer with respective formulas ? If yes check this http://www.varanasisaichand.com/2012/04/fact-and-dimension-from-single-source.html
    let me know if it is different
    Thanks,
    Saichand

  • How to create logical fact table in BMM layer ?

    Hello,
    I have 3 Dimension table - 2 are in one schema and last is another schema. Using this 3 dimension tables, I need to create a logical fact table.
    So, my question is whether we can create this fact table by joining these 3 dimension table which are in 2 different schema s ?
    Thanks

    Fiaz,
    you are correct. We can use tables from different subject area to create a report. However, my question was related to rpd design. Sorry, I was not very clear about the queries earlier.
    Here is the whole scenario in the physical layer of the rpd
    Table name      Databse name      Connection pool name      Schema name
    AV          AV_PXRPAM     AVAILABILITY          CRMODDEV
    OUTAGE          AV_PXRPAM     AVAILABILITY          CRMODDEV
    COMPANY          PXRPAM          PXRPAM_POOL          CRMODDEV
    AV and OUTAGE have the joins already. I want to make a join between COMPANY with OUTAGE. And then I want to include a column from each of above tables to the logical fact table in the BMM layer. then I want to do a star schema with the logical fact table to the above 3 tables in the BMM layer.
    Thanks

  • Logical fact table with fragmented data sources with different dimensions

    Hello.
    I have a logical fact table with four logical table sources. Three of the LTS's share the same dimensions, but the fourth LTS has one dimension (called Dim_A) less. In the physical layer the dimension Dim_A is joined to the first three physical fact tables, but not to the fourth fact table (since it doesn't have that dimensionality). In the BMM layer the logical fact table is joines to the logical dimansion Dim_A.
    When I run an analysis on this RPD the measures from the logical fact is aggregated correctly (union of all four table sources) as long as I doesn't include Dim_A, but as soon as I include dimension Dim_A I get the error message:
    +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: 14052] Internal Error: Logical column Dim_A.Column_X has no physical sources that can be joined to the physical fact table source [Logical table sources (Priority=0): Fact_B.Fact_Y]. (HY000)+
    I would like a solution where the analysis returns correctly aggregated measures also for the LTS with the "missing" dimension, but with a dimension value NULL for this LTS. Or something like this.
    Is there a way to set this up in the RPD.
    Thanks,
    Henning Eriksen

    The SQL could look something like this.
    SELECT dim_a.col_1, fact_a.measure_1
    FROM db.dim_a
    JOIN
    db.fact_a
    ON fact_a.col_2 = dim_a.col_2
    WHERE fact_a.date = '28-nov-2012'
    UNION ALL
    SELECT dim_a.col_1, SUM (fact_b.measure_1)
    FROM db.dim_a
    JOIN
    db.fact_b
    ON fact_b.col_2 = dim_a.col_2
    WHERE fact_b.date = '28-nov-2012'
    UNION ALL
    SELECT dim_a.col_1, SUM (fact_c.measure_1)
    FROM db.dim_a
    JOIN
    db.fact_c
    ON fact_c.col_2 = dim_a.col_2
    WHERE fact_c.date = '28-nov-2012'
    UNION ALL
    SELECT NULL, SUM (fact_d.measure_1)
    FROM    db.fact_d
    WHERE fact_d.date = '28-nov-2012'
    I would appreciate if you could give me some hints for the RPD.
    Thanks,
    Henning

  • How to prioritise obiee to select logical fact out of 2 logical fact tables

    Hi All,
    I have a scenario where in I have 2 Logical Fact tables F1 and F2 and 2 Logical Dim tables D1 and D2.
    Both Logical Dim tables are joined to F1 and F2 i.e.(D1-F1-D2) and (D1-F2-D2). When a user selects columns from D1 and D2 it always select F1.
    I would like OBIEE to select F2 instead of F1. Is this possible?
    With Regards
    Prads

    You need to mention the levels in content tab of LTSs depends on the joins to dimensions.
    It automatically picks the right LTS based on the dimensions selected in criteria & levels in the content tab of your LTSs.
    Anyways, if you want to make f2 as main LTSs put that in first position under Sources folder.

  • Foreign keys in logical fact

    Hi,
    Should I define foreign keys in logical fact table? I need to use "aggregation rule=count distinct" of the foreign key column in my reports.
    Thanks.
    Andy

    Hi Andy,
    You can add the foreign keys to your fact table as a measure column (count distinct aggregation).
    Do not use these foreign keys to create foreign key joins in the logical layer. Always use complex joins (http://obibb.wordpress.com/2010/08/06/joins-in-oracle-bi-ee/)
    Good Luck,
    Daan Bakboord
    http://obibb.wordpress.com

  • Using a Fact Column in Prompt

    Hi,
    I have requirement to use a Fact Column (Eg: Control flag) to be used in the Column Prompt. What is the best way of using it such that query performance will improve. If I use it directly it might have scan through my entire fact table which will have a performance impact.
    Is there a best way to do it?
    Thanks,
    GJ

    Hi GJ,
    The "proper" way to model this in the RPD is to add the column on to a dimension vs. leaving it on the fact table. i.e. the underlying physical fact table becomes a source for both a logical dimension and the logical fact. OBIEE smart enough to sort everything out.
    Having said that - the real performance issue could be because, in a prompt, it would have to scan a potentially huge fact table to get the distinct values of the control flag. If that's the case, then you should either 1) build a real dimension table to make it faster (this would be preferable), or 2) add a bitmap index to the control flag column on the fact table, which would also greatly improve the performance of the "select distinct control flag from fact table" query.
    Hope this helps!
    Scott

  • Implicit Fact column creating problem to the reports.

    Hi Friends,
    I have two reports from same subject area from two different facts F1 & F2.
    I have created one implicit column, as it is unable to judge from which fact it needs to build the query. So, it is genarting query from fact F1.
    I have created one logical column in the fact and marked it as Implict column in presnenation layer.( as we the process)
    But the problem is, for both the reports it is using same implicit column and it is generating the query with only one fact F1.
    It is excluding the other fact F2.
    One report it shoud use Fact1 and other report it should use Fact2.
    PLease hep me in regarding this,
    Thanks & Regards,
    Kalyan J V

    Kallu wrote:
    Hi Friends,
    I have two reports from same subject area from two different facts F1 & F2.
    I have created one implicit column, as it is unable to judge from which fact it needs to build the query. So, it is genarting query from fact F1.
    I have created one logical column in the fact and marked it as Implict column in presnenation layer.( as we the process)
    But the problem is, for both the reports it is using same implicit column and it is generating the query with only one fact F1.
    It is excluding the other fact F2.
    One report it shoud use Fact1 and other report it should use Fact2.
    PLease hep me in regarding this,
    Thanks & Regards,
    Kalyan J VFrom my understanding, implicit fact column's are set a subject area level and not dimension/fact level. So the fact table you have set for implicit fact will be used in both the reports. Why dont you just drag the second fact into the report and hide it, if you are not trying to use the fact 1 that is setup as implicit fact?

  • Logical Aggregate Column (count(distinct)) Does Not Group for SQL Server DB

    When utilizing the count(distinct column_name) aggregate function within a Logical Fact source in the Business Model and Mapping layer in the RPD file the output in BI Answers is not grouping correctly for SQL Server 2008 database sources only. All Oracle database sources represent the same aggregate column correctly within BI Answers.
    I am using OBIEE version 10.1.3.3.3
    Does anyone know how to resolve this issue?
    Thanks in advance,
    Kyle

    I thought that I would update my current findings with this issue. If you display the report in BI Answers as a Pivot Table view the aggregate column displays properly, it does not in a Table or Compound Layout view for some reason. I am still working with Oracle Support on this.

  • In Answers am seeing "Folder is Empty" for Logical Fact and Dimension Table

    Hi All,
    Am working on OBIEE Answers, on of sudden when i clicked on Logical Fact table it showed me as "folder is empty". I restarted all the services and then tried still showing same for Logical Fact and Dimension tables but am able to see all my reports in Shared Folders. I restarted the machine too but no change. Please help me out to resolve this issue.
    Thanks in Advance.
    Regards,
    Rajkumar.

    First of all, follow the forum etiquette :
    http://forums.oracle.com/forums/ann.jspa?annID=939
    React or mark as anwser the post that the user gave.
    And for your question, you must check the log for a possible corrupt catalog :
    OracleBIData_Home\web\log\sawlog0.log

  • Logical level for logical fact table sources

    it is clear that for fact aggregates, we should use the Content tab of the Logical Table Source dialog to assign the correct logical level to each dimension.
    question is : is it mandatory to assign even for non-aggregates fact tables the logical level for each dimension (which normally should be set to the most detailed level of each dimension) ? is it any known issue if "logical levels"in content tab are not set ?
    the reason I'm asking this is a strange bug I have (I'm not going to discuss it here) and then only workaround seems to be NOT setting the logical levels (on content tab) for logical fact table sources.
    thank you !

    If levels are not set: By default levels are considered as lowest level
    It should not matter if you set or not
    Generally we set for facts explicitly when we are using Aggregate tables.
    Your current issue might be a case by case; I would suggest to check implicit fact, any table mapped to the source to force a join etc
    Mark if helps
    Let me know how it helps
    Edited by: Srini VEERAVALLI on Feb 5, 2013 8:33 AM
    Any updates on this?+_
    Edited by: Srini VEERAVALLI on Feb 14, 2013 9:09 AM

  • When we should go for implicit fact column

    hi all,
    In which scenario we have to go for implicit fact column....
    let say we are having dimensions D1 and D2 and D3.. and two Facts F1and F2
    all dimensions are connected to both facts F1 and F2,
    once you drag the columns from D1 and D2... the report will come based on facts F1 and F2.... so if we want to restrict the report .. i mean report should come based one Fact table let us say
    F1 that time only we have to go for implicit fact column .....
    or any other scenarios ... are there for implicit fact column
    Thanks

    Hi ,
    have a look http://obiee.nl/?tag=dimensional-modelling&paged=2 you willl get a good idea.
    Hope this may helpful for you
    Thanks,
    Ananth

  • How to create Implicit Fact column ?and how to use it ?

    Hi all,
    How to create Implicit Fact column ?
    and how to use it ?
    Thanks in advance

    When you create a request with only dimension columns, the Oracle BI engine has to choose a fact table to join the dimensions to each other. If you have multiple fact tables in your BMM layer, the Oracle BI engine will use the most economical fact table, depending on the number of dimensions of the fact table.
    In some cases you do not want to use this fact table, but you want to force the Oracle BI engine to use the fact table you want.
    In that case you should create a fact (or select an existing fact) of the fact table you want to use for the dimension only query. In the presentation catalog of the subject area you should select this fact as the implicit fact. This fact will always be used in the query, but it won't be visible in your report. An example of an implicit fact is the count of the primary key (id) of the fact table.

Maybe you are looking for