February 1, 2017 at 3:53 am
Hi
I'm in the process of designing a POC Datawarehouse and hope someone can provide some guidance.
The LOB Application deals with providing Funding to Companies. This takes the form of an Application form whereby the Client seeks money. This application form, from a Business viewpoint will go through many different status' from Draft, In Progress, Under Review, Suspended, Approved etc.
The monetary value in the LOB system is held in a single column thus when we require to Sum All Draft we use SUM(Column) where Status = 'Draft', or all Approvals SUM(Column) where status = 'Approved'
My question is regarding the fact table:-
February 1, 2017 at 6:04 am
What you've just described sounds like a classic example of an Accumulating Snapshot fact table as described by Kimball. This would be a fact table modeling a multi-step process having multiple date keys (OrderDate, ShipDate, PaymentDate, etc.) and one or more accumulating measurements (Quantity, ExtendedPrice, etc.).
http://www.kimballgroup.com/2008/11/fact-tables/
https://www.amazon.com/Data-Warehouse-Toolkit-Complete-Dimensional/dp/0471200247
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 3, 2017 at 6:44 am
Came here today to answer a question and learned something instead! Thanks Eric. I think most of my fact tables are Transaction Grain, but I'm excited to go into the warehouse and inventory them to see if that's the case.
February 3, 2017 at 7:37 am
Thanks Eric for taking the time to provide me with the guidance I sought. Much appreciated.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply