It's my (recent) understanding that fact tables are built around (forgive my unexpert terminology) 'concepts'. I would say 'entities' or 'objects' if i didn't think those terms probably mean something else. So, one fact table would contain aggregaged data from different systems about say what i am calling the concept 'service request', another fact table would contain data relating to the concept of 'order' etc. Is that correct?
Fact tables are based on measurable quantitative attributes surrounding business entities, usually processes. If the business process crosses normal departmental boundaries, then so be it. If it crosses transactional system boundaries, then so be it.
For example, Purchasing may have several systems (requisition, vendor management, receiving, inventory) and cross departmental boundaries (purchasing, accounting, warehouse, etc).
In your case, the fact table processes are Service Request and Order Fulfillment (pardon me for putting words in your mouth - use your business terminology).
-------------------------
The trouble with doing something right the first time is that nobody appreciates how difficult it was - Steven Wright
Great,thanks, just what i needed! Opportunistic I know, but about measures, I understand that they are sums or counts of data, so for instance: total number of service requests, total travel time, total part usage, total working days. When combined in a MOLAP cube with a dimensional characteristic like who or when, this allows a detailed business analysis of the data. If this is correct then it would mean that in a 5 layer architecture of 1) Staging > 2) ODS > 3) Data warehouse> 4 Datamart > 5 MOLAP > the measures could only be created at the MOLAP stage. Have I got that right?
Sometimes the datamart is already summarized or contains summary tables for things like total travel time, total working days, etc summarized by, say, month, or Year to Date, etc.
-------------------------
The trouble with doing something right the first time is that nobody appreciates how difficult it was - Steven Wright
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.