Logical table source

Hello!
Can someone please explain difference between dragging and dropping a physical column from a table in Physical Layer to a Logical Table in BMM layer and ragging and dropping a physical column from a table in Physical Layer to a Logical Table Source? When to use these two options?
Thanks,
-D

Hi,
First you have to read the OBIEE Administrator concept and will clear you doubt,
OBIEE Administrator, Windows based client tool to develop and manage Metadata repository. Repository changes can be done in either online or offline mode.
Online mode is when BI Server is actively reading the repository file (when a user is logged in).
Offline is when BI Server is idle. Best practice is to develop in Offline mode.
Minor changes can be made when in online mode. Administrator uses ODBC connectivity to connect to physical data sources, uses Native Drivers for Oracle and DB2.
OBIEE defines three layers of abstraction.
Physical Layer – connections to physical data sources (OLTP, OLAP, Flat Files, Oracle, SQL*Server, Teradata, etc.).
Business Model Layer – Brings together data elements from Physical sources into a logical Star-Schema representation. This is where business rules and definitions are setup.
Presentation Layer – An abstraction from the Business Model, defines exactly how users will see tables and fields.
Connection Pool is a connection to a Physical data source. Multiple connection pools can be created to the same source to improve end-user query performance.
All tables in the Physical layer must have a Primary Key column. Column properties can be edited to set the Primary Key. Physical joins need to be established between tables, using Foreign Keys and Primary Keys. Right-click on Connection pool to create the Physical diagram joins.
A Business Model can be created by drag and drop of objects from the Physical Layer. It’s a logical Star-Schema representation of the Physical objects. Tables from different sources can be merged to form one Logical table. These sources are called Logical Table Sources.
Logical Fact tables hold Metrics; every Metric must have an aggregation rule. Hierarchies can be setup on dimensions for drilldown functionality.
It is important to join logical Facts and Dimensions together, much like the Physical Diagram. Right-click on Model, click Business Model Diagram to create joins. Use Complex joins in the Business Model.
Presentation Layer is exactly what End-Users will see in BI Answers, contains multiple Subject Areas that answer specific Business questions.
Thanks,
Balaa...

Similar Messages

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

  • Filter on the same logical table source on two logical tables is not working properly

    Hi,
    In the RPD, assume that I have a physical table named Employee_fact, created an Alias called D0 Employee Fact
    In the BMM I've two logical tables called Employee_fact_Type1 and Employee_fact_Type2
    Each of these logical tables has the same Logical table source - D0 Employee
    But in each logical table source, I've a filter in where clause
    such as, for Employee_fact_Type1  employee_type = 'XXX'
                 for Employee_fact_Type2 employee_type='YYY'
    These two facts are present in the same BMM and each of them are connected to two dimensions
    such as
    Dept_type1 <- Employee_fact_type_1 -> Tenure_type1
    Dept_type2 <- Employee_fact_type_2 -> Tenure_type2
    In analysis, When I query the columns from Dept_type1 and Tenure_type1, the database query generated shows the condition employee_type='YYY' instead of employee_type='XXX' .
    But, adding the columns from Dept_Type1, Employee_fact_type_1, Tenure_type1 it shows proper filter.
    I checked the relationships, presentation layer for the sources of presentation tables and everything looks good.
    Can anybody tell me what goes wrong here?

    did you set the content level as well?

  • Dynamically change the Priority Group of Logical Table Sources in OBIEE 11g

    Hi All,
    I have 2 Logical Table Sources(LTS 1 and LTS 2 for a Logical Table in BMM Layer).
    Example: Logical Table : Sample
    LTS Source 1 : Sample 1(Priority Group Set to 1)
    LTS Source 2 : Sample 2(Priority Group Set to 0)
    I have set the Priority Group of Sample 1 LTS Source to 1 and Priority Group of Sample 2 LTS Source to 0.
    I need to dynamically change the Priority Group of Sample 1 LTS Source to 0 if my role is DEVELOPER where role is a column in database.
    If my role is not equal to DEVELOPER then the Priority Group of Sample 1 LTS Source will remain same(1).
    Please suggest how can i achieve this.
    Thanks,
    Soukath Ali

    hello Soukath Ali,
    didi you find a way to dinamically changing Priority Group?
    thanks,
    Maria Teresa Marchetti

  • 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

  • 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

  • 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 :)

  • Multiple Logical Table Sources vs Single Logical Table Source

    OBIEE 11g. I am totally confused. Can someone help me with the following for me.
    I have seen logical table sources being used in 2 ways. I have a 2 sources tables: CUSTOMER & ADDRESS. In physical layer these 2 tables are linked by CUSTOMER _ID in a 1:M relationship.  i.e. A customer can have many addresses.
    Scenario # 1: In BMM the two tables form a logical table called CUSTOMER with 2 different logical table sources which are CUSTOMER & ADDRESS.
    Scenario # 2: In BMM the two tables form a logical table called CUSTOMER with 1 logical table source called CUSTOMER only.
    What is the difference between the above 2 scenarios and which one is better to use when creating the logical table source.
    Regards.

    Scenario # 1: In BMM the two tables form a logical table called CUSTOMER with 2 different logical table sources which are CUSTOMER & ADDRESS.
    -->In this case; based on the columns select source is defined in the physical query
    possible case would be CUSTOMER , ADDRESS, and CUSTOMER & ADDRESS
    -->Used in DE-normalized scenarios
    --> BI uses intelligence based on content tab settings
    Scenario # 2: In BMM the two tables form a logical table called CUSTOMER with 1 logical table source called CUSTOMER only.
    -->In this case; CUSTOMER properties->General tab used both CUSTOMER & ADDRESS, in your physical query both tables present irrespective of column selection
    -->Used in normalized scenarios
    -->Forcing BI to follow our way, since we wont set content tab settings
    Hope this helps

  • 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

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

  • No Fact table Exists and [nQSError: 14070] Cannot find logical table source

    Hi,
    I have 3 tables A(fact),B(dim) and C(dim). there are some other dims. i am getting Errors here.
    A is joined with B and B is joined with C .
    1) In report if i pull columns from A and B its giving data. If i include C table Columns in the report i am getting Error like
    No Fact table Exists.
    2) If i pull the C table columns only in the Criteria i am getting error [nQSError: 14070] Cannot find logical table source
    How can i resolve this.
    Thanks

    In Logical table B source properties general tab ->Click on Add button and add table C and pull required columns from Physical layer table C.
    If helps mark for any issues let me know.
    Edited by: Srini VEERAVALLI on Feb 13, 2013 6:42 AM

  • 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

  • Confused about logical table source

    Hi,
    I'm confused about logical table source(LTS), there are 'General', 'Column Mapping', 'Content' tabs in
    LTS, in General tab ,there are some information,like 'Map to there tables' and 'joins',
    just here, we have created relationships in physical layer and BMM layer, so I would like to ask what's the use of the 'joins' here?

    Hi Alpha,
    Valid query, when you establish a complex join it is always between a logical fact and dimension table.Consider a scenario,
    Example:w_person_dx is an extension table not directly joined to a fact but joins to a dimension w_person_d.
    When you model the person_d tables in BMM, you ll have a single logical table with w_person_d as source.If you have to pull columns from both w_person_d and w_person_dx tables in a report, you add dx table as inner join to persond table in the general tab.Now when you check your physical query, you can see the inner join fired between the two dimensions.
    Rgds,
    Dpka

  • Invalid data from serveral fact logical table sources after upgrade to 11g

    Hi,
    We have a situation after upgrade from 10g to 11g. Answers' querys works fine in 10g environment, but in 11g, generated SQL is not correct.
    Our example is something like that: we have orders fact table, customers and time dimensions. Customer have an hierarchy like: Customer Total -> Customer Country -> Customer Region -> Customer Detail (each level in one different physical table).
    Order's logical table source has two table sources. One sets to Customer Country level, second one Customer Region level, both with different WHERE clauses in Content tab inside LTS configuration. Both at same level of Time dimension.
    The issue is that, at dimension level, SQL is getting correct table to resolve Customer data (Customer Region level), but then, is getting the WHERE clause sets in LTS set to Customer Country level, so we are getting error data. Priority is the same to both LTS at fact table, sets to 0 (default).
    How to know the way Oracle BI Server takes one LTS instead of another one? It's supposed to take the LTS defined at the same granularity level... but is not correct this case.
    Thanks.

    Can you try one of these options:
    Try to set the priority group of lowest granular dimension to 1
    or disable the LTS that is getting the where clause and check if it works fine and then enable again.

  • How to "think" use of multiple logical table sources

    Hi everybody,
    i'm new to OBIEE and its paradigm. I'm trying to build a prototype with multiple physical sources: ERD and a Data Mart; I need OBIEE to go to the Data Mart model at the need of aggregated info and to go to the relational model at the need of transactional info. I need to do that working with dimensions, assigning different sources to each logical level of the dimension.
    My problem begins when thinking how to actually do that. Here is my question:
    - Should I add the relational source in the data mart logical table source folders, mapping the same information with joins? If so, how does dimensions work from that point? (drill down)
    thanks in advance!

    I'm a little confused
    Is the problem
    1 - You want to Access a table in an existing 9i database from a different 10g database
    or
    2 - You have a new 10g database as a copy of a 9i one, and a table called system has gone missing?

Maybe you are looking for