Building Making It Happen
Building Making It Happen
  Sign-in         Register
    
Principles and Rules Listing Page
Do not separate the parent and child line item data
In cases like invoice, purchase orders and Job Card, there are header items and detailed items. One should always combine both the levels into a single fact table.
 
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, Metadata Management, Core Data Management Tools,


The reasons for this is that there are many header level items like (discounts, taxes..) are calculated as a sum for all the line items.

A good dimensional table design would look for calculating the header items like discounts, taxes, transportation etc and allocate them to the individual items. This may involve some allocation rule, which may not be thoroughly scientific, but they will help in making better analysis.

For example, if I have an invoice containing 6 different items, I will have six records in the fact table, with each item having the freight (calculated for overall invoice) allocated to individual line items as per the sale value of the line item, and tax calculated as per the tax rules for the given product in the line item. Ideally the allocation rules should be kept simple or else you will get caught into hundreds of different rules related to these kind of calculations (for example free shipping for a product if bought within Christmas seasons..).

One has to make sure that the total rolled-up amount will be equal to the header amount in the invoice.

   Access more details on this page   

Quick Feedback- Was this information helpful ?
Relevant Links to this page
TOPIC - Data Mart Business Theme Matrix in Data Warehouse Dimensional Model → 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 → Principles & Rules → Add extra buffer for ETL phase → Principles & Rules → Homework before interviews is must (Business Requirements Phase in Data Warehouse) → Principles & Rules → Excel is the competition, which should be challenged → Principles & Rules → Avoid Pure MOLAP → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Consolidate Data-Marts → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Licensing & Maintenance Contracts → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Governance & Standards → Practice Techniques → Field Tips Series- Streamlining & reducing cost of Business Intelligence- Evaluate Open Source → Principles & Rules → Master Data Management- Making a Right Start → Practice Techniques → How to integrate stand-alone BI environments- Gradual Approach → Principles & Rules → Business owned applications are a reality- Manage it → Principles & Rules → New Data Standards- What about existing data and applications? → Principles & Rules → Handle Each Time-stamp in the Fact Table as a separate dimension → Principles & Rules → Keep Aggregates and Details data in different Fact tables → Principles & Rules → Some considerations for Infrastructure in Data Warehouse → Principles & Rules → For Core BI platform go for a single, established and robust player → Principles & Rules → Don't be guided only by the business requirements for your Business Intelligence → Practice Techniques → Using Synonyms and Views → 
 
Back
Featured Pages
Data-Warehouse Requirement Interview
Data Quality is not Perfect Quality
MDM- Account and Product Management
Data Mining Techniques- Predictive Modeling

Make 'Executable' Strategy
Maximize Results
Maximize People
Manage Execution

Featured Pages
Manage Leads Database Centrally
Root Cause of Data Quality Issues
BI Competency Centre Setup- Overview
Dimensional Attributes+ Facts + Source Matrix