Fact LTS behaviour

Hi
Would like to check if the behaviour that I encountered in Fact LTS is normal.
E.g. Fact A has 1 LTS AB
in LTS AB, there are 2 physical table sources: Table 12 and Table 23
I have 2 measures in Fact A:
1. Measure A, is mapped directly to Table 12
2. Weighted Measure A, is mapped to Table 12 and Table 23 (basically, Table 23 stores weight factor, so this weighted measure is essentially Measure A * weight factor)
Now when I pulll in Measure A only, the SQL generated will bring in Table 23 in the join even though I did not pull in Weighted Measure A.
But for Dimension LTS, the behaviour is different, it will only join to the table only when necessary.
e.g. I have 1 Dimension LTS that joins Product table with Country table and Region table.
So I choose Product ID and Country ID, it'll only join Product and Country tables.
Only when I choose Product ID, Country ID, Region ID, then it'll bring all 3 tables together.
Please advice if this is a known behaviour for Fact LTS
Many thanks

Hi bifacts
Just to clarify, the LTS for the dimension have 3 physical table sources:
1. Product table
2. Country table (joined to Product table)
3. Region table (joined to Product table)
Product ID is mapped to (1),
Country ID is mapped to (2),
Region ID mapped to (3),
So when I select only Product ID, it'll only reference (1),
if I select Product ID and Country ID, only tables (1) and (2) will be referenced in the SQL
Now for the Fact LTS, it has 2 physical table sources:
1. Table 12
2. Table 23 (joined to Table 12)
Measure A is mapped to (1),
Weighted Measure A is based on an expression formula, so it's not really mapped to both table, it's a multiplication of columns from Table 12 and Table 23
Now when I only select Measure A, the SQL generated will reference Table 12 and Table 23. But if we're to follow the behaviour in Dimension LTS, it should only bring in the necessary table, which is Table 12, there's no need to bring in Table 23 in the SQL.
Is the behaviour correct ?

Similar Messages

  • Content level settings in fact LTS

    Hi all,
    i just want to get very clear picture upon content level settings of LTS, when we create a dimensional hierarchy say time hierarchy (Year, Quarter, Month, Day), when we want a measure to sum up to month level we go to that particular measure column in fact and set its content level to month, now i want to know the significance of content level in LTS of the fact table, suppose if i set content level of whole fact table to "month" does all the measures in the fact sum to month level or how it is going to impact the result. In what scenario do we use the content setting in fact LTS?
    Many Thanks,
    Sreekanth

    Hi,
    @Kishore
    thank you for quick reply, to get more clarity now lets assume we have one fact table with daily granular data and one aggregate table with month granular data, so when i drag and drop aggregated measures to BMM it creates another LTS for aggregate table, in that aggregate table we would set the content level as "MONTH" so whenever a report is constructed based on month columns and measures, BI Server picks aggregate table since it has LTS at month level. Is my understanding correct?
    Now, i have a connecting question.. we have monthly aggregate table which has 2 columns:
    1. MONTH_CODE (1999-01,1999-02,...)
    2. SALES_AMT
    now if i join TIME_DIM.MONTH_CODE = AGGREGATE_TABLE.MONTH_CODE
    time dimension (TIME_DIM ) has records with day granularity so there will be 31 "1999-01" in TIME_DIM, this will result in summing up same measure value 31 times, so this will result in high numbers, so in this case what would be the ideal join condition to be used between aggregate table and time dimension, or what is the ideal join column to be used in aggregate table for joining to time dimension at day level.
    Much appreciated...
    Sreekanth

  • Getting Warning while adding Dimension table to FACT LTS

    Hi,
    While i am applying join betwwen fact and Dimension at BMM level, i am getting warning as there is no join with Fact Source, even though i provided join there.
    Can any one help in this.
    thanks
    Manu

    Hi
    Make sure you have set the Content Level of all LTS of all Fact Tables...
    Double click on LTS of fact, go to Content Level --> change to Logical Level to 'Column (or) Detail Level'
    then u will not get warnings..
    Please mark helpful or correct if this helped you out

  • 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

  • Join multiple fact tables and dimensions and use all tables in report issue

    Hi,
    I have a report requirements and need to use multiple fact tables and unconformed dimensions as described below
    Fact table: F1,F2,F3
    Dimensions tables: D1.....D9
    F1:(joined to) D1,D2,D3,D4
    F2::(joined to)D1,D2,D5,D6
    F3::(joined to)D1,D2,D7,D8
    D7::(joined to)D9,D8 (dimension D7 joined to two other dimensions D9 and D8
    I'm trying to use columns from almost all the fact and dimension tables but getting "Unable to navigate requested expression. Please fix the metadata consistency warnings."
    Repository is consistent and no errors and warnings.
    How can I configure the repository to develop reports using all fact tables and dimensions?
    Appreciate for your help.
    Thanks
    Jay.
    Edited by: Jay on Feb 9, 2012 4:14 PM

    So you want me to convert snowflake schema to star. does it solve my problem? individual star queries are working find but when I query multiple stars together getting inconsistency errors. I removed content tables dim level totals for unconformed dimensions in logical fact LTS and set level for measures at total level for unconformed dimensions. it is still in progress and need to test.
    Thanks
    Jay.

  • No fact table exists at the requested level of detail Error.

    Hi Everybody,
    Facing a issue on the using  Fact less Fact tables.
    Scenario:
    ========
    Using two subject areas to develop a report.OBIEE 11g
    Fact1 --> Compensation Plan Assignments Real Time
    Fact2 --> Participant Detail Real Time"."Participant Details
    On both facts we created dummy metrics on respective table id's and aggregated to ROWCOUNT.
    As i said in earlier we are using the above 2 subject areas to develop reports.
    Logical SQL:
    ===========
    SELECT
    0 s_0, "Incentive Compensation - Compensation Plan Assignments Real Time"."Role"."Role Name" s_1,
    "Incentive Compensation - Participant Detail Real Time"."Participant Details"."Cost Center" s_2,
    "Incentive Compensation - Participant Detail Real Time"."Participant Details"."Country Code" s_3,
    "Incentive Compensation - Participant Detail Real Time"."Participant"."Participant First Name" s_4,
    "Incentive Compensation - Participant Detail Real Time"."Participant"."Participant Last Name" s_5,
    "Incentive Compensation - Participant Detail Real Time"."Participant"."Party Number" s_6
    FROM "Incentive Compensation - Earnings Real Time" FETCH FIRST 65001 ROWS ONLY
    Error Message:
    ==============
    Expression 'RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]' converted to NULL because [nQSError: 14020] None of the fact tables are compatible with the query request RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]..
    [2013-10-21T12:18:45.000-05:00] [OracleBIServerComponent] [TRACE:2] [USER-34] [] [ecid: 004uJx90aHO9lZ73VJJNB80007eh000gl_,0:2:1:9:5] [tid: 457c2940] [requestid: f2e001b] [sessionid: f2e0000] [username: [email protected]] -------------------- Query Status: [nQSError: 14025] No fact table exists at the requested level of detail:
    Please share some ideas on this or any guidelines will be very much helpfull.

    Govardhan,
    Did u configured any Dimension Hierarchy please set the levels in that particular Fact LTS.
    For more info,check the below thread
    https://forums.oracle.com/thread/2134934
    Thanks,

  • No Fact Table exits at the requested leve of detials

    Hi All,
    I am getting the follwoing error..while am into Oracle Answers...
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 14025] No fact table exists at the requested level of detail: [[AP Invoice Payments.Payment Terms.Payment Term Name],,,,,,,,,,[Suppliers.Suppliers.Supplier Name],,,,,,,,]. (HY000)
    SQL Issued: SELECT 0 s_0, "Business Area : Accounts Payable"."Payment Terms"."Payment Term Name" s_1, "Business Area : Accounts Payable"."Suppliers"."Supplier Name" s_2 FROM "Business Area : Accounts Payable"
    any ideas to correct this problem ?
    Thanks in advance,

    Hi,
    You have to go to the fact LTS and set granularity for each dimension associated with it. You might be bringing a column from a dimension in your report, for which you didn't set up granularity in the facts LTS.
    Thanks
    Venkat
    OBIEEDeveloper

  • No fact table exists at the requested level of detai error

    Hi Gurus,
    Gud Evening,
    There is a report with 10 columns and its coming fine when ever we are adding new column some date column (Start Date) it is showing the below error
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 14025] No fact table exists at the requested level of detail:
    Can any give some suggestions..
    Regards

    Hi,
    You have to go to the fact LTS and set granularity for each dimension associated with it. You might be bringing a column from a dimension in your report, for which you didn't set up granularity in the facts LTS.
    Thanks
    Venkat
    OBIEEDeveloper

  • Again: two facts and one conformed dimension

    Dear all,
    I know this has been asked quite often but I haven't found a solution for my problem here. Believe me I have done a lot of searching across the net ..
    What I want to do is the following:
    I have two fact tables with a number of common dimensions. A report should show the two facts across these common dimensions.
    To keep it simple I start with only one common dimension.
    Here's what get's to the db from OBIEE:
    *SELECT Revenue."Date (YYYYMMDD)" saw_0, Sales."Day Day Code" saw_1, Revenue."TPV (Total Payment Volume in Millicent [€])" saw_2, Sales.DEBIT_AMOUNT saw_3 FROM "Company KPIs" ORDER BY saw_0, saw_1, saw_3*
    Note that *Revenue."Date (YYYYMMDD)"* and *Sales."Day Day Code"* are the same field from the common time dimension. I just put them in different presentation tables for the end users.
    TPV and DEBIT_AMOUNT are facts from the two different cubes.
    Everything fine, right?
    Now I look at the nqquery.log:
    RqList
    Dim Time.Day Day Code as c1 GB,
    Dim Time.Day Day Code as c2 GB,
    *Tpv:[DAggr(Cube Revenue.Tpv by [ Dim Time.Day Day Code, Dim Time.Day Id, CUBE_SALES.DEBIT_AMOUNT] )] as c3 GB,*
    CUBE_SALES.DEBIT_AMOUNT as c4 GB,
    Dim Time.Day Id as c5 GB
    OrderBy: c1 asc, c2 asc, c4 asc
    now the bold thing looks odd to me. Is he trying to aggregate one cube based on the other? Could be the problem, but where to influence this?
    And finally this translates into this query:
    WITH
    SAWITH0 AS (select distinct T4110.DEBIT_AMOUNT as c1,
    T281.DAY_DAY_CODE as c2,
    T281.DAY_ID as c3
    from
    DIM_TIME T281,
    CUBE_SALES T4110
    where ( T281.DIMENSION_KEY = T4110.DIM_TIME ) ),
    SAWITH1 AS (select distinct SAWITH0.c2 as c1,
    SAWITH0.c2 as c2,
    *cast(NULL as DOUBLE PRECISION ) as c3,*
    SAWITH0.c1 as c4,
    SAWITH0.c3 as c5
    from
    SAWITH0)
    select SAWITH1.c1 as c1,
    SAWITH1.c2 as c2,
    SAWITH1.c3 as c3,
    SAWITH1.c4 as c4
    from
    SAWITH1
    order by c1, c2, c4
    As you see, the tpy ist gone and a NULL appears. That's what I see in the report. TPV is always NULL.
    So where did I miss a configuration ???
    Thanks, Knut

    You only need to set the content levels on the measures themselves when you want non-conformed dimensions in the report, as your working with fully conformed dims just make sure your levels are set on the content tab for each Logical Table source in the Logical fact table. Leave the non-conformed dim hierarchies as blank.
    Remember - You should put a hierarchy on each logical dim , even if there is no real hierarchy, just have a total -> Detail.
    You should always always always set your content levels for logical table sources, both in Dimensions and Logical fact LTS's.
    If they are greyed out, make sure your not in read only, have checked the object out if on-line mode, failing that, perform the changes off-line then re-start your BI Server.

  • Creating dimension with several LTS problem

    Good morning fellow experts,
    I've hit the following issue - I have two dim tables that I have no problem using separately, however, I want to merge them into 1 dimension for better drill-down capability. Here's the structure:
    Table1 "Geo Dim" fields: location_id (Primary key), Country, State, City, Zip, Address, Name (lowest level)
    Table2 "Buildings Dim" fields: building_id (Primary Key), location_id (could be FK to Table 1), Building Name
    Fact table has building_id as FK
    The goal is to be able to drill from Country to Individual Building. I also know that ideal variant is to create a view and merge the 2 dim tables, however, I'm doing a POC incorporating snowflake. I used this wonderful link (courtesy of Adrian Ward) http://majendi.blogspot.com/2009/01/obiee-snowflakes-and-stars-part-3.html as a guidance, however, I hit some problems. My question is - what's the proper way to model it in physical layer. Here's how I've currently designed it:
    Physical:
    Fact >-- (building_id key) Buildings >-- (location_id key) Geo
    Logical Star:
    Fact (with fact LTS) >--complex join Building_Geo
    Building_Geo has 1 LTS with 2 mapped tables. A custom hierarchy is built. Logical key is building_id. Should I use 2 LTS instead of 1 and set hierarchy levels to a) building b) geo ?
    Can someone point me as to what's wrong in this schema? It's resembling Header-Detail a lot - and I'm sensing that I'm just missing a small piece somewhere. Thanks

    Hi mma,
    My first solution started to work once I created/defined all hierarchical keys (simply dragging them wasn't enough and I missed that) . BI had no problem with single LTS for 2 mapped tables and generating correct sql. So, just a follow-up question - how does dimensional hierarchy behave in BMM if you don't define keys (I'd guess it'd throw a RPD consistency error). Also, Mma, do you think such schema would work when more dims would get thrown in? Also, except for circular joins - what other pitfalls might be there?
    Physical:
    Fact >-- (building_id key) Buildings >-- (location_id key) Geo
    Logical Star:
    Fact (with fact LTS) >--complex join Building_Geo
    I marked as answered - but would appreciate if you could answer 1 more time.

  • LTS Problem

    Hi,
    I've a fact table which is having 4 Agg logical table source (LTS), in each LTS having same 4 columns . When i gave level as 'MOnth' for all 4 Agg logical table source (LTS). On what basic BI server will hit ? Which table is going to hit. Is there any logic behind hit, what if i want to hit on specific table.
    Thanks,
    Malli

    user10675696 wrote:
    Hi,
    I've a fact table which is having 4 Agg logical table source (LTS), in each LTS having same 4 columns . When i gave level as 'MOnth' for all 4 Agg logical table source (LTS). On what basic BI server will hit ? Which table is going to hit. Is there any logic behind hit, what if i want to hit on specific table.
    Thanks,
    MalliEssentialy the decision process is as follows :
    1) Decide which LTSs which map to the required fields in the request
    2) Determine combinations of Dim & Fact LTSs which work together (joins and levels)
    3) Identify Fact LTS with highest grain, defined in your content tab
    4) If tied, it then picks the top most LTS from the Logical fact.
    You can manipulate the # of elements at your hierarchy levels to force the choice if you desire.
    Im not 100% sure but the rowcount in the physical layer might have an effect if your talking about different aggregate tables.

  • Possible to automount AEBS HD

    My configuration includes an iMac running Mac OS 10.7.5, an Apple Extreme Base Station
    with a partitioned USB hard drive connected to it, and various other machines wirelessy connected. I am
    trying to configure the hard drive so that its volumes are accessible with different permissions
    depending on the user. I want this configuration to survive a restart and wake scenario.
    It appears to me that the only configuration workable with Lion and networked drives is for open
    (Read Write access) access for all users that mount the drive (or any of its volumes). This involves
    simply accessing the server via command-K and supplying the password.
    A permanent configuration via some automount solution has been raised in a number of queries
    and I have tried all the solutions to no avail. An example of a more comprehensive thread is:-
    https://discussions.apple.com/thread/3221944?start=0&tstart=0
    I have tried using the fstab and automount solutions (using a mount map file) but they both result in
    root mounted volumes. It seems some regression was introduced in Lion that has broken the auto-mounting of
    networked drives (note, mounting the drives using mount_afp works fine).
    I wonder is anyone aware of a solution and more importantly, for Mountain Lion users, does this problem still exist ?
    If I upgrade to ML will this allow an auto-mount configuration?
    Notes
    ====
    For anyone with the time to try on ML, the fstab mods are of the form (man fstab):-
    <Id of Vol. to mount> <Mount Point> <fstype> <options> <dump param> <fsck pass no.>
    192.168.0.3:/Iomega-100GB /Volumes/myIomega-100GB url rw,auto,automounted,url=="afp://username:[email protected]/Iomega-100GB/" 0 0
    Where username is login name and password is the disk password set via AirPort Utility.
    Mods to fstab can be tested via sudo automount -vc (avoids reboot etc.). Can then delete/reset fstab and re-run this command to
    get system back to previous state.
    Console application will show some errors and info.
    From man documentation and console output, the above fstab mod leads to the invocation of mount_afp.
    I can see that there are potential issues with this approach. Such as, how does the username/pw apply to other users?
    Given this mount will take place during a boot then volumes could at most be potentially available to users
    with the final stage of credential checking only taking place at the point of use of volumes. This would explain
    why mount_afp works (there are no ambiguities of who the user is).
    From the automount documentation I have noticed that there is an 'executable map' option that allows conditional
    mounting of volumes. I have not explored this as I don't understand the root mount behaviour (where this executable
    option is likely to lead!).

    Thanks VikingOSX. The Apple info is basic and does not cater for giving each user different permissions to the volumes (as you would normally expect from a standard ownership model .. in fact, the behaviour you get when you plug the drive directly into the machine). I want to be able to mount a drive as a network drive such that its ownership is respected. I can see that this would entail some form of matching users across a network in order to establish the 'owner'.
    I have tried dragging drive icon into the account login items however, this does not address file ownership. It just provides open access to that user. I have read in some threads that MacOS X works on the basis of a floating ownership whereby whoever mounts the drive gets R/W access to all files. This looks like what I am seeing.
    I am beginning to think the type of functionality I am looking for is more in the realms of OSX Server ?

  • Content level setting in OBIEE 11g

    Hi,
    i am new to obiee 11g.i have an doubt in setting up the content level setting in BMM layer.i have given details level in fact LTS content tab with help of physical join,i dont get any error but while trying to generate reports i am getting an error "None of the fact table is compatible with the requested level".where i am commiting mistake,do i need to set content llevel based on physical join or logical join scenario.kindly help regarding this.
    thanks in advance!
    Edited by: Nandha on 10 Jan, 2012 10:55 PM

    Hi Nanda,
    We set the content level of logical source based on the granularity of the source.
    Say, a product hierarchy is like
    Category -> Sub Category -> Product
    Say one of your dimensions has Product information, for this source set the level as 'Product'
    Say there is an aggregated source which has Category information, set the source level as 'Category'.
    Hope this helps you to set your levels.
    Thank you,
    Dhar

  • Logical Key for Degenerate Dimension

    Hi Gurus,
    Need some help on the degenerate dimensions in the BMM layer.
    I have one fact table with dimension attributes and I would like to move the attributes into separate logical table and treat it as dimension.
    Now my newly created dimension has the Fact LTS and I would like to assign a logical key to the newly created table and then create the logical dimension.
    Can anyone provide some inputs on we can assign the logical key to the column?
    Thanks

    Hi Srini,
    Since my main logical fact table consists of two LTS and the dimension being created from this table will also have 2 LTS, the content level will be set to all levels on which the fact is joined.
    So I would like to create a logical dimension based out of my dimension and then assign the content level at the detail level.
    Please let me know if I am not clear.
    Thanks

  • Warning - 39008 in Oracle BI

    Hi,
    I'm getting the following warning. [39008]Logical Dimension table <dim table name> has a source <source table name> that does not join to any fact source.
    I've done the following.
    1. There are physical joines between the source tables.
    2. I've also specified the Facts LTS's content tab.
    Please help in resolving this error.
    Thanks in advance.
    Regards
    Ajay

    Hi Ajay
    There are a few things you could check when this error occurs.
    * There should be a physical (foreign key) join between the Logical Table Sources,
    * There should be a complex join between the logical tables.
    * The granularity between the dimension and the fact table should match. You could check this on the content tab (Aggregation content, group by) of the Logical Table Source.
    Good Luck,
    Daan Bakboord

Maybe you are looking for