Inventory is used to illustrate:

Slides:



Advertisements
Similar presentations
Dimensional Modeling.
Advertisements

CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
Cognos 8 Training Session
BY LECTURER/ AISHA DAWOOD DW Lab # 2. LAB EXERCISE #1 Oracle Data Warehousing Goal: Develop an application to implement defining subject area, design.
BY LECTURER/ AISHA DAWOOD DW Lab # 4 Overview of Extraction, Transformation, and Loading.
MIS 451 Building Business Intelligence Systems
Copyright © Starsoft Inc, Data Warehouse Architecture By Slavko Stemberger.
1 9 Ch3, Hachim Haddouti Adv. DBS and Data Warehouse CSC5301 Ch3 Hachim Haddouti Hachim Haddouti.
© Ron McFadyen1 Many-to-one-to-many We need information that can only be obtained by accessing two fact tables through a common dimension … drilling across.
Dimensional Modeling – Part 2
CSE6011 Warehouse Models & Operators  Data Models  relations  stars & snowflakes  cubes  Operators  slice & dice  roll-up, drill down  pivoting.
Data Warehousing (Kimball, Ch.2-4) Dr. Vairam Arunachalam School of Accountancy, MU.
Data Warehousing DSCI 4103 Dr. Mennecke Introduction and Chapter 1.
Agenda Common terms used in the software of data warehousing and what they mean. Difference between a database and a data warehouse - the difference in.
Business Intelligence
DIMENSIONAL MODELLING. Overview Clearly understand how the requirements definition determines data design Introduce dimensional modeling and contrast.
Chapter 1 Adamson & Venerable Spring Dimensional Modeling Dimensional Model Basics Fact & Dimension Tables Star Schema Granularity Facts and Measures.
Bus Architecture. Value Chain Identifies the natural logical flow of an organization’s primary activities Operational source systems produce snapshots.
INVENTORY CASE STUDY. Introduction Optimized inventory levels in stores can have a major impact on chain profitability: minimize out-of-stocks reduce.
Basic Model: Retail Grocery Store
UNIT-II Principles of dimensional modeling
1 On-Line Analytic Processing Warehousing Data Cubes.
CMPE 226 Database Systems October 21 Class Meeting Department of Computer Engineering San Jose State University Fall 2015 Instructor: Ron Mak
June 08, 2011 How to design a DATA WAREHOUSE Linh Nguyen (Elly)
Dimensional Modeling Primer Chapter 1 Kimball & Ross.
CMPE 226 Database Systems April 12 Class Meeting Department of Computer Engineering San Jose State University Spring 2016 Instructor: Ron Mak
On-Line Application Processing
MRP: Material Resource Planning
Data Warehouse Systems
Data Warehousing CIS 4301 Lecture Notes 4/20/2006.
Data Warehouse.
On-Line Analytic Processing
Data warehouse and OLAP
Using Partitions and Fragments
Data Warehouse—Subject‐Oriented
OLAP Systems versus Statistical Databases
Star Schema.
Applying Data Warehouse Techniques
Assignment 2 Due Thursday Feb 9, 2006
Overview and Fundamentals
Competing on Analytics II
Dimensional Model January 14, 2003
Retail Sales is used to illustrate a first dimensional model
Display Item Information
CMPE 226 Database Systems April 11 Class Meeting
Introduction to Customizing Reports in SAP
Typically data is extracted from multiple sources
MIS2502: Data Analytics Dimensional Data Modeling
DataMart (Data Warehouse) Tool:
Assignment 2 Due Thursday Feb 9, 2006
Retail Sales is used to illustrate a first dimensional model
Data warehouse architecture CIF, DM Bus Matrix Star schema
Introduction to Customizing Reports in SAP
Aggregate Improvement and Lost, shrunken, and collapsed
MIS2502: Data Analytics Dimensional Data Modeling
On-Line Application Processing
Retail Sales is used to illustrate a first dimensional model
Role Playing Dimensions (p )
Dimensional Model January 16, 2003
Applying Data Warehouse Techniques
Aggregate improvement Lost, shrunken, and collapsed Ralph Kimball
Examines blended and separate transaction schemas
Review of Major Points Star schema Slowly changing dimensions Keys
Many aggregates can be defined for one base star schema
Slides based on those originally by : Parminder Jeet Kaur
Applying Data Warehouse Techniques
Review of Major Points Star schema Slowly changing dimensions Keys
Page 37 Figure 2.3, with attributes excluded
Data Warehousing.
Presentation transcript:

Inventory is used to illustrate: Chapter 3 Inventory is used to illustrate: Data warehouse architecture Bus Matrix Conformed dimensions Conformed facts Fact table types: periodic snapshot accumulating snapshot transaction Semi-additive facts In chapter 3, the focus is primarily on the periodic snapshot fact table January 2004 91.4904 Ron McFadyen

{Note: in Chapter 2 we examined a “transaction” fact table} Periodic Snapshot At regular intervals some metric is calculated and recorded in a fact table – could be daily, weekly, monthly, … but its done at regular predictable times. {Note: in Chapter 2 we examined a “transaction” fact table} e.g. Inventory Periodic Snapshot January 2004 91.4904 Ron McFadyen

Inventory Periodic Snapshot Date Product Store Inventory Snapshot Store January 2004 91.4904 Ron McFadyen

Inventory Periodic Snapshot Store Inventory Snapshot Each day the quantity on hand is recorded for each product and store We have a “snapshot” of inventory at the end of each day. Levels vary during the day, but we know what it is at the end-of-day. Date key Product key Store key Quantity on hand January 2004 91.4904 Ron McFadyen

Inventory Periodic Snapshot Store Inventory Snapshot An issue with this fact table is its size. See text for example … 30 GB each year Save space by: Reducing the frequency Reducing the number of days kept Date key Product key Store key Quantity on hand January 2004 91.4904 Ron McFadyen

Inventory Periodic Snapshot Store Inventory Snapshot Is the quantity on hand Additive? Semi-additive? Non-additive? Date key Product key Store key Quantity on hand Instead of adding quantities across time, if we average the metric, we may have a useful aggregation January 2004 91.4904 Ron McFadyen

Inventory Periodic Snapshot Store Inventory Snapshot Date key Product key Store key Quantity on hand E.g. Average inventory for a brand in a region for a given week? Product  brand {3 products} Store  region {4 stores} Difficult to do in SQL … January 2004 91.4904 Ron McFadyen

Inventory Periodic Snapshot Store Inventory Snapshot Date key Product key Store key Quantity on hand Quantity sold Value at cost Value at latest selling price Gross profit … Other useful facts January 2004 91.4904 Ron McFadyen

Other fact tables for Inventory Inventory Transaction Facts Inventory Accumulating Snapshot Facts January 2004 91.4904 Ron McFadyen

Warehouse Inventory Transaction Facts Product Date Warehouse Inventory Trans fact Date key Product key Warehouse key Vendor key Inventory trans type key Inventory trans dollar amount Vendor Warehouse Trans type January 2004 91.4904 Ron McFadyen

Warehouse Inventory Transaction Facts Transaction types: Receive Place in bin Authorize for sale Ship to customer Remove from inventory … January 2004 91.4904 Ron McFadyen

Warehouse Inventory Accumulating Snapshot Facts Provides an updated status of something as it moves through various states or milestones. Typically there are many dates – a date is related to each milestone. A record is placed in the fact table, and then updated as milestones are reached. One can measure the velocity of something moving through the system January 2004 91.4904 Ron McFadyen

Warehouse Inventory Accumulating Snapshot Facts Product Date received Warehouse Inventory Accumulating fact Date received key Date inspected key Date placed in inventory key Date authorized to sell key Date picked key Date boxed key Date shipped key Date of last return key Product key Warehouse key Vendor key …facts… Date inspected . . . Vendor How many Date tables are there? Warehouse January 2004 91.4904 Ron McFadyen

Warehouse Inventory Accumulating Snapshot Facts Product Date received Date inspected Warehouse Inventory Accumulating fact . . . Vendor The fact table must be updated from time to time (again in Chapter 5) Warehouse January 2004 91.4904 Ron McFadyen

The chapter illustrates several potential data marts. Conformed dimensions The chapter illustrates several potential data marts. To make best use of these, it is recommended that dimensions be reused. This allows us to query multiple stars and combine results. Multipass SQL : each star is queried separately and the results combined/merged. Querying multiple stars is referred to as drill-across e.g. What are the sales amounts for products that represent the top 80% of inventory value? January 2004 91.4904 Ron McFadyen

Conformed dimensions Dim 1 Fact table 1 Dim 4 Fact table 2 Dim 2 January 2004 91.4904 Ron McFadyen

Bus Architecture The Bus Architecture relates dimensions to data marts, promoting re-usability. As new data marts are added they plug into the architecture, reusing existing dimensions; adding others e.g. Time and Product dimensions are reused in the Orders and Production data marts Orders Production Dimensions Time Sales Rep Customer Promotion Product Plant Distr. Center January 2004 91.4904 Ron McFadyen

Data warehouses are built one data mart at a time - iteratively. Bus Architecture Data warehouses are built one data mart at a time - iteratively. This architectural framework relates each of these marts to one another. The objective is to build dimensions once, promote their reuse (the same dimension appears in many star schemas) and be able to deliver successive data marts faster. This architecture relies on building conformed dimensions and conformed facts. Conformed dimensions make it possible to perform analyses across data marts. January 2004 91.4904 Ron McFadyen

Likely between 10 and 30 data marts Bus Architecture One data mart at a time. Each project may be 3 to 6 months in duration. Data warehouse construction begins with a planning phase to identify potential data marts and dimensions. Create a matrix Likely between 10 and 30 data marts January 2004 91.4904 Ron McFadyen

Data Warehouse Bus Matrix A useful planning tool Business processes are rows; these become data marts Dimensions are columns Illustrates re-use of dimensions Illustrates complexities in data mart construction Can be used to guide which data mart to build first/next Recommendation for first data mart is one that is easy to build – limit the number and complexities in source systems January 2004 91.4904 Ron McFadyen

Matrix assumes that dimensions are re-usable Conformed dimensions Matrix assumes that dimensions are re-usable Different data marts either use Same table A synchronous copy A subset dimension Includes horizontal/vertical partition Includes roll-up dimensions (occur with aggregation – see figure 3.9) January 2004 91.4904 Ron McFadyen

This is a very disciplined approach to naming attributes. Conformed facts If facts are given the same name in two fact tables, they are conformed if they have the same definition and formula. If two facts are different in some way, then they must be given different names. This is a very disciplined approach to naming attributes. January 2004 91.4904 Ron McFadyen

Summary of topics Architecture Facts Additive Semi-additive Bus Matrix Conformed dimensions Conformed facts Facts Additive Semi-additive Non-additive Types of fact tables: periodic snapshot accumulating snapshot transaction January 2004 91.4904 Ron McFadyen