Bridge table between fact/dim table

My requirement is to create a relationship between fact (service request) and dim (timesheet) table.
Many rows of dim table is related to a record in Service request. Hence i created a bridge table to join them.
I imported the bridge table into physical layer. Then created two foreign key between the bridge table, dim/fact tables.
Then pulled the bridge table into the dimension logical table source. Then created a new logical join between the fact and dimension table.
When i want to count the nbr of service request, my query is not hitting the service request fact.
Is there any step missed to create the relationship between the fact and dimension for introduction bridge table.
Pls any one provide the step by step for this process. This is little urgent.
Thanks

Just continue on Marks blog...he put it all together nicely:
http://www.rittmanmead.com/2007/06/19/obiee-data-modeling-tips-1-integrating-1-1-and-1-many-source-tables/
and
http://www.rittmanmead.com/2007/09/16/obiee-dimension-data-modeling-redux/
Cheers,
C.

Similar Messages

Fact/Dim Tables entries analyzing using RSRV

Hi All,
When we analyzing the infocube in RSRV to see percentage of Dimension tables, system is showing 0% for all the dimensions and also for Fact tables.
But data is existing in fact table of infocube and also in dimensions tables, when we see in SE11.we also executed report SAP_INFOCUBE_DESIGNS in SE38, in their also we are not able to find any entry for particular infocube.Please advice on this ASAP.
Thanks & Regards
Manoj

1) transaction se16 -> fact table name, /bic/f[infocube name] and /bic/e[infocube name] or /bi0/f.. and /bi0/e for business content infocube, click 'number of entries'
2) transaction db02 -> 'detail analysis' -> object name = [infocube name]
Hope it Helps
Chetan
@CP..

Create a fact table from two Dim Tables - is it possible in powerpivot?

I have two comma delimited flat files.
1 - Customer Details (customerCode, Name, Address etc)
2 - Order Details(OrderNumber, OrderLineNumber, CustomerCode etc)
The two link by CustomerCode. I can bring both into powerpivot and link them directly, so cna deliver a report quickly. This model will grow however, with product dimension, store dimension and a few others.
So, i want to design it correctly from the outset, having a DimCustomer & a DimOrderDetail, that both link via a FactTable. I cant figure out how to create a factTable using both Dimensions using only powerPivot & dax. Is it possible?

Shaping the data before it gets to PowerPivot using Power Query is the easier option:
http://office.microsoft.com/en-us/excel-help/introduction-to-microsoft-power-query-for-excel-HA104003940.aspx
http://www.microsoft.com/en-us/download/details.aspx?id=39379
Ideally, with Power Pivot, the best model is a star schema where you have a single fact table and all the dimensions are linked directly to the fact table and not to one another. This isn't always possible in real world modeling but it is definitely the
easiest to deal with when writing measures and designing pivots. It also generally gives the best performance.

Bridge Table between two fact tables

Hello everybody,
From what I have read on the BI Administration tool help and on this forum, bridge tables are used to define many-to-many relations between dimension sand fact tables. Is it possible to have a bridge table defining a many-to-many relation between two fact tables?
Here is my senario:
1. We have a fact table called fact_Orders describing orders for some products.
2. We have a fact table called fact_Sales describing sales og these products.
3. We have a table describing the transformation from order lines to sales lines which is a many-to-many relation, because it is possible to transform an order in more than two steps.
I was thinking of connecting the two fact tables with a bridge table.
If bridge tables are inappropriate for this case, what could be a better model for my senario?
Thanks for your time.

Hi,
Well a conformed dimension is a bridge table between two facts, so not sure why you need anything else. If there is a one to many from D1 to F1 and a one to many from D1 to F2 then effectively there is a many to many join from F1 to F2 through the D1 dimension.
Sounds to me like all you need is an order dimension table, rows in the orders fact table will join to this dimension and so will rows in the sales fact table. You can then do calculations like number of sales per order, total sales revenue per order, # of order items per order etc etc.
Regards,
Matt

Best Practice - Outer Join between Fact and Dim table

Hi Gurus,
Need some advice on the below scenario
I have an OOTB subject area and we have around 50-60 reports based on it. The related subject area Fact and Dim1 table are having inner join.
Now I have a scenario for one report where outer join has to be implemented between Fact and Dim1. Here I am against changing the OOTB subject area join as the outer join will impact the performance of other 50-60 reports.
Can anyone provide any inputs on what is the best way to handle this scenario?
Thanks

Ok. I tried this:
Driving table : Fact, Left outer join -- didnt work.
Driving table: Dimension D left outer join -- didnt work either
In either the case, I see physical query as D left outer Join on Fact F. and omitting the rows.
And then I tried this -
Driving table: Fact, RIght outer join.
Now, this is giving me error:
Sybase][ODBC Driver]Internal Error. [nQSError: 16001] ODBC error state: 00000 code: 30128 message: [Sybase][ODBC Driver]Data overflow. Increase specified column size or buffer size. [nQSError: 16011] ODBC error occurred while executing SQLExtendedFetch to retrieve the results of a SQL statement. (HY000)
I checked all columns, everything matched with database table type and size.
I am pulling Fact.account number, Dimension.account name, Fact.Measures. I am seeing this error each time I pull Fact.Account number.

Fact table have tow column reference the same dim table

In my analytic domain, my fact table have tow column reference the same dim table, but in physical diagram, between two table ,can only have one join, so i create a copy of the dim table, then finish the join in physical. This method can resolve this question, but not so good, Anyone have perfect solution?

user4497169 wrote:
Thanks,
yours method is very very good, I don't know this method before. Where do you get this imfomation?The sample sales RPD has (good) modelling references you can refer to, otherwise think about how you'd write the SQL Statement yourself, you'd need to use an alias to access the same table on seperate joins.

Multiple 'logical joins' between a fact table and one dimension table

It appears that one cannot create multiple ‘logical joins’ between a fact table and one dimension table in OBIEE using the Oracle BI Administration Tool. For example, considering a Business Model with a dimension table TIMES and a fact table FACT containing START_TIME and END_TIME, we would like to create separate logical joins from FACT to TIMES for the START_TIMEs and END_TIMEs? Obviously, the underlying foreign keys can be created, but as far as I can tell the Oracle BI Administration Tool doesn’t support this. The workaround would be to replicate the TIMES table, but that’s ugly.
I seek an alternative approach.

Try this. Create an two aliases for the TIMES dimension (Start & End) in the Physical Layer and then remove foreign key to the "Parent" Times dimension. Create the Foreign Key in the Physical Layer to the new aliases and then create the complex joins in the BMM Layer to the new aliases as well. This will allow you to present both dates within the same table in the Presentation Layer. Not the most elegant solution but it works.

How to display a description in fact table from an unrelated DIM table in powerpivot?

Hello,
I have two tables in powerpivot 2010: 1 that is my fact and the is unrelated. I'm relatively new to SQL and powerpivot.
What I need to do is display a description from my DIM table based on a column in my fact. Is this possible? In my fact, I
have a ReasonID, the DIM has the ReasonID and description. I just need the description added in my fact as a new /
another column. Thanks. John

Hello,
When you have the same column in both tables, then they are related, even if in database no primary / foreign key is defined. In PowerPivot we can define additional / manual relation, just Change to "Diagram View" and define the relation like below:
But if you still want the "Dim description" as a computed column in your fact table, then you can use the
LOOKUPVALUE function
=LOOKUPVALUE(Dim01[Description], Dim01[ReasonId], Fact01[ReasonId])
Olaf Helper
[ Blog] [ Xing] [ MVP]

Ratio between Fact table and Dimention table for a Infocube

Hi All,
How can we reduce the Ratio between Fact table and Dimention table for a Infocube below 20%.??
please give suggestions

Hi
Reduce Ratio??
The Ratios are dependent on the Fact Table, and the Dimension table that is modeled for your Cube.
You cannot change ratio individually, but can set the Line Item Dimension , provided you have only one char object is taking much space and bulky with much percentage, based on your requirement. You can always use fine tuning objects.
Please be more specific while posting, to get right help from sdn.
Hope it helps

To check fact and dim table sizes in RSRV

Hi guys,
i hve access to only RSRV on prod so how do i check the fact and dim table ratios what is the test that i have to use to find....
Thanks,
Your help will be greatly appreciated

Hi,
I guess you can try the following options available in RSRV ->All Elementary texts -> Database ->
Database Statistics for an InfoCube and Its Aggregates
Database Information about InfoProvider Tables
Databank Parameters of *-Schema Tables for InfoCube
Check this help link:
[http://help.sap.com/saphelp_nw04/helpdata/en/92/1d733b73a8f706e10000000a11402f/frameset.htm]
hope this helps U...
Regards,
NR

Table as fact and dimension

Hi,
Can one table act as a fact in one subject area and act as a dimension in another subject area? Thanks.

Hi
I confirm Stijn Gabriels' post.
You don't have to do an alias in your physical table, otherwise the request will generate an alias in SQL for nothing ! However, in your logical layer, you will create 2 logical table : one for the fact, one for dimension. Both of them will have the same source : your unique physical table.
Let's take an example : suppose you have only 2 table in your datawarehouse : 1 fact table with degenerate dimension attributes (so a table with fact and dimension data), we'll call it "revenue", and 1 dimension table for... "Time", for example. We'll call it"Time"
Your conceptual (on paper) is a star schema with 1 fact table (revenue_fact), and 2 dimension table (time, and revenue_carac).
In your OBIEE physical layer :
- you import the 2 tables "revenue" and "time" from your database.
- you link "revenue" with "time"
In your OBIEE logical layer :
- you create a logical table called "Dim Time", based on the "Time" physical table and you do what you want with it (hierarchy...)
- you create a logical table called "Dim Revenue Carac", based on the "revenue" physical table, and you do what you want with attributes
- you create a logical table called "Fact revenue", based on the "revenue" physical table, and you do you what you want with measures and aggregation
- you link the 2 logical dimension table with the logical fact table
And that's all. Now, let's see which kind of SQL OBIEE will generate if you want to display the measure "revenue" with the attribute "revenue_carac" and the attribute "year".
Select Sum(R.revenue_measure) , R.revenue_carac , T.year
From revenue R , time T
Where R.time_id = T.id
Group by R.revenue_carac , T.year
If you set alias in your physical layer, the request will be that (and you don't want it) :
Select Sum(R1.revenue_measure) , R2.revenue_carac , T.year
From revenue R1, revenue R2 , time T
Where R1.time_id = T.id
And R1.id = R2.id
Group by R2.revenue_carac , T.year
same results, but useless join between the same physical table

Dimension table and fact table exists data physically

Hi experts,
can anyone plz tell me weather dimension table and fact table exists data physically or not/

Hi..Sudheer
SAPu2019s BW is based on "Enhanced Star schema" or "Info Cubes" database design.This database design has a central database table, known as u2018Fact Tableu2019 which is surrounded by associated dimension tables.
Fact table is surrounded by dimensional tables. Fact table is usually very large, that means it contains
millions to billions of records.
These dimension tables doesn't contain data it contain references to the pointer tables that point to the master data tables which in turn contain Master data objects such as customer, material and destination country stored in BW as Info objects. An InfoObjects can contain single field definitions such as transaction data or complex Customer Master Data that hold attributes, hierarchy and customer texts that are stored in their own tables.
SID is surrogate ID generated by the system. The SID tables are created when we create a master data IO. In SAP BW star schema, the distinction is made between two self contained areas: Infocube & master data tables/SID tables.
The master data doesn't reside in the satr schema but resides in separate tables which are shared across all the star schemas in SAP BW. A numer ID is generated which connects the dimension tables of the infocube to that of the master data tables.
The dimension tables contain the dim ID and SID of a particular IO. Using this SID the attributes and texts of an master data Io is accessed.
The SID table is connected to the associated master data tables via teh char key.
Fact table(Transaction data,DIM ID)<>Dimention Table(SID and Dim ID)<->Masterdata table(SID,IO)
Thanks,
Abha

Resolving loops in a star schema with 5 fact tables and 6 dimension tables

Hello
I have a star schema, ie 5 FACT tables and 7 dimension tables, All fact tables share the same dimension tables, some FACT tables share 3 dimesnsions, while other share 5 dimensions.
I did adopt the best practices, and as recommended in the book, I tried to resolve them using Context, as it is the recommended option to Alias in a star schema setting. The contexts are resolved, but I still have loops. I also cleared the Multiple SQL Statement for each context option, but no luck. I need to get this resoved ASAP

Hi Patil,
It is not clear what exactly is the problem. As a starting point you could set the context up so that it only covers the joins from fact to dimension.
Fact A, joins Dim 1, Dim 2, Dim 3, and Dim 4
Fact B, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 5
Fact C, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 6
Fact D, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 7
Fact E, joins Dim 1, Dim 2, Dim 4 and Dim 6
If each of these are contexts are done and just cover the joins from fact to dim then you should be not get loops.
If you could lay out your joins like above then it may be possible to specify the contexts/aliases that should work.
Regards
Alan

How to provide joins between oracle tables and sql server tables

Hi,
I have a requirement that i need to generate a report form two different data base. i.e Oracle and Sql Server.
how to provide joins between oracle tables and sql server tables ? Any help on this
Regards,
Malli

user10675696 wrote:
I have a requirement that i need to generate a report form two different data base. i.e Oracle and Sql Server. Bad idea most times. Heterogeneous joins do not exactly scale and performance can be severely degraded by network speed and b/w availability. And there is nothing you can do in the application and database layers to address performance issue at the network level in this case - your code's performance is simply at the mercy of network performance. With a single glaring fact - network performance is continually degrading. All the time. Always. Until it is upgraded. When the performance degradation starts all over again.
If the tables are not small (few 1000 rows each) and row volumes static, I would not consider doing a heterogeneous join. Instead I would rather go for a materialised view on the Oracle side, use a proper table and index structure, and do a local database join.

Fact table is GT Dimension table

Hi All
Where can i find the relation between Fact table and dimension table sizes. If i want to check whether my dimension table is greater than fact table then how?
If i can use program " sap_infocube_designs" then when i am trying to execute it it is not working.
regards
Naga

I dont think SAP_INFOCUBE_DESIGNS doesnt give u the size of the fact table rather the density and the row count in the cube.
"density" in SAP_INFOCUBE_DESIGNS
check the answer by pizzaman in this thread detailing the size of the fact tabe
Fact table size of the cube

Bridge table between fact/dim table

Similar Messages

Maybe you are looking for