Additional join in rpd physical layer.

Hi,
I created a subject area joning all the tables in physical and BMM. Now I need to existing two tables with one more key. Can I just go the physical layer joins, double click on the join and add the new join there. Can we do like this or is there any process to follow. Please advice.

user4683504 wrote:
Hi,
I created a subject area joning all the tables in physical and BMM. Now I need to existing two tables with one more key. Can I just go the physical layer joins, double click on the join and add the new join there. Can we do like this or is there any process to follow. Please advice.Yes thats it, or edit the join from the UI (right click table -> Foreign Keys)

Similar Messages

  • Logical joins differ from Physical layer joins

    Can please answer to my Question?
    1.How does Logical joins differ from Physical layer joins?
    2.What is NQSConfig.INI file and what does it contain?
    Thanks
    Chi
    [email protected]

    2) The NQSConfig.INI file contains configuration and tuning parameters for the Oracle BI Server. There are parameters to configure disk space for temporary storage, set sort memory buffer sizes, set cache memory buffers, set virtual table page sizes, and a number of other configuration settings that allow you to take full advantage of your hardware's capabilities.
    For more information about the NQSConfig.INI file parameters, refer to Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
    1) Logical joins are used in Business Model, Physical joins are used in physical layer. 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. Logical joins supports outer joins. so many else to mention... just go through RPD help file.
    - Madan

  • Defining Keys/Joins in the physical layer

    When the keys and the join conditions are defined manually using a table's Properties dialog box in the Physical layer, do these keys or joins also get defined in the database automatically? My understanding is that it does not get created in the database. So what I am trying to understand is - once the joins are defined in the RPD physical layer, do I have to then define the indexes/constraints in the database as well?
    Thanks,

    803309 wrote:
    When the keys and the join conditions are defined manually using a table's Properties dialog box in the Physical layer, do these keys or joins also get defined in the database automatically? No
    My understanding is that it does not get created in the database. So what I am trying to understand is - once the joins are defined in the RPD physical layer, do I have to then define the indexes/constraints in the database as well?
    Not required. Indexes can be created in DB on joining col for performance purpose only.
    Hope this helps
    Edited by: Deepak Gupta on Aug 15, 2011 10:07 AM

  • Joins in the physical layer

    Hi,
    I have a small doubt:
    Is it possible to to give the Outer joins in the physical layer+ of the RPD.i.e.,left outer join,right outer join and full outer join.
    If yes can you pls provide me any links related to that.
    Thanks,
    Chinna

    Hi,
    No we cannot have outer joins in Physicla layer.
    We can outer joins in BMM layer.
    In BMM layer - complex join can be full inner join or full outer join or whatever your criteria was,but in physical layer - physical join is always an inner join.
    Check this....http://nerdsofobiee.wordpress.com/2010/07/06/obiee-interview-questions/
    http://gerardnico.com/wiki/dat/obiee/physical_layer
    Regards,
    Srikanth
    Edited by: Srikanth Mandadi on Oct 15, 2010 1:29 AM

  • How to reimport relational table objects into RPD physical layer...

    I am new to OBIEE. I am not sure how to reimport relational database tables into physical layer whenever the base database table structure changes.
    How do I configure the ODBC or OCI 10G/11G connections on my computer so I can reimport objects into RPD on remote server.
    I would appreciate it if you can give step by step instructions
    Thanks in advance.

    Hello -
    You can re-import a table to the Physical Layer the exact same way that you would import the table for the first time:
    1) Click File > Import > From Database...
    2) Select your data source connections
    3) Choose your table you wish to reimport
    The system will warn you that you will overwrite the existing table and may lose information. The information you would lose is any discrepencies in the physical layer that are no longer existing in the actual database table. However, logical columns will NOT be overwritten.
    Alternately, if it is a minor change to the table (say a column name change, or one additional column added), you can also manually add the column
    1) Right Click on the already imported table in the presentation layer and select New Object > Physical Column...
    2) Name the column and provide the proper data type
    The column now exists in the physical layer and will be properly associated with the new column in the database, assuming the same column name was attributed. You WILL have to drag this new column forward to the logical layer and presentation layer, as this will not be automatically done.
    I hope this answers your question. If you found this helpful, please assign points!
    Regards,
    Jason

  • Keys and Join description at physical layer does not reflect in BI Answer?

    Hi All ,
    While creating a RPD , the description about keys and join information using
    description and hint property which we define at physical layer, those informations do not reflect BI Answer when i query to metadata dictionary.
    Any ideas in this regard?
    -- Ashish

    Hi All ,
    Here i give little bit more description what i did.
    (1) I created a RPD and gave some description about Foreign Keys and using hint a gave some description about Physical joins.
    (2) After then using utilities I generated the Metadata Dictionary.
    (3) Now after restarting of services when i query to Metadata Dictionary using BI Answer , i am not able to see those descriptions. Rest of the information like table level and column level descriptions i am able to see.
    Is there any way to get these descriptions or metadata dictionary does not keep descriptions for keys and joins?
    Any ideas in this regard??
    --Ashish                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Multiple joins Problem in Physical Layer.

    I have two tables Departments and Employees in the physical layer of admin tool. When i am trying
    to create foreign keys at physical diagram its giving error.
    Scenario:
    Departments                    
    ===========               
    Department_id (PK)               
    Manager_id (FK)                    
    Employees
    ========
    Employee_id (PK)
    Department_id (FK)
    Manager_id (FK)
    1. Manager_id of Departments table references Employee_id of Employees table
    2. Department_id of Employees table references Department_id of Departments table.
    3. Manager_id of Employees table references Employee_id of Employees table.
    I have done 1st one. After 2nd one i have tested for consistency check, the following error is coming:
    [38015] Physical tables "Oracle DB Connection".."HR"."EMPLOYEES" and "Oracle DB Connection".."HR"."DEPARTMENTS" have multiple joins.
    Delete new foreign key object if it is a duplicate of existing foreign key.
    How to solve this?
    How to do 3rd one also?
    Please clarify.
    regards
    chandra kanth
    Edited by: Chandra kanth on 08-Dec-2011 01:47

    Hi,
    I have created two alias tables (E1 Employees, D1 Departments) for Employees, Departments tables.
    I have created foreign key joins as follows:
    D1 Departments:
    EMPLOYEES.EMPLOYEE_ID = "D1 DEPARTMENTS".MANAGER_ID
    E1 Employees:
    EMPLOYEES.EMPLOYEE_ID = "E1 EMPLOYEES".MANAGER_ID
    and it is consistent also. Please let me know whether the above approach is right or not.
    regards
    chandra kanth.

  • RPD Physical Layer

    Hi,
    I am trying to import tables from database to the physical layer. when we select objects to add to physical layer which boxes to we need to check below. I know we need to check 'Tables' and 'Keys'. Other than these two do we check any other box?

    Thank you. I have one more question. When I try to do a foreign key join in Physical layer a message pops up saying ' A matching table key doesnt exist in table. Do you want to create one'. Sould I just say 'yes' to it. Any idea why this message is coming?

  • OBIEE 11g - complex join in physical layer

    Hi, I need to create a complex join in the physical layer with join criteria like the following:
    fact.fiscal_year = dim.fiscal_year and fact.accounting_period <= dim.accounting_period
    Every time I try to do this, I get the nQSError: 37005 Transaction Update Failed message. Any ideas what is going on?
    Thanks,
    Scott

    Actually, I (finally) got it to work - wow logical joins are a big pain in the butt in 11g. First off, I had to edit the RPD offline, couldn't get it to work (at all) online.
    Next I had to delete the existing joins...there appears to be no way to change an existing FK join into a logical join.
    Next created the logical joins as stated in my original post - but had to fiddle with it for about 15 minutes to get it to work. You can NOT click the two columns on the dim side, two columns on the fact side, and then just edit the default formula (which defaults to have = sign between the expressions) - because it creates a FK join, and then you start getting errors. Instead, I had to build the expression from scratch.
    All in all, 11g has gotten much less flexible and easy to use in this regard.
    Scott

  • Trunccolumn value while importing data to physical layer in RPD

    Hi All,
    While importing data from database, I want to trunc few column values so that I can put complex join, but I am not getting any link to do so.
    Can anyone suggest me that if on database, if two tables are linked by outer join, than how can I restore the same join state in Physical layer while maintaining star schema.
    Thanks in advance.

    Hi,
    I am using version 10.1.3.4.0
    This query is a select type physical table in a physical layer of the RPD
    select distinct project_no,project_name from cw_vertical_d where project_no = VALUEOF(NQ_SESSION."Project_Number")
    NQ_SESSION."Project_Number" is a session non system variable.I am trying to set this variable through a dashboard prompt ( as a request variable ).
    So when a user selects any value in the dashboard prompt then this session non system variable "Project_Number" should be set and then BI Server should fire a query with this value to pick the data from database.
    But this report is failing with "*[nQSError: 23006] The session variable, NQ_SESSION."Project_Number", has no value definition*" error.
    Don't know what is causing this?
    Regards,
    Vikas

  • Complex join in physical layer

    Hi Experts,
    In which scenarios we will use complex join in physical layer i saw in many blogs that when we are using expressions and other than equality.
    For better under standing can any one post few scenarios on this.
    Regards,
    Rafi

    Hi,
    Always use “Foreign Key” joins, not “Complex Joins” on the Physical Layer
    Refer-http://obiee101.blogspot.com/2011/10/obiee11g-golden-rules-rpd-physical.html
    If your join looks like D_DATE = TRUNC(S_DATETIME) try add a extra column S_DATE in your DWH. Any matching processing done by the BI-server costs time and you often loose the advantage of an index in your DWH.
    For all others relationships other than a Primary Key-Foreign Key Relationships (expression other than equal to perform an equi join), you have to use a complex join otherwise you have to use a foreign key

  • Physical Layer Joins

    I am creating a data model from a database that is in 3rd Normal Form. My understanding in the physical layer I should make the joins based on the relation between tables. I have a CUSTOMER & ADDRESS table and I understand that my join will be 1:M here since 1 Customer can have many addresses. However I would like to get all my facts from the CUSTOMER table so since this is going to be the fact table should the Many end of the join be at the CUSTOMER table. I have been given much misinformation about this and have 2 scenarios but do not know which is correct.
    Scenario #1: Model the joins in the physical layer as 1:M e.g 1 Customer has many Addresses and then reverse the joins in the BMM to make the CUSTOMER table a fact table.
    Scenario #2: Model the joins in the physical layer making the M (Many) side of the join on the Customer table therefore choosing it as a fact table in the physical layer.
    Thanks in advance for any answer.

    So if I understand correctly then the join in the physical layer will look like this: CUSTOMER------------->ADDRESSES. Is this because the CUSTOMER table is going to be the fact table. I thought the relationship between Customer and Addresses is a 1:M i.e. 1 Customer has many addresses. Why do we not model this in the Physical Layer.

  • 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

  • Unable to do Physical Join in rpd

    Hi
    I tried to join table Ra_Customer_trx_all and OE_order_header_all but the join condition is to_char(OE_order_header_all .order_number) = Ra_Customer_trx_all .Attribute6
    can i use this join condition in physical layer..Because in physical join we staraightway give the join condition but here we are changing the column type and then using the join.
    I am using OBIEE 11g
    thanks in advance for the help
    Debo

    Hi
    Thanks for the solution in physical join but when i simply join the two tables in the business layer the logical join is not pulling any data..Do we need to do something else to do the logical join between those tables
    Regards
    Debo

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

Maybe you are looking for