Comments on: Oracle BI EE 10.1.3.4.1 – Single Table Repository Design – Part 1 http://www.rittmanmead.com/2009/11/10/oracle-bi-ee-10-1-3-4-1-single-table-repository-design-part-1/ Delivered Intelligence Wed, 17 Mar 2010 13:47:41 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: Venkatakrishnan J http://www.rittmanmead.com/2009/11/10/oracle-bi-ee-10-1-3-4-1-single-table-repository-design-part-1/comment-page-1/#comment-11223 Venkatakrishnan J Mon, 16 Nov 2009 07:15:01 +0000 http://www.rittmanmead.com/?p=3632#comment-11223 @Abhishek - Yes. Attributes from a single table can be treated as multiple dimensions in the BMM. It all depends on how you are joining with your fact measures. If you have seperate join keys for the fact then Aliases are the way to go. But if you have the fact measures coming from the same table as well, then you surely can model it as separate dimensions. -Venkat @Abhishek – Yes. Attributes from a single table can be treated as multiple dimensions in the BMM. It all depends on how you are joining with your fact measures. If you have seperate join keys for the fact then Aliases are the way to go. But if you have the fact measures coming from the same table as well, then you surely can model it as separate dimensions.

-Venkat

]]> By: Abhishek http://www.rittmanmead.com/2009/11/10/oracle-bi-ee-10-1-3-4-1-single-table-repository-design-part-1/comment-page-1/#comment-11218 Abhishek Fri, 13 Nov 2009 15:40:29 +0000 http://www.rittmanmead.com/?p=3632#comment-11218 Hi , I liked the way you presented this , its very useful. I think if you want to use the same table in Fact and Dim then the approach you are suggested will really be useful, but tell me about what if someone wants to use the same table as more then one dim, for exp.- You have W_SOURCE_D, we can have Program / Campaign / Event all in same table.In that case if we want to have all these 3 attributes separately in BMM layer like W_SOURCE_D_PROGRAM , W_SOURCE_D_CAMPAIGN , W_SOURCE_D_EVENT then we have to create the alias only .. any suggestions on this ? Hi ,
I liked the way you presented this , its very useful. I think if you want to use the same table in Fact and Dim then the approach you are suggested will really be useful, but tell me about what if someone wants to use the same table as more then one dim, for exp.- You have W_SOURCE_D, we can have Program / Campaign / Event all in same table.In that case if we want to have all these 3 attributes separately in BMM layer like W_SOURCE_D_PROGRAM , W_SOURCE_D_CAMPAIGN , W_SOURCE_D_EVENT then we have to create the alias only .. any suggestions on this ?

]]>