Combining Low Level Data and 3rd Party Aggregated Data
3 posters
Page 1 of 1
Combining Low Level Data and 3rd Party Aggregated Data
Hi,
Say you have a fact table that captures sales value and sales cost, and you compute the margin at the semantic layer. Dimensions are simply time, and customer. In addition, you have 3rd party benchmark data that is aggregated for margin alone (no other data available) for a certain year.
What is the best way to model this so that a user can view actuals vs. benchmarks in OLAP or a report?
Also, how do you make the link between the calculated margin and the 3rd party margin?
Cheers
Say you have a fact table that captures sales value and sales cost, and you compute the margin at the semantic layer. Dimensions are simply time, and customer. In addition, you have 3rd party benchmark data that is aggregated for margin alone (no other data available) for a certain year.
What is the best way to model this so that a user can view actuals vs. benchmarks in OLAP or a report?
Also, how do you make the link between the calculated margin and the 3rd party margin?
Cheers
diz_420- Posts : 2
Join date : 2013-02-28
RE: Combining Low Level Data and 3rd Party Aggregated Data
Its better to store the benchmark data in a separate table. Whenever actual vs benchmark data is to be seen... actual data should be rolled up to the same grain as the benchmark values available. If you are getting benchmark data with varying granularity then add a column in the benchmark tablle to store the level to which it rolls up to. The linking can be done at semantic layer or at the reporting layer too.
-JR
-JR
rathjeevesh- Posts : 15
Join date : 2013-02-16
Re: Combining Low Level Data and 3rd Party Aggregated Data
So, you are suggesting to snowflake the star schema to this benchmark table?
diz_420- Posts : 2
Join date : 2013-02-28
Re: Combining Low Level Data and 3rd Party Aggregated Data
You have to aggregate your sales data to the same grain as the 3rd party data (which is in another fact table). Then you can combine on a report. Here's an example, http://www.kimballgroup.com/2005/06/03/design-tip-68-simple-drill-across-in-sql/
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Similar topics
» Problem with Different level of grain, BRIDGE and Combining two Dimensions
» difference between data mart and data warehouse at logical/physical level
» Store Aggregated data in dimension
» Loading Data Aggregated to Date into Fact Table
» Combining data from different fact tables in a query
» difference between data mart and data warehouse at logical/physical level
» Store Aggregated data in dimension
» Loading Data Aggregated to Date into Fact Table
» Combining data from different fact tables in a query
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum