Union of more than 2 fragments/Logical Table Sources in BMM Layer

Hi,
I have come across many blogs which explain how to union two fragments/physical tables in a logical table source.
Currently, i have a requirement where i have to combine/union 4 fragments/physical tables in a logical table source, say T1, T2, T3, T4 dimension tables.
All have the same table structure, but differ in data.
The requirement is to define dashboard prompt on the union of these tables and populate the values from all the tables.
I am able to union two of the tables using a '>' and a '<' condition on a key column.
But, am not able to union the other two tables.
If i try to put more than 2 LTS, then the union fails.
Please share your thoughts.
thanks,
Varun

Hi Varun,
What do you mean by the Union fails?
You can have a logical table source in your business layer with 4 different tables as a source.
Import the tables in the physical layer and create your joins.
Then create a logical table in the Business layer and go in the table properties you will see that you can add as much tables as you want into the source (Map to these tables).there you can add all of your 4 tables and specify what type of join you want to have between them (inner, outer...)
Regards
Adil

Similar Messages

  • Logical table having more than one Logical table sources

    Hi ,
    Is it possible a logical table has 2 logical table sources and there is no join between the underlying table of logical table sources?
    What will happen if we create the request which contains one attribute from each source?
    Will BI server return records with Cartesian join?
    Is it mandatory if logical table is having more than one logical table sources(exp. Logical table sources are X,Y and underlying table is A,B respectively),
    The underlying tables (A&B) must be joined ?
    Can someone explain the logic behind the logical table sources? How does it work?
    Any reference of document will be appreciable.
    Thanks,Ashish

    Hi Stijn,
    Thanks for response.
    You are saying that Oracle BI server will run a query against both tables and combine the results. But if there is no possibilty of any type of join, how BI server will combine the results from both tables.
    I have a scenario like below -
    Suppose i have 2 tables A and B at physical layer. Both table contains the information of any common subject area.
    But there is no attribute is common between A and B so not any kind of join possible between two.
    Now if i create a logical table with 2 logical table source A and B and create any request having one column from A and one from B ,
    What will happen? How BI server will combine the result? Will BI server not result records after Cartesian join.
    How can i model this scenario?

  • Time series functions are not working for fragmented logical table sources?

    If i remove that fragmented logical table sources, then its working fine.
    if any body know the reason, please let me know.
    thanks and regards,
    krishna

    Hi,
    is because the time series function are not supported for the framentation content, see the content of the oracle support:
    The error occurs due to the fact the fragmented data sources are used on some Time series measures. Time series measures (i.e. AGO) are not supported on fragmented data sources.
    Confirmation is documented in the following guide - Creating and Administering the Business Model and Mapping Layer in an Oracle BI Repository > Process of Creating and Administering Dimensions
    Ago or ToDate functionality is not supported on fragmented logical table sources. For more information, refer to “About Time Series Conversion Functions” on page 197.
    Regards,
    Gianluca

  • Multiple Logical Table Sources In BMM Under 1 Logical Table In OBIEE 11g

    I have a question and even after doing a lot of search on google i could not find any article so through to ask you :-
    I want to create a Logical Dimension table
    This logical dimension has columns coming from 2 different physical tables, TableA and TableB. The relationship between TableA to TableB is 1 to zero.
    There are 2 ways to create the logical dimension :-
    1) Go to the logical table source properties of TableA-->then there + sign click and then add TableB right outer join with tableA.
    Here in the logical table source we see only one table tableA.
    2) Drag the tableB column so that we have 2 logical table source.
    Please try this to explain without using the concept of fragmentation and without considering the fact tables. I have this question for simple logical dimension tables only.
    I wanted to know which is the right way and what requirement/factor decides what to do ?

    Check this post
    Business Model - Logical Table Source
    Let me know for Qs.
    If helps mark as correct :)

  • Logical table source in BMM

    Hello,
    I am using obiee 11g.
    I have few doubts In RPD with respect to logical table Source.
    Consider i have tableA,tableB,tableC in PL.
    Now in my BMM i dragged tableA now i want one column from the tableB.
    So which method is correct?
    1>
    Go to the logical table source properties of tableA->then there + sign click and then add tableB left outer join with tableA.
    Here in the logical table source we see only one table tableA.
    2> Drag the tableB column so that we have 2 logical table source.
    Now what i am more interested is which method is selected on what basis?
    Any help?
    Thanks

    Thanks a lot for the reply
    Second case can u just elaborate more.
    First case i think i understood.
    My main confusion is ok ill explain my situation.
    I have tableA,TableB,TableC all are connected.
    Now i have one fact table.In that fact table i would like to create 10 measures.5 From tableA,3 from tableB and 2 from tableC.
    So
    First i created 5 measures from tableA.
    Second i created 3 measures from tableB.
    Third i created 2 measures from tableC.
    Till now i have 3 logical table source sources in one LTS.
    Now in my report when i combine columns from tableA and tableB , tableB column shows no data.
    When i see in the sql i see tableB col is not taken itself.
    Then i need to go to tableB,then go to General tab and then click + sign add tableA and then go to column mapping and map atleast one col of tableA here.
    So on what basis here i should do mapping.
    Since i have 3 logical table source sources in one LTS.Each time i click on sources->tableB->i could see even the
    tableA columns but not mapped?
    Is that every column from tableA should be mapped to tableB and tableB to tableC and tableC to tableA?I mean in the column mapping
    This is something which i am feeling very difficult to understand?
    Pls help me out?
    Thanks

  • Question related to Logical table source

    Hi All,
    I have very basic questions -
    (1) When do we create multiple logical table sources within a dimension?
    (2) If a dimension has more than one logical table sources , when do we need to map the underlying table to other underlying table of logical table sources.
    For exp consider these tables XLE_Entity_Profile, XLE_REgistration , AP_Invoice_ALL
    AP_Invoice_All is a fact table. relationship between XLE_Entity_Profile & XLE_REgistration is (1:M).
    Join info is as below -
    (a) XLE_Entity_Profile.Legal_entity_id = AP_Invoice_ALL.Legal_entity_id
    to get the registration of LE the where clause is as below-
    (b) XLE_Entity_Profile..Legal_entity_id = XLE_REgistration.Source_id and XLE_REgistration.Source_table = 'XLE_Entity_Profile'
    I have created the alias of XLE_REgistration as XLE_REgistration_LE.
    With in a dimension , i have 2 logical table source - XLE_Entity_Profile & XLE_REgistration_LE.
    logical table source 'XLE_REgistration_LE' has where clause 'XLE_REgistration.Source_table = 'XLE_Entity_Profile'
    When i query , LE name , LE Registration Name, i get error like -
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14070] Cannot find logical table source coverage for logical columns: [LE_NAME]. Please check more detailed level keys are mapped correctly. (HY000)
    Le Name is from XLE_Entity_Profile and LE Registration Name is from XLE_REgistration_LE.
    But when using the properties of logical table source ' XLE_REgistration_LE' , i map it to 'XLE_Entity_Profile' ,i get the correct result.
    I am not able to understand why am i getting error in first way of modeling.
    Thanks , Ashish

    Hi Ashish,
    first about logical table sources (lts): you can create different lts for aggregation and/or fragmentation. Aggregation means that data is aggregated on another level among different physical tables. Fragmentation means that the content is different over different tables (other rows).
    In your case, I think the problem is that your dimension is not denormalized, which results in a snowflake.
    What I understand is that you have the following (physical diagram):
    Invoice (fact table) >----- Entity (Dim) >----- Registration (Dim)
    You have the following joins:
    invoice.entity_id = entity.entity_id
    and entity.entity_id = registration.source_id and registration.source = 'something'
    First idea:
    I would create the following join (in physical diagram):
    Invoice (fact table) >---- Registration (Dim)
    Where:
    invoice.entity_id = registration.source_id and registration.source = 'something'.
    Then in your Entity dimension you should create a hierarchy:
    Grand Total Level
    Entity
    Registration.
    In your dimension you should create the first lts: Entity
    Set the aggregation content of this lts to Entity.
    This lts contains only one physical table.
    Map only the entity columns to the Entity physical table.
    Then create the second lts:
    Entity and Registration.
    Set the aggregation content of this lts to Registration.
    This lts must contain two physical tables, Entity and Registration.
    Map the entity columns to the Entity physical table and the registration columns to the registration physical table.
    Let me know if it works or not.
    Regards,
    Stijn

  • Dragging the columns to existing logical table source.....

    Hi,
    I am just learning OBIEE 11g and I am using a turorial from oracle it is
    "Creating a Repository Using the Oracle BI 11g Administration Tool" for practice purpose.
    In this tutorial it is saying that drag that columns from phscial layer to Logica Table Source
    in BMM Layer to avoid creating a second logical table source.. But when I am trying to drag the columns to
    existing logical source it is disabling I mean which it is not allowing .. is there any other technique to
    do it... or Am i wrongly approaching.. .The below is brief description in the
    tutorial.
    "Drag all six columns from D50 Sales Rep in the Physical layer to D5 Sales Rep in the BMM layer. This action
    creates logical columns and adds a D50 Sales Rep logical table source to D5 Sales Rep.
    Rename the D50 Sales Rep logical table source to LTS1 Sales Rep.
    In the Physical layer, expand D52 Sales Rep Position.
    Drag POSTN_DESC and POSTN_LEVEL from D52 Sales Rep Position to LTS1 Sales Rep. Note that you are
    dragging the columns to the logical table source, not the logical table. Dragging to the logical table would create a
    second logical table source.
    Drag DISTANCE from D51 Sales Rep Parent Child to LTS1 Sales Rep. Again, you drag the column to the logical
    table source, not the logical table."
    help would be appreciated.
    Thanks and Regards,
    Sri_Oracle.

    Hi Sri,
    When you are dragging a physical column onto an existing Logical table source and if it does not let you do so, then it means that there is no physical join between the existing physical table(which the logical source is pointing to already) and new physical table (from which you are dragging the column now). So, please make sure, you have the join in place.
    Hope this helps.
    Thank you,
    Dhar

  • Logical Table source source query

    In OBIEE 10g we can have multiple logical table sources and we can also add multiple tables into a single logical table source(logical table source source). I wanted to know the difference between doing so and having multiple logical table sources for each logical source.
    Hope I made myself clear.
    Cheers
    Rem

    Hi Rem,
    When data is duplicated across different physical tables add them as separate LTS with column mapping pointing to most economical sources. Specifying the most economical source is about the idea that a single column exists in more than one table, based on the column mappings BI server picks up those LTS's which could satisfy the request with minimal joins.
    When the data is not duplicated add them in a single LTS source. When the physical sources are added in a single LTS, you have the flexibility of using outer joins. But specifying a join as outer join makes BI Server to include this source even if its not required otherwise when the join is inner, the sources will not be included if not required to satisfy the query.
    Hope this helps.
    Thanks!

  • Question on Logical table Sources

    Good day!
    I would like to ask for your advice on an bottleneck I am experiencing in a repository implementation in Siebel/OBIEE.
    I am to create a logical table which sources comes from two different tables(Physical table A and Physical table B).
    I am trying to union the contents from table A and table B so I planned to use fragmentation content.
    My problem is that there is no way to distinguish the difference between the records coming from physical table A and table B.
    I created two logical tables sources and specified the same condition for both but the server would automatically choose the first one and would not include the records from the second logical table source.
    Is there any other way I could combine the records from table A and table B in Business Model and Mapping layer?
    Please, I would like to know your thoughts.
    Thanks,
    Ivan

    Hi Ivan,
    I dont think there is other way which is equable to fragmentation content functionality.
    I would suggest to try with any column is not null or most satisfied condition so that both contents present in the query.
    If helps pls mark

  • BIEE Answers: Problem with logical table source

    Hi,
    I am creating a detail report in answers. This report does not use any column from the fact table in the logical model, but uses other dimension tables.
    In the logical model fact table, I use 3-4 times the same physical table as logical table source in order to filter results or not.
    The problem is that my report filters results by using one of the logical table sources. Is there a way to specify in answers or administration which should be my "default" logical table source for the specific physical table joins?
    Another workaround is to add as a filter on the report one of the columns from the fact table that do use the desired logical table source, but this is not always a workaround..
    Can you please advise?
    Thanks in advance,
    Nadia

    Remember to set the # Elements in your hierarchy to the appropriate ratio between levels, actual numbers not so important but the ratio needs to be correct for the BI Server to make the best guess if using more than one LTS.

  • OBIEE: Incorrectly defined logical table source doesn't contain mapping

    In OBIEE 10.1.3.2 I have a very simple thing but cannot get it to work. Hopefully someone can point out the mistake. I have the same schema on two different database that I want to compare data.
    The schema is simple. Table (dimension) A has two columns: id and name. Table (Fact) B has two columns: id and value. Table B.id is a foreign key to A. I imported two database schema into the physical layer and for each database, I built the foreign key relationship between table A and B. In the logical layer, I have two logic tables, one to represent A (Dimension) and the other B (Fact) with a logical join. Each logical table has two data sources. For the dimension tables, both id and name columns have two sources. For the fact table, the id has two sources and for the value, I created two separate columns, one called value1 and the other value2 with one from one database's B table's value column and the other from another database's B table's value. They then were made available at presentation layer.
    Now in the Anwser, I can build a query with id from dimension and value1 from fact; it displayed fine. Same with a query with id from dimension and value2 from fact, it displayed fine. However, if the query is id, value1 and value2, I got the following error
    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 B) does not contain mapping for [B.value1 [ ] , B.value2 [ ] ]. (HY000)
    Is there something I have to do additional to make both values appearing the same time.?
    Thanks for your help
    Ralph

    Hi, Siddhartha P
    I don't think I understand your information. I couldn't find connection pool at the business mapping layer. I only see it in the physical layer. Do you mean to do the mapping at the logical source table? That's only places I see any mappings and I don't see complex join there (only inner join, left outer, right outer and full outer) What mappings should I need to create between table B (fact table) of database 1 and table B (fact table) of database 2. I thought they don't have any relationship other than join through a dimension table which has columns that map to both table A (dimension table) of database 1 and 2. Then the logical fact table has 3 columns, one is id (to join to Dimension table) with two mappings (one to table B of database 1 and one to table B of database 2) and one column value1 which maps only to table B's value of database 1 and another column value2 maps to table B's value of database 2. That seems to be done correctly because I can pick column id and value1 or column id and value2 and have them displayed correctly but not all 3. I thought if it can display the two separately correctly, they should be able to display all 3. no?
    I am not getting any inconsistency error.
    There must be something I still don't understand. If you don't mind give me a little more direction, that would be great.
    Thanks
    Ralph

  • Problem: 1 physical table -- multiple logical table sources

    Hi,
    I'm quite new to BIEE and setting up my repository.
    So I have a question, if the following scenario is possible:
    Physical Layer: TABLE_A: COL_A, COL_B, COL_C
    TABLE_B: COL_D, COL_E, COL_F
    Join TABLE_A.COL_A = TABLE_B.COL_D
    In Business Model I have a Dimension Table with TABLE_A as datasource with fields DIM1 (COL_B).
    The Fact Table (MEASURE) would have twice TABLE_B as data source with different where-clauses on COL_F and logical table columns (ATT1 and ATT2) of value COL_E.
    So far I have created everything and the consistency check shows no errors or warnings, but I get an error in Answer: Incorrectly defined logical table source (for fact table MEASURE) does not contain mapping for [MEASURE.ATT1, MEASURE.ATT2], when I creating an report showing DIM1, ATT1, ATT2.
    Isn't it possible to have one physical column used as multiple data source?
    I know it 's working, when I create the physical table twice ... but maybe there's a solution for business model.
    Thanks
    chrissy

    Hi mengesh,
    that's what I also tried, but it's always returning me the same error.
    I know it would work, when I import the physical table twice or more, but that's not what I want to do, because at the end I have 10 or more fields based on this one physical table. There's one field indicating what value is contained in the record, this means:
    COL_F | COL_E
    1 | customer name
    2 | customer number
    3 | customer branche
    4 | salesman
    5 | date
    6 | report number
    etc.
    I don't think it's usefull to import the physical table as often as I need this field. So I want to divide it in business model.
    thanks
    chrissy

  • Max number of logical table sources

    Hi,
    I have one logical table based (a fact table) on 8 logical table sources. This is done to simulate some partitioning as my customer does not have an partition set up on data base level.
    Anyway my challenge is that a request fired in answers does not seem to take all logical table sources into account when building the physical SQL.
    The missing logical table source (the one not being part of the physical SQL) does not differ from the other logical table sources.
    Is there a limit of how many logical table sources BIEE can handle under one logical table?
    BIEE version: 10.1.3.4

    Alastair,
    thanks for replying.
    The logical tables sources partition the data by year. The aggregation level is the same for all LTS, the check for using this with other sources at this level is set and I've tried to force a result from every LTS (not combined but each LTS for itself). Forcing the results is done by using a dashboard prompt in answers filtering on year.
    The whole 'LTS-setup' works in combination with Oracle Warehouse Builder. What I mean by this is the following: In OWB I split the data from one table into 8 different tables, each containing 3 years of data (except for the oldest data where the number of years and amount of data will grow over time).
    This is done by comparing values of a year column with the actual year. E.g. the most actual table would contain data for the years 2010 - 2008, the next would contain data for 2007 - 2005, and so on.
    Now as the years in the different tables will change, I decided to establish an equaly changing counterpart in BIEE. Basically I defined some repository variables: actaul_year, three_years_ago, six_years_ago, 9_years_ago, etc.
    The fragmentation content of the different LTS is defined like this:
    most actual data: MyModel.Year.Year >= VALUEOF("3_years_ago")d
    next table: VALUEOF("3_years_ago") > MyModel.Year.Year AND MyModel.Year.Year >= VALUEOF("6_years_ago")
    next table: VALUEOF("6_years_ago") > MyModel.Year.Year AND MyModel.Year.Year >= VALUEOF("9_years_ago")
    etc.
    The funny thing is that the missing table is the one containing years 13 - 15. All the other tables (e.g. 16 - 18 years and 19 - 21 years) are represented in the physical SQL. This particular table is not even represented in the physical SQL.
    I haven't yet tried to take one of the 'working' tables out to see if this helps (getting an idea if there is a limit on number of LTS per logical table).
    Any idea?
    Thanks
    regards
    Andy

  • Logical table source error

    I am having a union report.
    I have a strange problem. The report executes successfully normally but when I am ordering the columns as per the customer requirement its throwing an error "
    A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Fact - tablename does not contain mapping for [case when Dim - Account. Number in (some values)]
    none of the report is using any column from the fact table so I don't think that join should exist between fact-dim in this case.
    Any other solution one can suggest?

    Try to redo the same report with requested order. that would be the simplest way to handle it unless you have hidden hills in your development.
    If helps mark
    Thanks,
    http://cool-bi.com

  • [nQSError: 15018] Incorrectly defined logical table source

    Hi,
    I have two fact tables and a type dimension.
    business model / physical
    fact1 /fact1
    fact2 /fact2
    type /type
    now I have them joined up on the physical layer with foreign keys AND on the business model layer.
    Nevertheless I still get this error whenever I mix and match the columns.
    [nQSError: 10058] A general error has occurred. (for fact table WABFact) does not contain mapping for [Dates.FLIGHTDATE [ ] ]. (HY000)

    Hi,
    The error "Incorrectly defined logical table source (for fact table XXX) does not contain mapping for YYY" means that the BI Server cannot reach from table XXX to table YYY. It can happen because of two reasons: The first one is that there are no relationships defined in the logical or the physical layers (or maybe both). Note that the connections can be indirect. The second one is that the relationships doesn't makes sense. For example, going from a fact table to a dimension table through many-to-many table cannot happen. You'll see this error many times as a beginner and it can be quite frustrating at first. You need to understand that the BI Server can only understand simple and classic star schemas. More complex ERDs need to be split by using alias tables.
    Thanks to-Miki
    Regards
    MuRam

Maybe you are looking for

  • OBIEE 11g Dashboard Customizations

    Hi All, I have this question which I need to be able to resolve in a short window. I have deployed a new skin for the OBIEE Dashboard and everything is working fine apart from the color or the Dashboard Page name being messed up. Please refer attache

  • Using Windows 7 on an iMac ...Can I wipe and Install Windows 7 only ?

    i have installed win 7 evaluation copy (which expires in march i think) using bootcamp ..... works just fine except for one thing: even though i have selected startup disk as windows in system prefs, it will often start in mac instead (and this is af

  • Questions Fi

    A customer from Chile consult for two reports that are required to deliver to agents of control and as indicated by them boths reports must match in Debit / Credit values. The first is the one that shows the balance J_CLBALTAX and the second is the j

  • Cannot see text in large PDF file

    Hi all, I've searched Google and these forums, but I have yet to find anything relating to my issue. I'm trying to view a PDF file, but I cannot see any text in Adobe Reader. I've viewed it w/ the FoxIt reader, and I can see all text there. Any idea

  • Error when try updating software in Setting

    When I use Software Update in Setting - General with my iPhone 4S, it prompted me "An error has occured while checking for a software update"