Sales Management Customer Relationship Human Resources Business Performance BI & Data Quality IT Tools & Vendors

Sign-in   Register
Establishing 'Making it Happen' as a 'Formal & Predictable' Discipline
Principles and Rules Listing Page

Handling of Null foreign Keys in fact tables

There are always situations where the key linking the fact table to a dimension table is NULL (meaning it is not available or applicable).
 
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 "Order Delivery Date" key in "Orders" fact table, is a future date, as the order is still under processing. In this case the date is not available. The best way to handle it is to give a surrogate key, and have that surrogate key link to a record having a description (say) this date is yet not applicable. In case of an accumulating fact table, when the date happens, one can over-write the record.

Sometimes that foreign key is not available, due to the data quality issues of the source systems. In this case the approach is similar, and that is to assign a special surrogate key linking to a record in the dimension table. For example, if the invoice number is not available, you can assign a special surrogate key, which will link to a special record in the dimension table, which will have the description the "invoice number is not available". If you want to assign more specific reasons related to the invoice number not being available, you can think of having multiple special surrogate keys linking to multiple special records, with each carrying a different description. That helps you at a later stage in case you want to do some data enhancement/fixing.
The same approach will be applicable in case the fact.


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

Most Popular Zones with list of pages crossing 25000 hits  →→→ 
Maximising Sales Performance
Sales force density
Sales Compensation administration
telemarketing Sales Lead Generation
Sales Leads Classification and prioritization
Sales Objectives Clarity
Read more...
  Customer Relationship Management
Customer Satisfaction and Retention- Overview
Supply Chain for Customer Service and Support
Customer Satisfaction & Retention- Data Management
Exit barriers for Customer Retention
Customer Value and Profitability-Overview
Read more...
  Human Resources & Leadership
Feedback does not mean only negative feedback
What is Leadership?
Give feedback closer to the observation
Empower Front-line Employees
Develop Self and Others
Read more...
 
 
Business Performance & Planning
Business Objectives Drill Down
A KPI should be simple -but it depends
SWOT Analysis in Strategic blueprint Planning
External Info Assessment Report
Strategic Planning leadership commitment
Read more...
  Business Intelligence & Data Quality
Data Warehouse Testing is Different
Customer Data Searching and Matching
Data Mart Business Theme Matrix in DW
time-stamps for multiple time-zones
Time-stamp in the Fact Table
Read more...
  IT Vendors & Tools Management
Vendor Partnership and alliance Evaluation
Data Quality Tools Integration
OLAP Sever Database Tuning
Vendor Delivery Evaluation Training
Vendor Delivery Project Evaluation
Read more...