Cardinality in physical and bmm layer.

Hi,
Is it not possible to define cardinality in physical layer. Do we do this only in BMM? Even in BMM why do we do it when it looks for 1:n between tables? Can anyone please expalin this cardinality in both layers?

I think your reading into it too much, think of the physical layer as merely your joins, no cardinality specified here.
in the BMM its a MUST to have a true logical starschema, you can have the same table as a source to a dimension and a fact in the BMM if you wish, as its a true star it will always be 1:N in here from your dims to facts. OLTP and snowflake sources are resolved by adding multiple tables into the Logical Table Sources (edit LTS and choose Add - you will see only tables connected to each other here).
The BI Server knows which physical tables serve logical dimensions and which serve logical facts in the physical layer based on the Logical table sources and model in the BMM layer.
can you tell us why your asking , or what your trying to achieve that your unsure about ? We can help you then.
Cheers
Alastair

Similar Messages

  • Diffence between physical layer and BMM layer

    Hi all,
    Please let me know the difference between Physical layer design and BMM layer design. Please write your views in your reply instead of links.
    regards
    chandra kanth.

    chandra kanth.,
    Use in the layers
    The physical layer is the layer of the Logical Business Model where you define the physical data model of your data source. It contains information about the physical data sources.
    The most common way to create the schema in the Physical layer is by importing metadata (table, view, …) from databases and other data sources. If you import metadata, many of the properties are configured automatically based on the information gathered during the import process. You can also define other attributes of the physical data source, such as join relationships, that might not exist in the data source metadata.
    In the Business Model
    In the business model, OBI recommends using complex logical joins instead of foreign key logical joins.
    When Complex joins are used in the business layer then they are really acting as placeholders. They allow the OBI Server to decide on which are the best joins define in the Physical Layer to satisfy the request.
    In a Dimension, you may have multiple Logical Table sources that all join to one fact table. The OBI Server will then decide the best joins to use to meet the requirements.

  • Sum Aggregation Error in Physical & BMM Layer in OBIEE 11g with Essbase 11

    Hi everyone,
    I'm using OBIEE 11g with Essbase 11 as the data source. I'm using Sample Basic database from the Essbase as my data source. If I'm using the hierarchy for the measures (so I don't flatten the measures), and when I changed the aggregation in both physical and BMM layer from Aggregate_External to Sum, I can't create a report at all from the Answers.
    Does anyone encounter the same thing? Any ideas/solution about this? Please help.
    Thanks a lot!

    Hi Deepak,
    When I picked the "Basic - measure" alone, I got this error.
    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: 96002] Essbase Error: Unknown Member Basic - measure used in query (HY000)
    SQL Issued: SELECT 0 s_0, "Sample Basic"."Basic"."Basic - measure" s_1 FROM "Sample Basic".
    When I picked the "Gen1,Measures" alone from the measure dimension, I got this error:
    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: 46008] Internal error: File server\Query\Optimizer\ServiceInterfaceMgr\SIMDB\Src\SQOIMDXGeneratorGeneric.cpp, line 2610. (HY000)
    SQL Issued: SELECT 0 s_0, "Sample Basic"."Measures"."Gen1,Measures" s_1, SORTKEY("Sample Basic"."Measures"."Gen1,Measures") s_2 FROM "Sample Basic"
    But when I queried the dimensions one by one (only single dimension each), no error was shown.
    This only happens if I use Sum in the physical and BMM layer. If I use External_Aggregation, these errors do not happen. And if I flatten the measures, these errors also do not happen.

  • BMM layer creation (Star Schema Physical Layer) - What to add/not add?

    Hi All,
    I am just looking for any general feedback on the thought/question below.
    I am setting out on creating my first BMM layer and trying to determine what I need to do in this layer that will be different and add value from what I already did in the physical layer. My data model is already defined as a star schema within my data mart source. So in the physical layer I have my facts imported along with the dimensions and I have joined them together as needed. Here is what I think I will setup as I move into the BMM layer:
    1. I will add heirarchies as needed to enable drill down within my reports
    2. I will need to add my calculations/measures to allow for any type of metric to be returned through a request in Answers
    3. I do not see a large need to create logical tables (at least not yet) based on multiple physical source tables as my source is already a star schema and dimensionally modeled. For users that also already source a star schema at the physical layer .. do you find that you do a lot of logical table creation/mapping to add functionality or does your BMM look a lot like you Physical Layer?
    Other than steps 1 and 2, I am not really sure how much additional manipulation I might do from the Physical to BMM layer since my Physical is already a star schema. Am I missing anything? Obviously everyone's data model and circumstances are different but I wasn't sure if maybe there were some good thoughts on what I might be missing (if anything)?
    One last question .. I am not currently planning to use any aliases at the Physical Layer but I do plan to rename the tables at the presentation layer to be more business verbage like. Why are others using aliases?
    Thanks in advance for the help.
    K

    Alastair, thanks for the advice. I'll definitely keep that in mind as I start to build out the BMM.
    One question/issue I just ran into as I was wrapping up my Physical Layer mapping. When I check for global consistency, I am getting an error that is complaining that I have multiple joins defined between the same two tables (which I do). This is because I have the following setup:
    TBL_A_FACT
    F_ID_HIT
    F_HIT_DESC
    F_ID_MISSED
    F_MISSED_DESC
    TBL_B_DIM
    F_ID
    F_DESC
    Table A joins to Table B in two ways:
    TBL_A_FACT.F_ID_HIT = TBL_B_DIM.F_ID
    TBL_A._FACT.F_ID_MISSED = TBL_B_DIM.F_ID
    The F_IDs can be either hit or missed on any given fact record and the total distinct set exist in the dimension.
    When I define two foreign key joins in the physical layer based on the relationship above and check Global Consistency, I get an error saying that "TBL_A and TBL_B have multiple joins define. Delete duplicate foreign keys if they exist" and it is listed as an error. I guess this makes sense because when the two tables are used in a request OBIEE would need to know how to join them (using the hit or missed field). What is the best approach for handling this..
    - Should I define TBL_A twice in the physical layer as:
    TBL_A (Alias TBL_A_HIT)
    F_ID_HIT
    F_ID_HIT_DESC
    TBL_A (Alias TBL_A_MISSED)
    F_ID_MISSED
    F_ID_MISSED_DESC
    Or do something like the above in the BMM layer?
    Thanks for the help!
    K
    And then establish the relationships using these separate tables?

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

  • Changing the LTS mapping in BMM layer  to new Physical Alias table

    Experts
    I need to change the source table mapping in my BMM layer to new physical tables aliases.
    I have finished BMM layer design (column name changes, business friendly names etc.) before actually creating the alias tables in the Physical layer and I know I hv to run for hiding now. I expected changing the logical source mapping to the new aliases will work but it's not the case though it works partially. Since the Column names are changed in the bmm, I have to manually change the Expression, Physical Table in the LTS column mapping tab for each non-matching name logical columns.
    Column mapping is intact where both the BMM columns and the new Physical alias names match.
    eg: CALENDER_YEAR(BMM) ---> CALENDAR_YEAR(Physical alias) mapping is intact but
    Week Day(BMM) ---> WEEK_DAY(Physical alias) need to be changed manually.
    Any tips/suggestions will be appreciated.
    Regards,
    Tom

    Hi Tom,
    I too do not see any other options here other than manually modifying the individual logical columns. When there is a new logical column, we have to map it manually to the physical column explicitly because the Admin tool will not know which physical column to pick up.
    Hope this helps.
    Thank you,
    Dhar

  • Link Join Concept In Physical and Business Model Layer

    Hi,
    As we know that we could make join relationship in physical layer and also business model layer in obiee 10g. This is what makes me confuse.
    First of all, I tried to follow the tutorial in the oracle learning library center with schema SH as an example.
    In the beginning, it is stated that we must make join relationship first in physical layer for all imported tables which are consist of dimension tables and fact tables.
    Then, in the business model layer, the tutorial said that we must also make join relationship for the logical dimension table and logical fact table.
    So, what's the purpose actually we must make join relationship in business model layer ?
    All objects in business model layer are actually mapped from physical layer. So automatically the relationship in business model layer should be available automatically as they are mapped from physical layer.
    Maybe for you guys who know the concept well about this difference of relationship, could tell me so I could get the idea of what it is actually about.
    Thanks

    Physical layer does represent datamodel joins as is in almost all cases.
    Federated queries are a best example why joins are implemented in both (Physical & BMM layer) places.
    Business model mapping layer is modelled according to your business requirements.
    This is where your model MUST be a simple star schema, also where you model your hierarchies based on logical tables in bmm layer, & do appropriate aggregate navigation.
    Hope the view points presented will put you in right direction.
    mark answers promptly.
    -bifacts
    http://www.obinotes.com
    J
    Edited by: bifacts on Dec 16, 2010 9:19 PM

  • Cardinality in BMM layer

    Dear All ,
    I have a question in the rpd in OBIEE that is what difference we will get when we have given an option in the BMM layer as 1 to many 0r many to 1 to 1 in the Joining tables .I would like to know that this cardinality will give any difference in the record count in the reports .
    Please suggest me what is the usage of the cardinality in sql query out put .
    Thanks

    Hi,
    From the guide "A key property of a logical join is cardinality. Cardinality expresses how rows in one table are related to rows in the table to which it is joined. A one-to-many cardinality means that for every row in the first logical dimension table, there are 0, 1, or many rows in the second logical table. The Administration Tool considers a table to be a logical fact table if it is at the Many end of all logical joins that connect it to other logical tables"
    It really matters when you specify the driving tables if left hand side has less reocrds than right hand and makng it as driving table by menitoning the cardinality
    Thanks,
    Saichand

  • How to resolve unresolved column error when we change column name in BMM Layer and removed alias in presentation layer

    how to resolve unresolved column error when we change column name in BMM Layer and removed alias in presentation layer

    Looks like the presentation column got Alias before your BMM changes, so in your case renaming logical column and deleting alias is not good to go.
    Keep Alias

  • 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

  • Facts and dimension tables in BMM layer

    HI Experts,
    i have one doubts that is.... i have 7 Fact and 20 dimension tables in my current project ( this is mine first project ) how can i join these tables in BMM layer...
    Regard's
    Harish

    Harish,
    Just explicitly mentioning # of facts and dimensions won't fetch you any help. Extract a simple business scenario containing a fact and dimension tables.
    e.g.
    1. firstly, how many of the fact tables built are associated with different subject areas?
    2. of the fact tables belonging to each subject areas, how many of them are aggregate tables?
    3. if step 1 is not true, do they have conformed dimensions to access? <-- a caveat exists which your user MUST definitely know.
    4. are there any partitions?
    5. are they aggregate or summarized tables?
    etc,....
    based on which your modelling will start.
    -bifacts :-)
    http://www.obinotes.com

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

  • Unable to create logical dimension in bmm layer

    Hi all,
    I am not able to create a logical dimension hierarchy in the bmm layer of the rpd.
    when I right click on the table I am not able to find the create logical dimension option in the popup window.
    could you please help me out in this?
    In the logical table we have data from sql statement also.
    Thanks!

    Create Dimensions is only available if the selected logical table is a dimension table (defined by 1:N logical joins) and no dimension has been associated with this table.
    To create a dimension automatically, the Administration Tool examines the logical
    table sources and the column mappings in those sources and uses the joins between physical tables
    in the logical table sources to determine logical levels and level keys.
    Hope you have defined the Logical join in BMM before looking for this option. If joins are not defined, this option won't come.
    Refer http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf
    Page 133, Creating Dimensions Automatically
    Hope its useful

  • 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

  • Problem with BMM layer warning messages.

    Hi,
    I have modelled with the following tables in BMM layer.
    Dimension tables: Regions,Countries,Departments, locations, Employees, jobs, job history
    Fact table: HR Facts (measured columns like salary, max salary, min salary, commission)
    The model is consistent with the following warnings:
    Logical dimension table REGIONS has a source REGIONS that does not join to any fact source.
    Logical dimension table DEPARTMENTS has a source DEPARTMENTS that does not join to any fact source.
    Logical dimension table COUNTRIES has a source COUNTRIES that does not join to any fact source.
    Logical dimension table LOCATIONS has a source LOCATIONS that does not join to any fact source.
    and also in the answers section (Presentation services) i could not able to view data, it's giving the following error (when i am trying to display REGION NAME field values)
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: REGIONS.REGION_NAME. Please fix the metadata consistency warnings. (HY000).
    I could not able to trace the problem where exactly is to be fixed.
    regards
    chandra kanth.

    Hi,
    Thanks for the information. Ideally that works out without any hierarchies. But the problem with which i was facing is somewhat different.
    Let me explain the problem scenario exactly:
    I have an employee, region tables in physical layer. Employee table has SALARY Column. Region table dont have any
    join with Employee table. In BMM layer i have created a fact table "HR Facts" and crated a logical fact column SALARY.
    The logical fact table source is Employee table. I have drag dropped Region table into BMM layer and joined with HR
    Facts table. While consistency check its given a warining message: Logical dimension table REGIONS has a source
    REGIONS that does not join to any fact source.
    What is the problem exaclty?
    regards
    chandra kanth.

Maybe you are looking for