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.

Similar Messages

I recently bought an ipad 2 and wanted to use all the apps on my iphone4 on my ipad but have been charged when I use my apple id. What should I have done to share the apps?

I recently bought an ipad 2 and wanted to use all the apps on my iphone4 on my ipad but have been charged for the first app I downloaded when I use the same apple id. What should I have done to share the apps and should I have been charged? 2 months ago when I got a new iphone, i was told in order to get all my apps back as I hadn't backed up my files, if I used the same apple id I would 'purchase' the app, but then would not be charged as apple would recognise that I have already purchased the app. That worked, but when I did the same thing on my ipad 2 using the same apple Id, I was charged... what should I have done and is this right as I thought the whole point of having multiple apple devices was I could share apps between devices. please help! thanks.

Using the same Apple id and Password you should be able to download purchased apps without being charged again.
I download to an iPad/iPad2/iPhone3 & iPhone4 with no problem.

When my phone is powered on and not in use all of a sudden the Samsung Galazy 5 then Samsung and the verizon logo comes on to frequent all threw out the day . Has this happened to anyone else ?

When my phone is powered on and not in use all of a sudden the Samsung Galaxy 5 then Samsung and Verizon logo comes on tell me to check my battery cover, I have checked it and it is secure but it still continues to happen all day long. Has this happened to anyone else?

My phone is 5 days old and does the exact same thing.
Just check the box that says do not show again when it pops up. That should Stop the pop ups all the time.
I am very dissapointed with my phone . My S5 has been very buggy, likes to freeze up , lags , drains battery in about 4-5 hours, loses data connection in "Good Signal" areas ( drops down to 3g and 1x data or says 4g lte but Web pages fail to load , say no data connection). Camera has also crashed on me twice already.

How to process each records in the derived table which i created using cte table using sql server

I want to process each row from the CTE table I created, how can I traverse from first row to second row and so on....
how to process each records in the derived table which i created using cte table using sql server

Ideally you would be doing a set based processing rather than traversing row by row as thats more efficient. To answer it specific to your scenario we may need more info. Can you explain with some sample data your exact requirement?
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Join multiple facts and dimensions for reporting 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.

You can find the same issue in
Logic of queries in OBIEE
or
Connection between 2 fact tables
Follow the link
http://there-n-back-again.blogspot.com/2009/04/oracle-analytics-how-to-report-over-non.html
Put 'All' or 'Total' at levels for dim_xxx for those facts you need in your report from facta and factb
Regards
Nicolae

Urgent - How to join multiple facts and dimensions in OBIEE rpd??

Hi,
In my RPD I have 3 facts and 4 dimensions and the joins defined are as below
Physical layer - All joins are FK and inner (1:N)
FACTA-------------- DIM_TIME, DIM_CUST,DIM_CAL
FACTB-------------- DIM_TIME, DIM_CUST,DIM_CAL
FACTC-------------- DIM_TIME, DIM_CUST,DIM_CAL, DIM_XYZ
BM layer - All joins are complex, inner
The logical table F1 pulls columns from FACTA, FACTB and FACTC . Complex join exists between all 4 dimensions DIM_TIME, DIM_CUST,DIM_CAL, DIM_XYZ to logical table F1.
Issue: I need to build a report with $ column from FACTA, FACTB and FACTC and need to add filter conditions using columns from DIM_TIME, DIM_CUST,DIM_CAL, DIM_XYZ.
However when ever I add a filter condition from DIM_XYZ the physical query generated is not generating code to access data from FACTA and FACTB. Instead it is subsituting a NULL and just pulls data frm FACTC.
My Questions: What is the best way to build the physical and BMM layer using FACTA, FACTB,FACTC, DIM_TIME, DIM_CUST,DIM_CAL and DIM_XYZ??
I need to resolve this issue ASAP so any help is appreciated. Thanks
Edited by: user11935561 on Feb 10, 2010 6:27 AM
Edited by: user11935561 on Feb 10, 2010 6:28 AM

You can find the same issue in
Logic of queries in OBIEE
or
Connection between 2 fact tables
Follow the link
http://there-n-back-again.blogspot.com/2009/04/oracle-analytics-how-to-report-over-non.html
Put 'All' or 'Total' at levels for dim_xxx for those facts you need in your report from facta and factb
Regards
Nicolae

Joining Multiple facts to the multiple Dimension tables

Hi All,
We have multiple fact tables which are Joined to common Dimension tables. We join them in physical layer and maintain Left outer join in the BMM. I do not get any consistency errors. But when I run report I get error.
"could not find level detailed enough for group by clause" any suggestion on the same.
The join Strucutre is as follows.
Facts - F1, F2, F3
Dim - D1, D2, D3
F1 --> D1, D2, D3
F2--> D1, D2,
F3--> D1, D2, D3
We cannot combine F2, F3 into F1 using multiple Logical Table Source.
What is the best way to achieve the above mentioned functionality.
Please advice.
Regards,
Narendra Shetty.

Check this
OBI Error While Running Query
Update us back with solution, if helps pls mark
Edited by: Srini VEERAVALLI on Dec 20, 2012 7:13 AM

One table containing DIMENSION and FACT columns ... How to make it work?

Guys, i have a question that relates to OBIEE working with a single table containing both fact and dimension columns.
What is the "best" strategy to get this to behave like a star schema? Following are my questions:
- Should i alias each dim set of columns in physical layer
- Should i alias fact set of columns in physical layer
- Join them in the Physical layer and then pretend they are actually two separate structures in business layer?
OR
Something else?
Please share your ideas how to handle this type of situation.
Regards,

You can just duplicate the table in the Business Model and separate the Facts and Dimensions, there is an article about this type of design here..
http://www.rittmanmead.com/2009/11/10/oracle-bi-ee-10-1-3-4-1-single-table-repository-design-part-1/

Dimension build using SQL table and process to fill the SQL table

I have a dimension in a cube that is manually* built by one of our power users. Now I have to get all the member information of that dimension into a SQL table(example : with columns...level0,level0property,level1,level1property etc....) to use that table in STUDIO for member load.
Is there any easy process to do this? Currently I am building each and every row manually in that SQL table and there are 1100+ members in that manually built dimension. Please advice.

Thank you so much Glenn!! That worked!! You make our lives so much easier!!

Header, Line Item and Cache Techniques Using Hashed Tables

Hi,
How can I work with header, line item, and a cache techniques using hashed tables?
Thanks,
Shah.

Hi,
Here is an example to clarify the ideas:
In general, every time you have a header-> lines structure you have a unique key for the lines that has at least header key plus one or more fields. I'll make use of this fact.
I'll try to put an example of how to work with header -> line items and a cache technique using hashed tables.
Just suppose that you need a list of all the material movements '101'-'901' for a certain range of dates in mkpf-budat. We'll extract these fields:
mkpf-budat
mkpf-mblnr,
mseg-lifnr,
lfa1-name1,
mkpf-xblnr,
mseg-zeile
mseg-charg,
mseg-matnr,
makt-maktx,
mseg-erfmg,
mseg-erfme.
I'll use two cache: one for maintaining lfa1 related data and the other to maintain makt related data. Also I'll only describe the data gathering part. The showing of the data is left to your own imagination.
The main ideas are:
1. As this is an example I won't use inner join. If properly desingned may be faster .
2. I'll use four hashed tables: ht_mkpf, ht_mseg, ht_lfa1 and ht_makt to get data into memory. Then I'll collect all the data I want to list into a fifth table ht_lst.
3. ht_mkpf should have (at least) mkpf's primary key fields : mjahr, mblnr.
4. ht_mseg should have (at least) mseg primary key fields: mjahr mblnr and zeile.
5. ht_lfa1 should have an unique key by lifnr.
6. ht_makt should have an unique key by matnr.
7. I prefer using with header line because makes the code easier to follow and understand. The waste of time isn't quite significant (in my experience at least).
Note: When I've needed to work from header to item lines then I added a counter in ht_header that maintains the count of item lines, and I added an id in the ht_lines so I can read straight by key a given item line. But this is very tricky to implement and to follow. (Nevertheless I've programmed it and it works well.)
The data will be read in this sequence:
select data from mkpf into table ht_mkpf
select data from mseg int table ht_mseg having in count all the data in ht_mkpf
loop at ht_mseg (lines)
filter unwanted records
read cache for lfa1 and makt
fill in ht_lst and collect data
endloop.
tables
tables: mkpf, mseg, lfa1, makt.
internal tables:
data: begin of wa_mkpf, "header
mblnr like mkpf-mblnr,
mjahr like mkpf-mjahr,
budat like mkpf-budat,
xblnr like mkpf-xblnr,
end of wa_mkpf.
data ht_mkpf like hashed table of wa_mkpf
with unique key mblnr mjahr
with header line.
data: begin of wa_mseg, " line items
mblnr like mseg-mblnr,
mjahr like mseg-mjahr,
zeile like mseg-zeile,
bwart like mseg-bwart,
charg like mseg-charg,
matnr like mseg-matnr,
lifnr like mseg-lifnr,
erfmg like mseg-erfmg,
erfme like mseg-erfme,
end of wa_mseg,
data ht_mseg like hashed table of wa_mseg
with unique key mblnr mjahr zeile
with header line.
data: begin of wa_lfa1,
lifnr like lfa1-lifnr,
name1 like lfa1-name1,
end of wa_lfa1,
data ht_lfa1 like hashed table of wa_lfa1
with unique key lifnr
with header line.
data: begin of wa_makt,
matnr like makt-matnr,
maktx like makt-maktx,
end of wa_makt.
data: ht_makt like hashed table of wa_makt
with unique key matnr
with header line.
result table
data: begin of wa_lst, "
budat like mkpf-budat,
mblnr like mseg-mblnr,
lifnr like mseg-lifnr,
name1 like lfa1-name1,
xblnr like mkpf-xblnr,
zeile like mseg-zeile,
charg like mseg-charg,
matnr like mseg-matnr,
maktx like makt-maktx,
erfmg like mseg-erfmg,
erfme like mseg-erfme,
mjahr like mseg-mjahr,
end of wa_mseg,
data: ht_lst like hashed table of wa_lst
with unique key mblnr mjahr zeile
with header line.
data: g_lines type i.
select-options: so_budat for mkpf-budat default sy-datum.
select-options: so_matnr for mseg-matnr.
form get_data.
select mblnr mjahr budat xblnr
into table ht_mkfp
from mkpf
where budat in so_budat.
describe table ht_mkpf lines g_lines.
if lines > 0.
select mblnr mjahr zeile bwart charg
matnr lifnr erfmg erfme
into table ht_mseg
from mseg
for all entries in ht_mkpf
where mblnr = ht_mkpf-mblnr
and mjahr = ht_mjahr.
endif.
loop at ht_mseg.
filter unwanted data
check ht_mseg-bwart = '101' or ht_mseg-bwart = '901'.
check ht_mseg-matnr in so_matnr.
read header line.
read table ht_mkpf with table key mblnr = ht_mseg-mblnr
mjahr = ht_mseg-mjahr.
clear ht_lst.
note : this may be faster if you specify field by field.
move-corresponding ht_mkpf to ht_lst.
move-corresponding ht_mseg to ht_lst.
perform read_lfa1 using ht_mseg-lifnr changing ht_lst-name1.
perform read_makt using ht_mseg-matnr changing ht_lst-maktx.
insert table ht_lst.
endloop.
implementation of cache for lfa1.
form read_lfa1 using p_lifnr changing p_name1.
read table ht_lfa1 with table key lifnr = p_lifnr
transporting name1.
if sy-subrc <> 0.
clear ht_lfa1.
ht_lfa1-lifnr = p_lifnr.
select single name1
into ht_lfa1-name1
from lfa1
where lifnr = p_lifnr.
if sy-subrc <> 0. ht_lfa1-name1 = 'n/a in lfa1'. endif.
insert table ht_lfa1.
endif.
p_name1 = ht_lfa1-name1.
endform.
implementation of cache for makt
form read_makt using p_matnr changing p_maktx.
read table ht_makt with table key matnr = p_matnr
transporting maktx.
if sy-subrc <> 0.
ht_makt-matnr = p_matnr.
select single maktx into ht_matk-maktx
from makt
where spras = sy-langu
and matnr = p_matnr.
if sy-subrc <> 0. ht_makt-maktx = 'n/a in makt'. endif.
insert table ht_makt.
endif.
p_maktx = ht_makt-maktx.
endform.
Reward points if found helpfull...
Cheers,
Siva.

When to use PGA_AGGREGATE_TARGET and when to use temporary table space?

Hi, all.
I am a little confused with regard to when to use pga work area, and
when to use temporary tablespace?
Is there any one who could give me an advice or a document?
Thanks in advance.
Best Regards.
Message was edited by:
user507290

You are more than a little confused... What has one to do with the other, do you think?
All Oracle documentation is at http://tahiti.oracle.com - I suggest you start with the Concepts manual of your version

Need of aggregated dimension to use summary tables

Hi,
I have two fact tables workdetail and worksummary. Worksummary is aggregated to month in time dim and workdetail is at timedim day level.
Now i configured my business model with timedim and work detail table.( created a hirerchy for time dim (year-month-day)). Now i want to use worksummary tables, how do i include this in my business model. I know creating new Logical Source and mentioning levels.
My major doubt is do i need to create another physical table for Time-Month? or can i use same time dim physcial table to use with summary fact tables?

the answer to your question is YES, To use aggregated summary tables, we need to have aggregated dimensions. Other wise data will be redundant and will return incosistent values.
In your case if you use the same timedim-day level table with summary tables, data will be multiplied by 30 days beacuse of time-dim monthkey will be repeated in multiple rows.
simplest solution is create view from Time_Dim table, select distinct year,month,monthkey. this view returns only unique year-months. so each month will have only one row.
-> import view in your physical layer and create a join with summary fact table.
-> Include the month table(which is view) in logical time_dim as another source,mention the levels.
-> and include your fact table in logical fact table and mention the levels to month of time dim
this will work. Let me know if i am not clear. Also we can wait for other experts comments.
- Madan

Joining Two facts with one dimension

hi,
Hello Experts,I am reporting out of 2 fact groups.
Mailing History and Booking.
The only common dimension between the 2 is the Person Dimension. I have created the hierarchies and defined the aggregation content in the LTS.This helps me in reporting using any column from the Facts or any one dimension from either of the fact groups. But if i select 2 or more dimensions , one or more from each fact group , then the report gives and error. A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: MailingHistory Campaign.Campaign Name. Please fix the metadata consistency warnings. (HY000)
For Example : BookingDim--BookingFact-MailingHistoryFact (ok) MailingSourceDim--BookingFact-MailingHistoryFact works (ok) but BookingDim--BookingFact-MailingHistoryFact - MailingsourceDim (Fails ).
When i am applying the filter from the fact 1 . i am getting this error.(which is the column in the second fact table 2).I checked all the joins in the BMM layer.
Please help me!!!
Thanks,
Surya

Surya did you set the levels properly for two fact tables and also for metrics.
When ever you are using two fact groups with non confirmed dimensions you have to make sure all the content levels set for the fact tables and as well as for metrics.
in your fact tables/ metrics - For related dimensions set the level to Detail. and for the non related dimension set the level to Total. This way obiee server will understand what is related dimension and whats not related..
hope this works for you.

Joining 2 Facts to one Dimension.

Good Afternoon
I am currently developing a report with 2 Fact tables and only 1 Dimension (Exact Date).
How can i join the 2 Fact tables with using only the one dimension?
I know the formula is something like (FILTER USING)
Can someone please assist?
Regards
Rayno

Joining two fact tables to a dimension is a simple approach like how you join one dim and one fact. Similarly you will join second fact with the same dim.
If the fact tables are joined together and only one fact joins with dim then you can join both fact tables under one LTS in BMM layer and join that logical fact to the dim table.
OBIEE handles how to query both fact tables, as per your design.
Pls mark correct/helpful.

2 facts with different dimensions in 1 logical table

hello,
im trying to accomplish the set up as described per blog:
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
i.e. i have 2 facts, F1: D1 ; F2: D1,D2,D3;
i followed the instructions and all seem to be working fine;
however: when i put the total on the report in Answers: D1,D2, F1, F2 then the measures from F1 that are repeated every row for D2 are being added , like regular sum on the column; this is not correct;
the only correct result i can get if manually i change the Aggregation Rule to :Server Complex Aggregate on all F1 measures;
id like to ask if this is a bug of this OBI version? 10.1.3.2
i wish not to instruct my users to change the aggregation rule; id like to have the set up via rpd such, that they dont have to manipulate the aggregation rules;
did anyone got the above working with correct totals without changing the aggregation rule?
if so, id appreciate any tips on how to achieve that
thanks
rgds

Basically, you need to :
* create your physical schema with the relationship
* drag and drop your Forecast Facts measure in the same logical table than your sales fact
* define your Forecast measure as level based measure (logical column/levels/properties) with the grain of the forecast table
Documentation
http://download.oracle.com/docs/cd/E12103_01/books/admintool/admintool_BusModSetup12.html
And you have an example in OBE series with quota in excel sheet :
http://www.oracle.com/technology/obe/obe_bi/bi_ee_1013/bi_admin/biadmin.html#t8
Success
Nico

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

Similar Messages

Maybe you are looking for