Logical Level in Content Tab

Hi,
What is the use of Logical Level under Content Tab in Logical Table Source?
Need more information, docs related to this
Thanks,
Satheesh

Hi
This logical level is useful for level bases metrics.It shows the levels in your hierarchy.We can give the level in this and in the report it shows the data for that level only.
See this lnk, http://gerardnico.com/wiki/dat/obiee/measure_level_based
Thanks
Don

Similar Messages

  • Logical level in Fact tables - best practice

    Hi all,
    I am currently working on a complex OBIEE project/solution where I am going straight to the production tables, so the fact (and dimension) tables are pretty complex since I am using more sources in the logical tables to increase performance. Anyway, what I am many times struggling with is the Logical Levels (in Content tab) where the level of each dimension is to be set. In a star schema (one-to-many) this is pretty straight forward and easy to set up, but when the Business Model (and physical model) gets more complex I sometimes struggle with the aggregates - to get them work/appear with different dimensions. (Using the menu "More" - "Get levels" does not allways give the best solution......far from). I have some combinations of left- and right outer join as well, making it even more complicated for the BI server.
    For instance - I have about 10-12 different dimensions - should all of them allways be connected to each fact table? Either on Detail or Total level. I can see the use of the logical levels when using aggregate fact tables (on quarter, month etc.), but is it better just to skip the logical level setup when no aggregate tables are used? Sometimes it seems like that is the easiest approach...
    Does anyone have a best practice concerning this issue? I have googled for this but I haven't found anything good yet. Any ideas/articles are highly appreciated.

    Hi User,
    For instance - I have about 10-12 different dimensions - should all of them always be connected to each fact table? Either on Detail or Total level.It not necessary to connect to all dimensions completely based on the report that you are creating ,but as a best practice we should maintain all at Detail level only,when you are mentioning any join conditions in physical layer
    for example for the sales table if u want to report at ProductDimension.ProductnameLevel then u should use detail level else total level(at Product,employee level)
    Get Levels. (Available only for fact tables) Changes aggregation content. If joins do not exist between fact table sources and dimension table sources (for example, if the same physical table is in both sources), the aggregation content determined by the administration tool will not include the aggregation content of this dimension.
    Source admin guide(get level definition)
    thanks,
    Saichand.v

  • Logical level for logical fact table sources

    it is clear that for fact aggregates, we should use the Content tab of the Logical Table Source dialog to assign the correct logical level to each dimension.
    question is : is it mandatory to assign even for non-aggregates fact tables the logical level for each dimension (which normally should be set to the most detailed level of each dimension) ? is it any known issue if "logical levels"in content tab are not set ?
    the reason I'm asking this is a strange bug I have (I'm not going to discuss it here) and then only workaround seems to be NOT setting the logical levels (on content tab) for logical fact table sources.
    thank you !

    If levels are not set: By default levels are considered as lowest level
    It should not matter if you set or not
    Generally we set for facts explicitly when we are using Aggregate tables.
    Your current issue might be a case by case; I would suggest to check implicit fact, any table mapped to the source to force a join etc
    Mark if helps
    Let me know how it helps
    Edited by: Srini VEERAVALLI on Feb 5, 2013 8:33 AM
    Any updates on this?+_
    Edited by: Srini VEERAVALLI on Feb 14, 2013 9:09 AM

  • Setting aggregation content for logical level in 11g

    Hi Guys,
    When working on with horizontal and vertical federation in OBIEE 11g with multiple data sources here in my case it is essbase and RDBMS.
    1) pulled the columns and dragged into the concerened table.
    2) The related heirarchies have been defined.
    3) when trying to go to one of the LTS and trying to set the logical level aggregation im not able to see the levels columns corresponding nor im getting the get levels option to get them. where am i going wrong?
    when im trying to join a fact by pulling it on to the fact...i can see the levels in content tab,but when i try to define levels and check it its giving me error "There are no levels matching the BI algorithm"
    Any answers wud be appreciated.
    TIA,
    KK
    Edited by: Kranthi.K on Sep 5, 2011 2:52 AM

    It is autocreated,i dint customize it.....Im dropping the RDBMS table onto the Essbase cube dimension table and im not getting the RDBMS content levels that should be defined in the LTS of the table,and the RDBMS table has an level based hierarchy but still no sucess.
    Any more ideas
    UPDATED POST
    Deepak,it was not helpful as i have gone through tht document before....Im trying it in all scenerios to figure out where actually it is going wrong.
    If i dont find the path,i will let you kne what im trying to do so you can help me out.
    UPDATED POST-2
    Any more pointers from the experts.
    Edited by: Kranthi.K on Sep 6, 2011 7:01 AM

  • Setting Logical Level in LTS

    Hi all,
    Usually we set the Logical Level (Content Tab) for the LTS in the Fact table.
    Is there any best practice to set it for the LTS in Dimension tables too? If yes, why do we do that?
    Please clarify on this. This is very urgent.
    Regards.

    one thing is If you have multiple LTS in a single dimension like detail dim and aggregated dim. then you have to set the content levels for each LTS. Its always a good practice to mention which level the dimension is in any case.

  • What is the content Tab

    Hi All,
    We have just started using OBIEE as a business intelligence solution and I am in a process of creating RPD for our current data model. However, as I have gone through the official oracle documentation and various posts but I am still not sure what is the CONTENT tab of an LTS signifies logically?
    Can anyone please elaborate upon this with a small example or direct me to a more precise documentation with an example?
    I will be highly thankful.
    Thanks,
    Ronny

    Thanks but it's not mandatory
    and give only those who
    want.
    If it was possible for me, I will give you a little
    bit of point because I'm now sure that you
    can't use the tab content of an lts for a level based
    measure ;-)
    good evening and go Netherlands !

  • Content Tab: None of the fact tables are compatible with the query request

    Hi All,
    **One thing I am not clear yet of all my years with OBIEE is working with the content tab in BMM.**
    I have made a rpd the joins in physical layer as shown below:
    https://picasaweb.google.com/114804305606242416264/OBIEEError#5663056545119428530
    And the BMM layer as:
    https://picasaweb.google.com/114804305606242416264/OBIEEError#5663056519553812930
    Error I am getting when i run a request from the 3 columns from the selected 3 tables is:
    Dim - Comment Code Details
    Fact - Complaint
    Dim - Service Details
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14020] None of the fact tables are compatible with the query request Sr Num:[DAggr(Fact - Complaint.Sr Num by [ Dim - Service Details.Sr Cat Type Cd, Dim - Comment Code Details.Cmtcode name] )]. (HY000).
    I get no error for consistency.. I read everywhere and I know i need to set the appropriate aggregation levels in the various dims and facts LTS properties to help OBIEE understanding our model, but how to do that.. how do i decide... how should I approach, what should be the aggregation level, what details.
    When i click More button i see different options: Copy, Copy From, Get Levels, Check Level, what do these mean.
    Aggregation Content, group by - Logical Level or Column which one should i choose and how should I decide.
    Can anyone explain the Content Tab in details and from scratch with some example and why we get these errors.... I know many people who are well versed with many other things related to RPD but this. A little efforts of explaining from you guys will really be appreciated.
    Thanks in advance,
    Dev

    Hi Deepak,
    Option 1:
    My tables in physical layer are joined as below:
    D1--> F1 <--D2--> F2 <--D3
    Same way i model it in BMM
    D1--> F1 <-- D2--> F2 <--D3
    Here D1 is non Conformed Dimension for F2 and D3 is non Conformed dim for F1. Later create Dimensional hierarchies, I tried setting up the content levels
    I go Sources>content tab of Fact F1 I set
    Dimensions----------- Logical level
    D1---------------------- D1 Detail
    D2---------------------- D2 Detail
    D3---------------------- D3 Total
    then, I go Sources>content tab of Fact F2 I set
    Dimensions----------- Logical level
    D1---------------------- D1 Total
    D2---------------------- D2 Detail
    D3---------------------- D3 Detail
    Then, I also go in all the dimensions and set their content levels to Details, but it still gives me errors not sure where I am going wrong in setting the content levels.
    I need to know whether the way I have modeled it in BMM is right,
    Option 2:
    I can combine the two facts in a single Logical Fact or the above design should also work.
    (F1&F2)<--D1, D2 , D3 joined separately using complex logical joins.
    what will be the content tab details?
    Thanks,
    Dev

  • Content tab in LTS

    Hi Experts,
    What is the purpose of content tab in the logical table source(LTS) after mapping the columns in the LTS why we have to set the logical level for the dimension if we won't set what will happens.
    Please let me know with good scenario for better understanding.
    Regards,
    Edited by: RAJ.bi on Jan 22, 2013 7:57 PM

    To use a source correctly, the Oracle BI Server has to know what each source contains in terms of the business model. Therefore, you need to define aggregation content for each logical table source of a fact table. The aggregation content rule defines at what level of granularity the data is stored in this fact table. For each dimension that relates to this fact logical table, define the level of granularity, making sure that every related dimension is defined.
    Good scenario is Fact table and Aggregate fact table.
    If helps pls mark
    Edited by: Srini VEERAVALLI on Jan 22, 2013 9:57 PM
    updates?
    Edited by: Srini VEERAVALLI on Jan 24, 2013 7:16 AM

  • If Logical level mappings are blank in an LTS , what does it mean?

    Hi All,
    I was trying to find this out in the forum but couldn't.
    In my LTS, on the content tab, if i don't specify any "Aggregation, group by" information for the dims associated with my Fact table and keep it blank, then what does it mean? Would OBIEE treat this as at the detail level by default? So to test this, I created a logical fact and for its LTS, i didn't associate any logical level for dimensions. The query didn't give me any error and worked fine by using the correct join details.
    Also when do we associate an LTS with the Total Level for a dim, what's the use because as I understand, this means all our measures from that LTS would be calculated for the total level of the dim and we can do this by creating level based measure and associating it with the total level of the dim.
    I'll be thankful if somebody could explain me this in detail or direct me to a relevant documentation/ blog
    Thanks,
    Ronny

    Hi,
    When you have only one logical Table Source(LTS).
    You don't specify the logical levels. By default it would consider the detail level of the logical levels mapped to the fact table.
    When you have Multiple logical Table Source(LTS).
    The concept of Multiple LTS comes into picture when you have multiple sources. The BI server picks the optimum logical source depending upon the fields (columns) selected. And also depends on the Number of element set while creating the dimension hierarchies. Refer-http://gerardnico.com/wiki/dat/obiee/level_number_element
    For example- Suppose you have two logical table source Fact 1 and Fact 2 and logical levels( dimension hierarchies are created for two dimensions Dim 1 and Dim 2).
    For the first Fact 1 source logical level is mapped only with Dim 1 and Fact 2 is mapped to Dim 2.
    (You need to decide which fact source to hit depending upon the dimensions used in the report.)
    Then in the report when you select Dim 1 (by means of column selector/filters) then Fact 1 source will be hit and same appears in the query.
    Then in the report when you select Dim 2 (by means of column selector/filters) then Fact 2 source will be hit and same appears in the query.
    One more situation where you have mapped Fact 1 with Dim 1 First level of aggregation and Fact 2 with Dim 1 with Detailed level. Then the BI server picks depending upon the user's request. If the request data can be pulled from the detailed level ( which tends to be optimum then picks from the second source).
    So, its always better to set the logical source and check the query, if its hitting the correct sources according to the requirements.
    Regards,
    MuRam

  • About the content tab

    Hi All,
    Can anyone telll me what is the function of where filed in Content tab with example. It will be great help for me.
    Thanks a lot in advance.

    Forum search.
    difference of ‘Specify Fragmentation Content’  and ‘where clause Filter ‘ ?
    Use for filtering current logical table source (target physical table). Advanced use with aggregation content dimension logical level. For examples search forum, blogs, etc. You can find plenty of information.
    Regards
    Goran
    http://108obiee.blogspot.com

  • 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

  • Use of New logical Level Key in OBIEE

    Hi all,
    can anybody tell me what is the use of newlogicallevel key in hierarchies(OBIEE).
    why we need to set a newlogical level key for each level in hierarchies.
    pls explain in detail....
    regards
    bharath

    You may get info as below if you use Admin tool help file
    Level keys. Each logical level (except the topmost level defined as a Grand Total level) needs to have one or more attributes that compose a level key. The level key defines the unique elements in each logical level. The dimension table logical key has to be associated with the lowest level of a dimension and has to be the level key for that level.
    A logical level may have more than one level key. When that is the case, specify the key that is the primary key of that level. All dimension sources which have an aggregate content at a specified level need to contain the column that is the primary key of that level. Each logical level should have one level key that will be displayed when an Answers or Intelligence Dashboard user clicks to drill down. This may or may not be the primary key of the level. To set the level key to display, select the Use for drill down check box on the Level Key dialog box.
    Be careful using level keys such as Month whose domain includes values January, February, and so on—values that are not unique to a particular month, repeating every year. To define Month as a level key, you also need to include an attribute from a higher level, for example, Year. To add Year, click the Add button in this dialog and select the logical column from the dialog that is presented.

  • How to set different navigation items for each content tab in xMII portal

    Hi,
    Scenario : I have added three content tabs in the xMII portal.
    I want to change the items in the navigation tree when each of the content tabs are selected.
    How is this possible?
    Please help.

    Vaishali,
    The built-in navigation tree is not intended for this sort of thing, where just like with the tabs it is intended to provide role/user based content links.
    You would be better off having your content tab link pass a criteria to the default target frame and allow a web page to give you the second level of dynamics.  Your content tab links could be something quite simple like "Page.irpt?Tree=1", "Page.irpt?Tree=2", "Page.irpt?Tree=3" and your irpt page would receive the Tree property and you could react accordingly in your web page.
    Regards,
    Jeremy

  • Logical Difference of defining Multiple Logical level keys

    Hi All,
    We add logical level keys in BMM layer by right cliking the logical level column of a dimesional hierarchy, doing so defines a new logical key, i already have another logical level column defined as logical level key.
    When i double click on logical level hierarchy, it has keys tab where i have two keys now.
    say the two keys are: "channel desc key" and "channel id key"
    My question is in one key say "channel id key" if we click edit, i am getting all the columns including channel desc column, so if i click it as key, it forms a composite key of (channel id) + (channel desc) inside "channel id key". Then what is the use of maintaining another key = "channel desc key"
    Is there any logical difference of ("maintaining two keys having single column defined as key in either of them") and ("maintaining one key having two logical columns defined as keys in a single logical level key")?
    Thanks in Advance.
    Regards,
    Sreekanth.

    Hey got the answer, there is a difference, if i add multiple columns as keys under a single logical level key, they both come under one key and its drill down on both the columns, i cannot select selectively out of which column of the two drill down is applicatble.
    If i create two different logical keys for two columns i can selectively choose which column drill down is applicable to.
    Drill Down is based on "Logical Level Key" not on Logical Level Column selected as key.
    Thanks,
    Sreekanth.

  • Content tab for a fact table

    Hi
    Please , help me in knowing the use of content tab for a fact table in the repository in OBIEE.
    Thanks.

    if you have multiple LTS then you should set the content level approprately otherwise you can get errors during consistency checks.not able to find any link which talks only about content level.see these links and let us know if you have any doubts
    http://kr.forums.oracle.com/forums/thread.jspa?threadID=604637
    Content tab is also handy when you are using aggregate tables.
    Regards,
    Sandeep

Maybe you are looking for