How to do join in BMM layer.

Hi Guys,
i am using Argus safety application for analytics. i need some help. here i am explaining my scenario.
CASE_MASTER is my main fact table.
Dim_Prefferd_Term (1)-------------(M) Map_PrefferedTerm_CaseId (M)----------------- (1) Case_master (1)-------------- (M) map_caseId_drugs (M) ---------- (1) Dim Drugs
can anybody suggest how to do complex join in BMM Layer.
Thanks In Adavance.
Edited by: 811469 on Apr 20, 2011 9:02 PM

Thanks!!
I think I made some mistake in configration file.
When I regeneted files by MyEclipse Reverse Engineering
I was able to do that.

Similar Messages

  • Left Outer Join in BMM layer

    Hi All,
    while building the RPD we have to use the join as Left outer join for two tables , we added join condition in BMM layer like evey table we have three tabs like General,Column Maooing and Content.
    In General tab we have to sections like map to these tabls and Joins right. In the Join Scetion we add join conditions for two tables as left outer join.
    Now i need to move the first table as second table and wise versa , how i can?? move these two tables
    Thanks for your help.

    Hi User,
    You will have to remove and add the table as there is no option to reorder the tables.
    Rgds,
    Dpka

  • Circular Join in BMM Layer

    Hi,
    There are few dimension tables in my BMM Layer which is joined to every other table. I get circular joins error at this point. I tried duplicating the logical tables and avoided the circular schema. It always showed my an error.
    Please guide me.
    Thanks in Advance
    Edited by: 914981 on Feb 16, 2012 5:43 AM

    Hi,
    Eliminate all circular joins (intra-dimensional circular joins) in a logical table source in the Physical Model by creating physical table aliases.
    For example, say you have a Customer table that can be used to look up
    ship-to addresses, and using a different join, to look up bill-to addresses.
    Avoid the circular joins by aliasing the table in the Physical layer so that there is one instance for each purpose, with separate joins.
    If its the same dimension table, make an alias on the dim for each different join you want to use and model them as seperate logical tables in the BMM.
    Also refer thread for good understanding:
    Re: Obiee - physical layer
    Regards,
    MuRam

  • How to define join in physical layer between cube and relational table

    Hi
    I have a aggregated data in essbase cube. I want to supplement the information in the cube with data from relational source.
    I read article http://community.altiusconsulting.com/blogs/altiustechblog/archive/2008/10/24/are-essbase-and-oracle-bi-enterprise-edition-obiee-a-match-made-in-heaven.aspx which describes how to do it.
    From this article I gather that I have to define a complex join between the cube imported from essbase to my relational table in physical layer.
    But when I use Join Manager I am only able to define jooin between tables from relation source but not with the imported cube.
    In My case I am trying to join risk dimension in the cube based on risk_type_code (Gen3 member) with risk_type_code in relation table dt_risk_type.
    How can I create this join?
    Regards
    Dhwaj

    Hi
    This has worked the BI server has joined the member from the oracle database to cube. So Now for risk type id defined in the cube I can view the risk type code and risk type name from the relational db.
    But now if I want to find aggregated risk amount against a risk type id it brings back nothing. If I remove the join in the logical model then I get correct values. Is there a way by which I can combine phsical cube with relational model and still get the aggregated values in the cube?
    I have changed the column risk amount to be sum in place of aggr_external both in logical and phsical model.
    Regards,
    Dhwaj

  • Why do we need to Join in the BMM Layer

    Hi,
    Somebody asked me the following questions
    *"If the joins are already defined in the Physical Layer and ultimately the query will pass thru Physical Layer to the Database and will take the joins defined in the Physical Layer then why do the joins in the BMM layer". This can be a Complex join or a Foriegn Key Join*
    Under what conditions do we use Foreign Key Joins in BMM layer ?
    How do we use Stored Procedure in OBIEE?
    Any answers.
    Rgds,
    Amit
    Edited by: amitsharma73 on May 20, 2010 5:51 PM
    Edited by: amitsharma73 on May 20, 2010 5:52 PM
    Edited by: amitsharma73 on May 20, 2010 5:52 PM
    Edited by: amitsharma73 on May 20, 2010 5:53 PM

    This is most likely because the copy's licence has not been verified, and to verify it you need to log in so it can check that you account contains the license.
    It's just to prevent torrenting and piracy.

  • Use of complex join in BMM and Physical Join in Physical layer ?

    Hi All ,
    Why we need to use complex join in BMM layer not the Physical Join ?
    Why we need to use Physical Join in Physical layer not Complex join ?
    thanks in advance

    Hi,
    A physical join is at the physical layer and defines the join between two physical tables.
    Logical joins live at the BMM (logical) layer and define a join between two logical tables.
    The important differentiation is that at the BMM layer you do not tell the OBIEE server how to do the join,
    you just tell it that there is a relationship between these two logical entities.
    when the server comes to this logical join it will use the information in the physical joins and decides how the two logical tables are joined together.
    thanks,
    pramod.

  • Arranging Hierarchy tables in BMM layer

    Hi
    I have a different structure of dimensions in the database.
    Year->Season->Quarter->Month->Week
    For every level in Hierarchy I have table i.e, Dim_Year, Dim_Season, Dim_Quarter, Dim_Month, DIm_Week
    They are joined in physical layer in as per the hierarchy thats is Dim_Year is joined to DIm_Season by Year_id, Dim_Season is joined to Dim_Qaurter by Season id and so on.
    In BMM layer I have to craete an Hierrarchy.
    How should i keep these tables
    Option1: Pull the all the tables separately
    Create comples join between all the dim tables year->Season->Quarter->Month->Week
    Create hierarchy from these tables
    Option2:
    Create a logical tables as Time
    Pull all the tables into Time table with different Logical table sources.
    Then create a hierarchy from these tables.
    This will avoid the comples join in BMM layer
    Please suggest which option will lead to less performance issue and which is ideal approach in such scenarios.
    Thanks in Advance

    Hi,
    I am new to OBIEE but still I am suggesting one option....
    Drag and drop any one of the Time table (for ex Dim_Year) from physical layer to bmm layer. create a complex join of this table with the other tables in the bmm layer. then simply drag and drop the columns from other tables (Dim_Season, Dim_Quarter, Dim_Month, DIm_Week) from the physical layer one by one on the LTS of Dim_Year.
    Hope I haven't given you a funny answer.
    Edited by: user9149257 on Mar 8, 2010 9:20 PM

  • Display of yellow colour icon to a table in BMM layer

    Hello all,
    Please ignore my previous thread. By mistake it went without any description of problem. Sorry for that.
    I have two tables org details, emp details
    org details having columns like orgname, year, quarter1 results, quarter 2,quarter 3, quarter 4
    emp details having columns like org, year, emp in quarter1, quarter2,quarter 3, quarter 4.
    Spread sheet as datasource and imported to physical layer....when i drag drop to BMM layer...emp details table icon showing yellow.
    But it's not a fact table...those two are normal tables....why is it showing yellow colour icon?
    please let me know the concept of how OBI administrator tool decides that the table is fact table or dimension table.
    regards
    chandra kanth.

    By default OBIEE will show yellow colour.Once you create joins in BMM layer then it will show colours accordingly.Table on n side in 1:n join will be shown as yellow(Fact).So create joins in BMM layer.
    Regards,
    Sandeep

  • Tables icon displaying yellow in BMM layer.

    Hi all,
    When i was tring to drag drop tables from physical layer to BMM layer it's showing yellow icons.....
    Scenario is as follows:
    tables: EMP, DEPT, BONUS, SALGRADE.
    I have created complex join in Physical layer between EMP and SALGRADE (condition is "EMP$".SAL BETWEEN "SALGRADE$".LOSAL AND "SALGRADE$".HISAL). Samething i have taken into BMM layer. 4 table icons showing yellow and checked for consistency..giving errors like there is no join of logical tables.
    i have created join Physical layer will it not carry to BMM layer? Do i need to create same complex join in BMM layer? After creating the complex in BMM layer will those errors come again??
    Please aswer to my questions..asap.
    regards
    ck

    Chandra kanth wrote:
    Gurus,
    The other two tables (DEPT, BONUS) are not required to join but i just kept it like that in BMM layer.
    1. I have created complex join between EMP and SALGRADE in physical layer and i also manually created complex join in BMM layer....it did not come when i drag drop the schema from physical to BMM layer. Do we require to create manually again the complex join in BMM layer?Yes.
    >
    2. After creating complex join in BMM layer EMP table icon shows white others are yellow. Will complex join not suffice to make error free (Consistent) in BMM layer?
    Is it require to join all tables (to maintain a star schema)?
    You need to create complex joins to create a star schema in BMM layer. This is needed to create an error free BMM layer.
    3. As per the requirement i dont require to join other two tables (DEPT, BONUS).
    What is the purpose of these tables?
    >
    Please advice if i am wrong in the above cases....and also please answer to all my questions.
    Thanks in advance
    chandra kanth.

  • Can we create a multiple joins in physical layer

    Hi,
    I have a requirement that i want to create a multiple joins in physical layer.
    Ex:
    Table a (custid,name,sal) and tableb (custid,ced_id, loc)
    i had requirement that cust id is joining with custid and cedid from table b
    i.e a.custid=b.custid AND
    a.custid=b.ced_id (Note data types are same across all the joins here).
    When am trying to handle it form physical joins, getting an issue that The column'cusid' is used twice.
    Regards,
    Malli

    As Daan said use complex join in physical layer that should work. Just in case its not working then go with 1 join condition physical layer and create foreign key join in BMM layer, this would override join in physical layer.

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

  • Please Help in Joins and content tab (BMM Layer).

    Hi all,
    I am a newbie in OBIEE. I am working on a project in our organisation for existing database schema in oracle. We are planning to use OBIEE for reporting purpose.
    Here's my problem.......
    I have Three dimensions and Two Fact tables in my schema.
    out of these one dimension is conformed Dimension.
    Product_Reporting_Line, Geography, Policy_Cover_Type are Dimensions and ClaimFact,*PolicyFact* are facts.
    Product_Reporting_Line is joined to Claim Fact and Policy_Cover_Type is joined to PolicyFact..
    Geography is joined to both Claim Fact and PolicyFact.
    Here's how it looks.....
    Product_Reporting_Line-----< Claim Fact >-------Geography--------< PolicyFact >-------Policy_Cover_Type
    I have a report in which columns from all the tables have to be taken.
    In the Fact tables F1 and F2, there are some columns for which aggregation rule is not set (varchar Data for example Claim Number from ClaimFact and Policy Number from PolicyFact).
    How should I design BMM layer. I want to know how the content tabs should be set.
    Can anybody suggest me how should I do this?
    Edited by: LavaRider on Jul 12, 2010 6:12 AM

    Hi Kart,
    I didn't do it the other way, I did it the the way you suggested me..
    I have set the content for the Policy_Fact LTS to the Total level of Product_Reporting_Line dimension.
    also I have set the* content* for the ClaimFact LTS to the total level of Policy_Cover_Type.
    When I set the level *(Level tab of logical columns properties)* of Measues to the total level then it works....
    i.e.
    I have set the levels of the logical columns of Policy Fact table to the total level of Product_Reporting_Line and also set the levels of the logical columns of Claim_Fact to the Total level of Policy_Cover_Type.
    I want to ask you Do we have to set the content in the LTS as well as in the Level (tab) of the measures?
    Thanks for giving your precious time for me, I really appreciate that

  • How should I deal with it in the BMM Layer

    Hi all,
    I need a suggestion in a problem.
    Here is the scenario,
    In the physical layer, There are some fact to fact joins.
    ProductFact ----< PolicyFact ----< PolicyCoverFact ----< ClaimFact ----< ClaimPaymentFact ----< CorrespondenceFact
    There are some conformed dimension tables given below
    Geography is joined to ProductFact, ClaimFact
    Organisation is joined to PolicyCoverFact, CorrespondenceFact
    Currency is joined to PolicyFact, ClaimPaymentFact
    Also there are non-conformed dimensions such as,
    ProductType is joined to ProductFact
    PolicyCoverType is joined to PolicyCoverFact
    and there are many more......What I know is when there are fact to fact joins, we should make a logical table in the BMM layer and add both fact tables to the same LTS, But in this case, almost all the fact tables are joined directly.
    How should I deal with these fact to fact joins in the BMM layer? Any suggestions?
    Edited by: LavaRider on Aug 25, 2010 2:47 AM

    LavaRider wrote:
    I have to create many LTS for the fact table......
    1 LTS for ProductFact
    1 LTS for ProductFact & PolicyFact (which contain ProductFact and PolicyFact as sources)
    1 LTS for ProductFact , PolicyFact & PolicyCoverFact ........
    and so on.....
    have I understood correctly? Is that what you mean?Yes, the reason why I said to "keep" the firsts fact table in each source is to make the dimension work.
    For example, if the "product dimension" is only linked to "product fact", but not "policy fact" then you won't be able to do a report based on "product dimension" and "policy fact". Right ? To be able to do this report, OBIEE must do a join with "product fact" (this fact table become an intersection table). That's why you will add product fact in the "policy fact" source. Same for others source.
    But the name of "ProductFact & PolicyFact" source can be "policy fact". Because each row of this source is a policy fact.
    For the 3rd table, each row is a "policy cover fact". But to be able to join with "product dimension" and "policy dimension", you need to integrate "policy fact" and "product fact" tables in the logical source.
    and so on.

  • How do I Join Fact to Fact in the BMM

    I have a star schema in the BMM layer. Another star schema is also modelled. Now the fact table of star schema 1 has to get data from the dimension table in star schema 2.
    How do I join the fact tables of star schema 1 and star schema 2.
    They do not share a common dimension.
    Thanks for inputs.

    Just click inside the Shape and either type or paste.
    or
    select a Textbox and Shape by clicking on each with the command key held down > Menu > Arrange > Group
    Peter

  • 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

Maybe you are looking for