Building Making It Happen
Building Making It Happen
  Sign-in         Register
    
Principles and Rules Listing Page
Handle different units of measure in the same fact table
Create separate fields for each different unit of measurement, either by writing the conversion factor or the converted value.
 
This page of 'Principles and Rules' is linked to:  Data Warehousing, Data Analysis/OLAP, BI platform Tools Evaluation, BI business intelligence end-to-end view,


For example, production volumes can be expressed in number of units, number of "production lots/Batches", number of shipment packs..

There are two ways to handle this requirements:

  • Have one field carrying the lowest granular unit of measure (like units of production), and have additional fields to carry the conversion factor between the granular unit of measure and higher units of measure (like 12 when the unit of measure is 'dozens'). As the OLAP gets populated from the data warehouse, the conversion factors can be applied to calculate the measures in different units OR the calculation can be done on the runtime basis.
  • Have one field carrying the lowest granular unit of measure (like units of production), and have additional fields to carry the measures in other units (like 1000 dozens against 12000 units of production).
   Access more details on this page   

Quick Feedback- Was this information helpful ?
Relevant Links to this page
Principles & Rules → Data Warehouse application is not limited to Analytics → Principles & Rules → Store as much detailed and granular data in data warehouse as possible → Principles & Rules → Data Normalization is not the best approach in Dimensional modeling → Principles & Rules → Keep the same names and definitions for all data elements → Principles & Rules → You cannot have a super-flexible Data warehouse → Principles & Rules → Dimensional models can be extensible and scalable → Principles & Rules → Data Marts should be ideally based upon a business process and not on a department. → Principles & Rules → Business Intelligence competency groups should be well-linked with business → Practice Techniques → Aggregation Queries on slowly changing Dimensions → Practice Techniques → Documenting your data-integration system → Principles & Rules → For a Data Warehouse/Data-Mart solution, analyze well, but be decisive → Principles & Rules → Maintain a trail of the key dimensional elements from source system to loaded → Principles & Rules → Conformed dimensions are must for cross-drilling → Practice Techniques → Checksum Approach for identifying the changed records from source systems → Principles & Rules → Dimensional model has to be aligned to the Entity-Relationship → Principles & Rules → Always Use Conformed Dimensions → Principles & Rules → You may not be a able to have a perfect ETL → Practice Techniques → Handling Sparse Dimensional tables → Principles & Rules → Do not separate the parent and child line item data → Practice Techniques → Managing time-stamps across multiple time-zones → Practice Techniques → Recording events in multiple currencies → Practice Techniques → Handle different units of measure in the same fact table → Principles & Rules → Handling of Null foreign Keys in fact tables → Principles & Rules → Dimension Attributes as NULL → Principles & Rules → Don't rely too much on Meta Data Tools to enforce Business Intelligence → Principles & Rules → Don't wait for universal models for Data Marting → 
 
Back
Featured Pages
Business Intelligence link to business
Data Quality Monitoring
BI Competency Centre- Establish Phase
Documenting data-integration system

Make 'Executable' Strategy
Maximize Results
Maximize People
Manage Execution

Featured Pages
Capabilities- Foundation & Transaction MDM
Data Warehouse Testing Categories
Data Monitoring through diagnostics
Data Warehouse Data Quality assurance