OBIEE Hitting incorrect fact table

Hi,
I have two Fact tables joined with 3 Dimensions..
F1 - D1, D2, D3
F2 - D1, D2, D3
Now I added another dimension D4 and joined it with F2.
While taking D1, D2 D3 while it use to get F1 in the Query now, it started taking F2 and showing incorrect results.. How can this be fixed?

Dont blame OBIEE!! You haven't configured it correctly.
Try to set implicit fact column setting on Subject area. That might help you.
If helps mark

Similar Messages

"AP Transactions" Subject Area hitting incorrect Fact table

Hi Gurus,
Requirement/Background:
We have done some customization to "Financials - AP Transactions" subject area i.e. adding 3 new W_DAY_D aliases in physical layer and few custom columns in W_AP_XACT_F.
I did not create any new BMM tables for new W_DAY_D aliases, just added these new tables in LTS (Fact_W_AP_XACT_F) under "Dim - AP Transaction Details", and put all the custom columns under same Logical table i.e."Dim - AP Transaction Details" mapping correctly to W_DAY_D and W_AP_XACT_F.
Problem Statement :
Whenever I add "Purchase Invoice Number" to the query, it hits incorrect fact table i.e.W_AP_AGING_INVOICE_A and gives incorrect results.
Expected Query : (if I select GL Account Number, Purchase Invoice Number & AP Amount)
select sum(T333486.AP_LOC_AMT * -1) as c1,
               sum(T333486.AP_DOC_AMT * T333486.GLOBAL1_EXCHANGE_RATE * -1) as c2,
               T333486.PURCH_INVOICE_NUM as c3,
               T334337.GL_ACCOUNT_NUM as c4
          from
               W_AP_XACT_F T333486 /* Fact_W_AP_XACT_F */ ,
               W_GL_ACCOUNT_D T334337 /* Dim_W_GL_ACCOUNT_D */
          where ( T333486.GL_ACCOUNT_WID = T334337.ROW_WID and T333486.PURCH_INVOICE_NUM = '1161/13 CH' and T333486.DELETE_FLG = 'N' )
          group by T333486.PURCH_INVOICE_NUM, T334337.GL_ACCOUNT_NUM
Current Query it is firing :
select sum(T333486.AP_LOC_AMT * -1) as c1,
               sum(T333486.AP_DOC_AMT * T333486.GLOBAL1_EXCHANGE_RATE * -1) as c2,
               T348360.PURCH_INVOICE_NUM as c3,
               T334337.GL_ACCOUNT_NUM as c4
          from
               W_AP_XACT_F T333486 /* Fact_W_AP_XACT_F */ ,
               W_GL_ACCOUNT_D T334337 /* Dim_W_GL_ACCOUNT_D */ ,
               W_SUPPLIER_ACCOUNT_D T336997 /* Dim_W_SUPPLIER_ACCOUNT_D */ ,
               W_STATUS_D T338711 /* Dim_W_STATUS_D_Generic */ ,
               W_XACT_TYPE_D T338741 /* Dim_W_XACT_TYPE_D_Financials */ ,
               W_DAY_D T344857 /* Dim_W_DAY_D_Payment_Due_Date */ ,
               W_DAY_D T348434 /* Dim_W_DAY_D_Purchase Invoice Date */ ,
               W_DAY_D T351452 /* Dim_W_DAY_D_Purchase Invoice Cleared_Date */ ,
               W_PAYMENT_METHOD_D T394960 /* Dim_W_PAYMENT_METHOD_D_AP */ ,
               W_XACT_SOURCE_D T394984 /* Dim_W_XACT_SOURCE_D */ ,
               W_AP_AGING_INVOICE_A T348360 /* Fact_W_AP_AGING_INVOICE_A */
          where ( T333486.GL_ACCOUNT_WID = T334337.ROW_WID and T333486.SPLR_ACCT_WID = T336997.ROW_WID and T333486.DOC_TYPE_WID = T338741.ROW_WID and T333486.DOC_STATUS_WID = T338711.ROW_WID and T333486.INVOICED_ON_DT_WID = T348434.ROW_WID and T333486.PAY_METHOD_WID = T394960.ROW_WID and T333486.CLEARED_ON_DT_WID = T351452.ROW_WID and T333486.PAYMENT_DUE_DT_WID = T344857.ROW_WID and T333486.SOURCE_WID = T394984.ROW_WID and T333486.DELETE_FLG = 'N' and T344857.ROW_WID = T348360.PAYMENT_DUE_DT_WID and T336997.ROW_WID = T348360.SPLR_ACCT_WID and T338711.ROW_WID = T348360.DOC_STATUS_WID and T338741.ROW_WID = T348360.DOC_TYPE_WID and T348360.PURCH_INVOICE_NUM = '1161/13 CH' and T348360.PAYMENT_METHOD_WID = T394960.ROW_WID and T348360.INVOICED_ON_DT_WID = T348434.ROW_WID and T348360.CLEARED_ON_DT_WID = T351452.ROW_WID and T348360.SOURCE_WID = T394984.ROW_WID )
          group by T334337.GL_ACCOUNT_NUM, T348360.PURCH_INVOICE_NUM
"Purchase Invoice Number" is out-of-box present under "Dim - AP Transaction Details" and it is mapped to 4 tables including W_AP_XACT_F & W_AP_AGING_INVOICE_A. It is also set at Detail level in AP Transactions dimension hierarchy.
Additionally, implicit fact column has also been set. So why it is not hitting W_AP_XACT_F ???
Thanks in advance.
Regards,
Ravi Desai

You said that the Logical table Date- dim has 2 LTS (Date_dim, Event_closed_date_dim ).
How you defined this, is it something like
1) Drag table Date_dim
2) Select the column Row_wid of Event_closed_date_dim from Physical layer and drop on Row_wid of Logical tabl Date_dim
With this logical column Row_wid 2 sources. In this case you see 1 logical join between logical table day(with 2 LTS) and fact
If you followed this way should not have any issues.
Joins like:
PL-: Date_dim--->Fact<-- Event_closed_date_dim
BMM: Date->Fact
If you have any doubts, just create a new rpd with these table objects
Check your configuration.

OBIEE 11g - No fact table exists at the requested level of detail

My dimesion tables are snow-flake.
Table1 has Key, ProductName, ProductSize, Table2Key
Table2 has Key, ProductDepartment, Table3Key
Table3 has Key, ProductDivision
I have created 2 hierarchies (in same dimension Product). Note: ProductSize is in Table1.
ProductDivision > ProductDepartment > ProductName (shared level)
ProductSize > ProductName (shared level)
There are 2 fact tables
Fact1 is at ProductName level
Fact2 is at ProductDepartment level
When I create a request with columns as ProductSize and some measure; and filter it on ProductDepartment. The request fails with error "No fact table exists at the requested level of detail", but the request can ideally be answered using fact with ProductName level.
I have properly defined logical level keys in the hierarchies and logical level in the LTS (content tab)
Can anyone point me what I am doing wrong here?

Since both fact tables are at same granular level I would suggest to map each other (Signon_A maping Signon_B) in BMM layer logical fact @source.
Considering them as Fact and with fact extension.
BTW: Did you try by setting implicit fact at subject area properties?
Edited by: Srini VEERAVALLI on Feb 1, 2013 9:04 AM

Large Fact Tables

I have some transactional tables that are quite large. Anywhere from 1 to 3 million records. I have been doing my best to find information on the best way to deal with these and I am having some trouble. I am a little tight for time and could use a little help from others who have dealt with large datas sets before. What are some of the best ways to deal with this.
I have tried creating database level partitions by date which didn't seem to affect the OBI performance much. If I actually create different physical tables through the ETL process for each year it helps but I would like to avoid needing to create and manage that many different mappings.
Is the best way to do this to use the OBI caching and seed the cache after loading the data? I have even tried a few indexes and not had much luck.
Any help is greatly appreciated and I thank everyone in advance for their time. :)

Presuming Oracle backend database.....(you didnt say)
Partitioning would seem a quick (and expensive $$$$) win, if you partition on date, be sure to use the same date key to perform 'partition pruning' , which is to say give the optimizer a chance to throw away all unrequired partitions before it starts going to disk. When you say 'didnt improve performance much' you need to give a partition wise join for the partitioning to become effective at query time - did you do this ? for example a dashboard prompt with a filter on week / month would help (assuming your week / month time dim column is joined on partition key)
Is your data model a star schema ? Do you have dimension metadata in your database ? I'd be looking at Materialized views and looking for some sort of aggregate rollup query re-write whereby you queries are re-written at run time to the Mview and does not hit your fact table.
As for caching, OBIEE caching is the last resort after you exhaust every other alternative, its not there to speed up queries and you would be hiding the problem, what when a user drills down or needs to run an ad-hoc report that is not cached ?
I would start with understanding Oracle execution plans, review your data model (with the view on speedy data extraction) and look at what Oracle DB gives for data warehousing appliances :
parallelism is your friend!
star transformation,
Mviews (table or Cube based)
OLAP

2 Fact Tables with a same content level

Hi,
I have 2 fact tables F1,F2 joined to the same 4 dimensions D1,D2,D3,D4.The detail level # of elements multiplied for all the dimensions D1,D2,D3,D4 are the same for both dimension.I even set the content level for the 2 fact tables and the content filter is the same in both fact tables F1.Column1=0 in F1 fact table and F2.Column1=0 in F2 fact table.So how does OBIEE decide which fact table to select in this scenario.
I went through the below blog but could not get much information
http://obiee-blog.info/administration-tool/what-rule-is-followed-when-several-fact-are-at-the-same-content-level/
I appreciate if anyone can guide me with the right answers.

How many records retrieving when joining F1 & F2 with dimension ? if the f1 and d1 has 200 records and f2 and d1 is retriving 100 records it chooses shortest path.
thanks,
Saichand

OBIEE Query not hitting the other fact table

Hi All,
I am trying to create report based on two fact column and one dimension. Dimension is connected with these two facts table. When i create report using one column from dimension and one column from respective facts so i get two scenerio...
For example let say..
D1 is dimension and F1 and F2 are two fact tables.
First i used a column which have aggregation rule from one fact and one column from other fact which also have aggregate column.
That is report like...
D1.c1,Agg(F1.c2),Agg(F2.c3)
When i run the report I get the data from dimension and only from first fact table. When i check the query, Query contain only one fact table and it doesnt hit the other one.
Now in second scenerio i used one column from dimension, one column from first fact which have aggregation rule and one column from second fact which doesnt have any aggregation rule.
like...
D1.c1,Agg(F1.c2),F2.c3
When i run the report i got the error. It says
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: F1 -C2 . Please fix the metadata consistency warnings. (HY000).
But there is no warning in RPD.
I am amazed that it is not taking both the fact columns even the dimension is confirmed dimension and have joined with both the fact tables.
As i am just started to learn OBIEE, So i am find it bit difficult that how OBIEE select the tables and formed physical query.
Waiting for your help.
Regards
Suhail

Aadi-Wasi,
Thumb rule, OBIEE BMM layer must contain a simple star schema.
Did your BMM layer suffice the above condition? If hope, Not.
My prediction of your BMM layer structure contains 3 logical tables, i.e. dimension & 2 logical facts...which is not a simple star.
Thus to make it a simple star collapse 2 logical fact tables into 1 logical fact table. As you mentioned dimension is linked to both facts, collapsing 2 logical fact tables into 1 logical fact table will provide the result for your query1.
regarding your second error:
All aggregations must be contained within Fact tables with few exceptions.
Let us know If I did resolve your issue
mark posts promptly...
J
-bifacts
http://www.obinotes.com

OBIEE: incorrect selection of fact table when generating SQL

I have 2 dimension tables ("DimA" and "DimB") connected with one fact table ("Fact1").
Also (only) "DimB" is connected with another fact table "Fact2".
When I want to make a report with one attribute ("Attribute_A") from "DimA" and another one ("Attribute_B") from "DimB", I receive a error like this:
"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 Fact2) does not contain mapping for [DimA.Attribute_A]. (HY000)"
Remember that is not supposed "DimA" to be connected with "Fact2", only with "Fact1".
The only factor that I see that can be a problem is the fact that in Presentation Catalog was defined a implicit column from tact table "Fact2".

Hi,
While I don't know the need to generate a report based on 2 dimensions only, I mean you are trying to generate a report between 2 dimensions. Dimensions are not joined together in OBIEE. OBIEE will try to pull any fact and try to obtain the relationship between the two dimensions. In your case it is taking Fact2.
One way could be if u just pull in some measure from Fact1, then u should be able to get the report.
Else u can try setting content level for DimA in fact 2 to grand total level. This can be done even though dimA and Fact2 are not joined. Although I am not sure whether this will work.

How to join Dimensions and Fact Tables in OBIEE

Hi All,
I need to create report which need to get the information from two fact tables and 7 dimensions. The granularity is not same in both the fact tables. One fact table is having common keys between all the dimension tables and second fact table have only two dimension keys but with different names. My requirement is to create the report by taking the measures from both the fact tables.
I have created joins between the second fact table and two dimension tables in physical and BMM layer and also set the highest level for all other dimension tables in the LTS of second fact table. when am creating report by taking the measures from both the fact tables, data is not getting for the measure which taken from the second fact table. Please advice me how to get the data for the measure which taken from the second fact table.
Thanks in Advancec !!

You have to use the level-base measure capabilities.
http://gerardnico.com/wiki/dat/obiee/bi_server/design/fact_table/level_based_measure_calculations
For all measures of the second fact table with the lowest grain (with two dimension keys), set for all dimension where you don't have any key the logical level to the "All" or "Total".
And UNSET the highest level of the LTS for the second fact table.
Success
Nico

Fact table showing incorrect quantity measure

Hi,
I have a scenario where i have a fact table with multiple rows and two quantity fields. My source system holds sales by "package" which can contain any number of components. The grain of my invoice table is component level. See
structure below:
PACKAGE1
- Component1 - each package contains 2 of these
- Component2 - each package contains 1 of these
So if i am reporting a sale of PACKAGE1, for a quantity of 2 - component1 had a total sales quantity of 4 and component2 has a total sales quantity of 2. However the package was only sold 2 of, but because of the sum aggregation, i see a total quantity
sold for PACKAGE1 of 6, but it should only show 2 at that level. I have looked at semi-additive measures but am unsure of how this would work in this scenario, or which option would work best for me here.
My fact table has 2 rows, each of which reference the component as one dimension and the package as another dimension.
As a workaround, I have created a calculation to divide the quantity by the number of package components (so it would show a 1 for each of the component lines in my fact table), but then the sales quantities of the components reported are incorrect.
What is the best approach for this?
Thanks in advance,
Dom

Hi Dominic,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Thanks,
Simon Hou
TechNet Community Support

How map to my particular table to the fact table in obiee 11g...

Hi friends,
I did this simple report in obiee 11g(i.e)
"NATIONALITY COUNT IN DEPARTMENT WISE"
For that i used the following tables:
per_all_assignments_f----->fact table
hr_all_organization_units----->dim table(containing departments)
per_all_people_f---------------->dim table(containing nationality)
I made all the mappings in the physical diagram, as also viewed my report in BI answers
It shows the following results like
NATIONALITY---------------------------------------------------------------------COUNT(NATIONALITY)
AUS------------------------------------------------------------------------------------------------24
AFR------------------------------------------------------------------------------------------------25
PHQ_VB-------------------------------------------------------------------------------------------40
SH_VT----------------------------------------------------------------------------------------------4
The problem is for me it is showing the above results, but the nationality column is of various codes of the country.
Since i doesnt want the code of the nationalitian to display in the results..i need the meaning of each and every nationality..
like,
AUS------------------------Australian
AFR-------------------------African
PHQ_VB----------------------Germanian(assigned)
Since i know that the meaning for the nationalitian is available in "FND_LOOKUP_VALUES"...okay..
I can import "FND_LOOKUP_VALUES" table to the physical layer...but how i can able to give the mapping to the fact table in my physical diagram...
In my report the fact table is "per_all_assignments_f"
As my fact table doesnt contains any matching column corresponding to the dimension table "FND_LOOKUP_VALUES".....
Then how i can give mappings to the fact column???? for viewing the full meaning of the nationalitian in my report.....Help me friends...
Regards,
Harry...

Hi bifact,
I followed the step that U asked me to go but im stuck with later.....
*) I saved the query that i executed in toad with the columns showing country codes and country meaning to the excel sheet...
This is the query that i executed in toad and copied data s in excel sheet..
select z.lookup_code, z.meaning
from per_all_people_f e, per_all_assignments_f f, hr_all_organization_units h, fnd_lookup_values z where
e.person_id = f.person_id and f.organization_id = h.organization_id and e.business_group_id = f.business_group_id
and f.business_group_id = h.business_group_id and f.location_id = h.location_id
AND z.lookup_type(+) = 'NATIONALITY'AND z.lookup_code(+) = e.nationality and sysdate between
e.effective_start_date and e.effective_end_date and e.nationality is not null
*) After that i created a system DSN for the excel drive..
*) After that when i tried to import metadata of the excel data that is saved, it showed me connection failed...
For importing this excel data
what connection details i need to give:--------------------
as well as user name and also password...
Soon after importing this excel you said that to give key connection only to fnd_lookup_tables(dim) and that excel data..
if so, again im not giving key connection to my fact table..
I think again the same error will occur that no logical mapping is not made to fact so again repository is inconsistent...
Hi bifact sorry to ask you, but can you see the steps that i followed is correct and after that wat more steps i need to proceed..Can you tell me in breif manner...Thanks for your help...
Regards,
Harry...

Confirmed Dimensions. OBIEE Not able to pull data from two fact tables.

Hi Experts,
I have a very simple set up of Star Schema with two fact tables and 1 dimension. Both fact tables joined to the dimension at the same level.
When i pull a column from both fact tables and the dimension table in OBIEE, it has to create simple SQL like below:
select FACT1.column1,
Fact2.Column1,
Dim.Column1
from FACT1, FACT2, DIM
where FACT1.ID = DIM.ID and FACT2.ID = DIM.ID
but instead it creating a query in a very complex way:
select case when D1.c2 is not null then D1.c2 when D2.c2 is not null then D2.c2 end as c2,
     D1.c1 as c3,
     D2.c1 as c4
from
     (select FACT1.Column1 as c1,
               DIM.Column1 as c2
          from
               DIM T1287863,
               FACT1 T1287945
   where (DIM.ID = FACT1.ID)
       ) D1 full outer join (
        select FACT2.Column1 as c1,
               DIM.Column1 as c2
          from
               DIM,
               FACT2
          where ( DIM.ID = FACT2.ID)
     ) D2 On isnull(D1.c2 , '1') = isnull(D2.c2 , '1') and isnull(D1.c2 , '2') = isnull(D2.c2 , '2')
I even tried setting the levels for both the fact tables and it still creates the query in avove way. Any thoughts on this will be vary helpful.

Subramanian,
see below the code we're using for the RFM.
on the ct_containers table i'm passing a line, and its getting updated after the call.
on the ct_errors table i just want to receive the errors and i only receive the line, we add manually there ('Serious error with validation code').
kr, achim
FUNCTION zbapi_ra_validations .
*"*"Local Interface:
*" IMPORTING
*"     VALUE(IS_RA_SCREEN) TYPE ZBAPI_S_RA_SCREEN
*" CHANGING
*"     VALUE(CT_ERRORS) TYPE ZRA_T_ERRORS
*"     VALUE(CT_CONTAINERS) TYPE ZRA_T_CONT_IP
DATA:
    lo_badi_handle TYPE REF TO zra_validation_rule,
    ls_error       TYPE zra_s_error.
GET BADI lo_badi_handle.
TRY.
      CALL BADI lo_badi_handle->validate_rules
        EXPORTING
          is_screen_flds = is_ra_screen
        CHANGING
          ct_containers = ct_containers
          ct_errors      = ct_errors.
    CATCH zcx_ra.
      ls_error-message = 'Serious error with validation code'.
      APPEND ls_error TO ct_errors.
ENDTRY.
ENDFUNCTION.
if i call this rfm in SE37 the ct_errors table is populated with all errors and the manually created line.
Message was edited by: Achim Hauck

How to prioritise obiee to select logical fact out of 2 logical fact tables

Hi All,
I have a scenario where in I have 2 Logical Fact tables F1 and F2 and 2 Logical Dim tables D1 and D2.
Both Logical Dim tables are joined to F1 and F2 i.e.(D1-F1-D2) and (D1-F2-D2). When a user selects columns from D1 and D2 it always select F1.
I would like OBIEE to select F2 instead of F1. Is this possible?
With Regards
Prads

You need to mention the levels in content tab of LTSs depends on the joins to dimensions.
It automatically picks the right LTS based on the dimensions selected in criteria & levels in the content tab of your LTSs.
Anyways, if you want to make f2 as main LTSs put that in first position under Sources folder.

Incorrectly defined logical table source (for fact table X

Hi!
Imagine the following Physical Diagram:
- Dim A
- Dim B
- Fact A
- Fact B
Joins:
- Dim A is parent of Dim B
- Fact B has a FK to Dim B
- Fact A has a FK to Dim A
Business Layer:
- Logical Table Dim A
- Logical Table Dim B
- Logical Table Fact A
- Logical Table Fact B
Joins:
- same joins (not FK Joins) that Physical Layer
When we build a report that only has one column of Dim A and one column of Dim B (A is parent of B), the following error appears:
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 "Fact A") does not contain mapping for [Dim A.col1, Dim B.col1]. (HY000)
What is wrong?
Help!
Thanks.

Hi,
The joins of dimensions go via a fact table. In your case there is no common fact table.
You can solve this by drag/drop a field from the physical table Dim B on the displayed logical table source of the logical table Dim A.
Now the BI Server knows that Dim A and B have a physical relationship.
Regards

Incorrectly defined logical table source (for fact table Facts) does not

Hi,
I have two Dimensions A and B. A is joined to B by a foreign Key.
The report works if I pull B. Column1, A.Column2.
The report is throwing an error if i try to change the order of the columns like this. A.Column2, B. Column1.
error : Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
File: odbcstatementimpl.cpp, Line: 186
State: S1000. Code: 10058. [NQODBC] [SQL_STATE: S1000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Facts) does not contain mapping for B.Column1
I am not sure where it is going wrong.
Thanks
jagadeesh
Edited by: Jagadeesh Kasu on Jun 16, 2009 4:22 PM

did you make joins in LTS or on the physical table.
try to make join in LTS if they are not there.

Unable to join 3 fact tables in obiee data model.

Hi,
I am unable to join the 3 fact tables in obiee rpd. If I join with 2 fact tables I got the data in repors, Once I add the one more fact table and join with related dimensions, I am getting nodata error. I am following all joins keys as per datamodel, I am able to see the data in database. anyone pls give me the solution. Thanks in advance.
Edited by: 1007582 on May 23, 2013 2:17 AM

Can you please give some more detail as in what you have model in RPD;
For example, if There are 3 Fact table F1, F2, F3 and two Dimesion Confirmed_D1, Non_Conf_D2. Confirmed_D1 is joined to all three fact tables and Non_Conf_D2 is joined to F2.
Now to implement this model we have to set the logical content level in BMM layer for Non_Conf_D2 in F1 & F2 to Total*. After this only we can report on Confirmed_D1, Non_Conf_D2, F1, F2, F3 whithout any error.
Sometime join with multiple table can also result in No Data, since the join conditions filters out the result data.
Please mark helpful or correct.
Regards,
Kashinath

OBIEE Hitting incorrect fact table

Similar Messages

Maybe you are looking for