Circular Joins

How to overcome the problem of "Multiple Path exist between 2 dimension" "Circular Joins are not supported"
Ex: A--> B, C and B--> C

Please find below a small example:
Circular join:
Countries --> Customers
Countries --> Sales
Customers --> Sales
Solution with aliases:
Countries_Customers --> Customers
Countries --> Sales
Customers --> Sales
Other typical use of aliases is where you use a physical table for different meanings. For example countries might link to both the customer country and the country of the sales office.

Similar Messages

  • Multiple Fact Tables or Circular Joins?

    I'm using OE schema to build an rpd, I'm importing foreign keys and I'm unable to decide which tables to be joined additional to the imported foreign key joins. If I'm not making any new joins I'm getting multiple fact tables and if I do make some joins I'm getting circular joins, some one please throw some light on this.

    It is not a good idea to bring the OE schema tables as it is. The ideal approach would be to create a view that would represent the Fact table. For e.g this view could comprise of OE headers and OE line information and the reference id to the other dimensions.<br>
    <br>
    Similarly create views from customer table, item tables etc and then create a star schema surrounding the fact view with all these dimension views.<br>
    <br>
    -Nilesh<br>
    Dashboard Development

  • Circular Joins in OBIA

    Hello Gurus,
    I have created a logical model where I am using conformed dimensions for reporting on multiple facts withing that Business Model.
    So lets say I have two dimensions Dim - Work Order and Dim - Company and I have two facts Fact - GL and Fact - SLA
    Fact GL is joined to Dim - Work Order and Dim - Company also does the Fact SLA in both physical and logical.
    I have created two Presentation subject areas and called it GL Analytics and SLA Analytics and put my respective GL and SLA facts and thier dims.
    When I try to pull the columns only from by dimensions Work Order Number from Dim- Work Order and Company Name from Dim - Comapany, even though these are joined to Fact -SLA table OBIEE is issuing qeury to Fact - GL instead. So I can sense a circular join problem here. I can see only results from one Company Name but not Work order number in the analysis.
    However in the BI Apps OOTB data model. I consider AP - Posted Transactions , AR - Posted Transactions with Dim - GL Account(Segment 1) and Dim - GL Company ( semgment 2) they to have a similar join. However when I query only dims Account number and Company name I get results for both and the query send joins to correct table W_AP_XACT_F and joins these dim tables.
    What am I doing wrong here.
    could someone please help me out.
    Thanks in advance.
    VidyaS

    Hi VidyaS,
    In the properties of your presentation subject area, you could specify an implicit fact column:
    For each subject area in the Presentation layer, you can set an implicit fact column. The implicit fact column is added to a query when it contains columns from two or more dimension tables and no measures. The column is not visible in the results. It is used to specify a default join path between dimension tables when there are several possible alternatives or contexts.
    Hope it helps,
    Benoit

  • 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

  • Circular joins in 11g

    Hi Gurus,
    I am working on 10g...In obiee there is no support for circular joins,if we do also consistency check will give us a Error..so I want to know is it Solved in 11g or is there any alternative provided in 11g to achieve circular join type of condition?please share your thoughts/information you have..
    Thanks in Advance...

    Hi,
    Circular joins should not be used and its not a best practice, no matter the version of the tool.
    Its always good to avoid them and use alias table to avoid them.
    You might have got lots of stuff but also do refer below link to avoid:
    http://www.rittmanmead.com/2008/08/resolving-fan-traps-and-circular-joins-using-obiee/
    Hope this helped.
    Regards
    MuRam

  • Error: 38015, Physical tables have multiple joins.

    Hi,
    I have 5 dimensions and 1 fact table. One of the dimension table have 2 keys, which are referenced with fact table.
    I have created aliases for all table on which I have defined joins.
    But, It is giving me error like
    ERRORS:
    GLOBAL:
    *[38015] Physical tables "obidb".."ORDER_DETAILS"."FACT" and "obidb".."ORDER_DETAILS"."BILLING_ACCOUNT" have multiple joins.*
    Delete new foreign key object if it is a duplicate of existing foreign key.
    Please give me any suggestions.....
    Thanks.

    Hi,
    Did your deleted existing foreign key before joining the alis_dim1(fk1), dim1(fk2) to fact join?
    double check u r model its comes like circular join so by using alias method u r can resolve that issue.
    In your model just check all your FK relation ship here u can find FK ending with #1 (double time just delete them and check metadata consitancey) if its not working delete the dimension and import it newly then create alias of the dim then join each other required fact also check below link
    http://mtalavera.wordpress.com/2012/03/29/obieerpd-fails-global-consistency-on-joins-between-tables/
    Thanks
    Deva
    Edited by: Devarasu on Nov 23, 2012 4:44 PM

  • Oracle BI Joins

    Hi all,
    I have two tables and there is no direct join between them in physical or logical layer, but there is a few indirect joins through a few tables.
    When I put these tables in one report in presentation services, it doesn't give an error. From query log I can see that it joined these tables one using one of tables between. What I want to understand is how it decides the join. If there is more then one path between tables how it decides to go.

    Hi seth2,
    I think if you have more than one way to go in you table, then OBIEE will produce an error.
    It is recommended that you use table aliases frequently to eliminate extraneous joins, including the following:
    * Eliminate all physical joins that cross dimensions (inter-dimensional circular joins) by using aliases.
    * Eliminate all circular joins (intra-dimensional circular joins) in a logical table source in the Physical Model by creating physical table aliases.
    Come from here : http://download.oracle.com/docs/cd/E12103_01/books/admintool/admintool_RepositorySetup7.html
    If you have more than one logical table source in the business model layer then obiee will choose the table which have the lowest grain defined. Obiee call this an Aggregate Navigation :
    http://gerardnico.com/wiki/dat/obiee/bi_server/design/fact_table/obiee_query_rewrite
    Regards
    Nico

  • Doubt regarding joins in obiee

    hi gems...
    i have a doubt regarding BI analytics join.
    When i have imported all the tables from my schema in the repository, then it got imported with all the joins defined in the database.
    then i made several business models and create some reports.
    there i got some errors, which are mainly due to self join in the tables and more than one joins between two tables.
    my question is...are these two types of joins not supported in obiee???
    and if i want more than one join condition between two tables, then what can i do???
    thanks in advance...

    Hi User,
    OBIEE doesnot support self join. To avoid such circular joins ,make use of alias tables in the physical layer.The following is a list of the main reasons to create an alias table:
    To reuse an existing table more than once in your physical layer (without having to import it several times.
    To set up multiple alias tables, each with different keys, names, or joins.
    To help you design sophisticated star or snowflake structures in the business model layer. Alias tables are critical in the process of converting ER Schemas to Dimensional Schemas
    Rgds,
    Dpka

  • Why Do we need to go for Alias? What are the Different uses of Aliases?

    Hello Everybody?
    I wanted to know the uses of aliases in RPD level. I do know some points like they will be used as a duplicate copy for the base tables and they will be used to remove the circular joins, otherthan this can anybody please give me a brief view about the different uses of Aliases.

    This article gives some good arguments for why you should use aliases:
    http://it.toolbox.com/blogs/achieving-great-bi/physical-layer-tips-and-gotchas-16445
    1. Import physical tables without FK joins turned on. Make the joins yourself, so there is nothing hidden that could cause problem. You should "own" your joins, not the other way around.
    2. Aliases are the technique one uses to eliminate circular joins. An easy example of how to use aliases is when you have a lookup table, like W_LOV_D - each version of it requires an alias, which will be joined to differently.
    3. With all tables & aliases, using a naming standard will guarantee that only one physical layer object will exist in one Business Model object. If you prefix every object in the physical layer with its Logical usage first (essentially making everything an alias), you will not be able to use the Customer (W_COUNTRY_D) table in the Employee logical table, as the standard would require you to use a table alias called Employee (W_COUNTRY_D).

  • 3-1674105521 Multiple Paths error while using Bridge Table

    https://support.us.oracle.com/oip/faces/secure/srm/srview/SRViewStandalone.jspx?sr=3-1674105521
    Customer Smiths Medical International Limited
    Description: Multiple Paths error while using Bridge Table
    1. I have a urgent customer encounterd a design issue and customer was trying to add 3 logical joins between SDI_GPOUP_MEMBERSHIP and these 3 tables (FACT_HOSPITAL_FINANCE_DTLS, FACT_HOSPITAL_BEDS_UTILZN and FACT_HOSPITAL_ATRIBUTES)
    2. They found found out by adding these 3 joins, they ended with circular error.
    [nQSError: 15001] Could not load navigation space for subject area GXODS.
    [nQSError: 15009] Multiple paths exist to table DIM_SDI_CUSTOMER_DEMOGRAPHICS. Circular logical schemas are not supported.
    In response to this circular error, the developer was able to bypass the error using aliases, but this is not desired by client.
    3. They want to know how to avoid this error totally without using alias table and suggest a way to resolve the circular join(Multiple Path) error.
    Appreciated if someone can give some pointer or suggestion as the customer is in stiff deadline.
    Thanks
    Teik

    The strange thing compared to your output is that I get an error when I have table prefix in the query block:
    Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
    Starting "SYSTEM"."SYS_IMPORT_FULL_01":  system/******** DUMPFILE=TMP1.dmp LOGFILE=imp.log PARALLEL=8 QUERY=SYSADM.TMP1:"WHERE TMP1.A = 2" REMAP_TABLE=SYSADM.TMP1:TMP3 CONTENT=DATA_ONLY
    Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
    ORA-31693: Table data object "SYSADM"."TMP3" failed to load/unload and is being skipped due to error:
    ORA-38500: Unsupported operation: Oracle XML DB not present
    Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 1 error(s) at Fri Dec 13 10:39:11 2013 elapsed 0 00:00:03
    And if I remove it, it works:
    Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
    Starting "SYSTEM"."SYS_IMPORT_FULL_01":  system/******** DUMPFILE=TMP1.dmp LOGFILE=imp.log PARALLEL=8 QUERY=SYSADM.TMP1:"WHERE A = 2" REMAP_TABLE=SYSADM.TMP1:TMP3 CONTENT=DATA_ONLY
    Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
    . . imported "SYSADM"."TMP3"                             5.406 KB       1 out of 2 rows
    Job "SYSTEM"."SYS_IMPORT_FULL_01" successfully completed at Fri Dec 13 10:36:50 2013 elapsed 0 00:00:01
    Nicolas.
    PS: as you can see, I'm on 11.2.0.4, I do not have 11.2.0.1 that you seem to use.

  • Consistency check error in OBIEE 10g

    Hi
    I have the below error while doing consistency check.
    I was trying to join two fact tables by complex join, but getting below error
    NQSError:15009 Could not load navigate space for subject area
    NQSError: 15009 Multiple paths exist to table Plans.Circular joins schemas not supported
    Please suggest

    If you have to join fact tables in physical, make sure your logical layer remains a star.
    Either add both fact tables to one logical fact table source , or create two logical stars, where both facts are joined to all conformed dimensions.
    Note: if both facts are not at exactly same granularity, your reports will show incorrect results most definitely. So avoid fact to fact joins.

  • Reporting running for more than 30 min and still says retrieving the data

    Hi,
    I created a report using a view, and in RPD for a measure column I put the aggregation AVG.
    In front end when I pull the column , if the column is placed in measure or column the report is displaying in 30 sec. But I want the report in rows section, when I place the column in row , the report is running for longer time and not displaying the data, Please help, any help is highly appreciated.
    Thanks & Regards,
    SR
    Edited by: user9255588 on Apr 14, 2013 5:22 PM

    Kindly chk the physical query and execute it in DB and chk its taking the same time
    If not chk the join conditions any circular joins present
    Hope it helps
    Regards,
    Nandha

  • URGENT!!! Incorrectly defined LTS

    Gurus..please help
    Physical Layer: I have the following tables
    Dimensions: D1, D2, D3...D10
    Facts: F1, F2
    Both facts are joined to all the dimensions and also both facts are joined to each other as I would need to drill down.
    BMM: same joins except a join between two facts as it would lead to circular join.
    Presentation: Brought in all the tables.
    Report level: I am using D1.C1 with F2.C1 and it throws me this error:
    View Display Error
    Odbc driver returned an error (SQLExecDirectW).
    Error Details
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    *State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table D2.C1) does not contain mapping for [F2.C1, D1.C1]. (HY000)*
    SQL Issued: SELECT "F1"."C1" saw_0, "D1"."C1" saw_1 FROM "HOT Sales Queries" WHERE "F1".C1 = 'ABCDE' ORDER BY saw_0, saw_1
    FYI: I tried to add the mappings in LTS but still didnt help.
    Please help....its very urgent....have been struggling.

    Hi,
    Try to Create heirarchy for the dimension.
    Then in LTS for both the fact tables, set the level to the lowest level of the dimension. (or other level as the case may be).
    for more refer:
    nQSError: 10058 Incorrectly defined logical table source
    Thanks
    Deva

  • Patch in obiee 11.1.1.6.0

    The action link reports is not opening in new window for obiee 11.1.1.6.0 . What patch should I apply in order to fix this? I do not want to upgrade to obiee 11.1.1.6.2 right now. I want to confirm if patch 14003822 will fix this bug.
    Thanks,
    Sanjay

    When I check for the patch 14003822 in the oracle support, it did not mentioned about the Bug 14165667 - LINKED REPORT OPEN IN NEW WINDOW DOES NOT WORK AFTER A CHANGE PROMPT bugs that has been resolved. The list of bugs that have been resolved from the patch are as follows;. Do I need to upgrade to obiee 11.1.1.6.1 or just if we use this patch it will solve this issue.
    Thanks,
    Bugs Resolved by This Patch
    10647655     COLUMN DATA FORMAT IS IGNORED ON WRITEBACK
    12612904     TOTAL PICKS VALUE IN FIRST ROW AND GIVES NOT A NUMBER WHEN AVERAGING NULL
    12978196     COLUMN SELECTOR DOES NOT PASS VALUES FROM SUMMARY REPORT TO DETAILED REPORT
    12981896     MAPVIEWER HOVER TOOLTIPS SHOW WRONG VALUES
    12992697     PAGE BREAK WITH COLUMN BREAK DOES NOT WORK IN PRINTABLE HTML
    13043745     PIVOT TABLE'S LAYOUT COLLAPSES WHEN HIDDEN ROW AND TOTALS BEFORE IS USED
    13071711     CIRCULAR JOIN ERROR WHEN RUNNING ANALYSIS USING UPGRADED REPOSITORY
    13083074     PROMPTS CREATING UNSPECIFIED ERROR WHEN SELECTING MULTIPLE CONSTRAINED CRITERIA
    13098323     AN ARITHMETIC OPERATION IS BEING CARRIED OUT ON A NON-NUMERIC TYPE
    13110980     THE SECTION PROPERTIES OF PIVOT TABLE IS NOT EFFECTIVE OR NOT CORRECT
    Open Readme to View all Bugs
    Related Knowledge to this Patch
    1470402.1     OBIEE 11g: Unable to See Column Added to Pivot View in Criteria Tab when Graph has been Added to Results     Modified 07/01/2012
    1467168.1     MULTIPLE PIE CHARTS DISPLAYED FOR PIVOT TABLE REPORT WHEN SHOULD BE ONE     Modified 06/12/2012
    1465324.1     OBIEE 11g: Cannot Edit Position of a Chart in Charted Pivot Tables     Modified 07/24/2012

  • Business Model with 2 fact tables

    Hi there
    I am trying to get a simple business model working , 2 fact tables, 1 dimension, similar to this example :
    http://www.rittmanmead.com/2008/08/resolving-fan-traps-and-circular-joins-using-obiee/
    However I keep getting this: [nQSError: 14025] No fact table exists at the requested level of detail:
    the tables are:
    Incident (dimension)
    PK Sequence
    Incident Detail (fact table 1)
    PK Sequence
    FK Problem #
    Order (fact table 2)
    PK Sequence
    FK HDNum
    I cant figure out why this doesnt work like the rittman mead example? do they need to have the same column name?
    Thanks
    Tim

    It says the model doesnt contains a fact table.Fact table will have foreignkeys and Measure columns.That link shows the circular joins between tables.There fact table is not there.
    See this link for fact and dimensions
    http://www.geekinterview.com/question_details/66773

Maybe you are looking for