QAD BI v3 – Tech Level 2 Certification - Part 2 > Troubleshooting > Troubleshooting – Too Much Data – Duplicate Records
  PPT
Troubleshooting – Too Much Data – Duplicate Records
Troubleshooting – Too Much Data – Duplicate Records
 
Business key values should never be null. If they are, there is a problem with either the data or the code.
Troubleshooting – Too Much Data – Duplicate Records
 
In earlier versions of BI (pre 3.5), there were quite a few problems with sliding historical date parameters and overlapping begin and end dates in the OM and PO order history tables. These would inevitably cause snapshot tables to fail when two same records with overlapping begin and end dates would get picked up by the snapshot table. The solution for these was to either delete one of the records or better still, set the begin and end dates of the records so they were no longer overlapping and wouldn’t get picked up by the snapshot for the same end of month/week date.
Troubleshooting – Too Much Data – Duplicate Records
 
If the column track back shows the data passes through a perm table, check the perm table to see if the record is there and if it is correct or not. Or at least jump back to the first table in the “landing strip” to the fact table. The “landing strip” tables are the final stage tables prior to a fact table that have all the records headed to the fact collated, but still need to calculate currency conversion rates and get dimension keys, etc. Examples would be stage_om_order1, stage_om_order2, stage_om_order3, stage_om_order.
Troubleshooting – Too Much Data – Duplicate Records
Troubleshooting – Too Much Data – Duplicate Records
Troubleshooting – Too Much Data – Duplicate Records
Troubleshooting – Too Much Data – Duplicate Records