QAD BI v3 – Tech Level 2 Certification - Part 2 > Troubleshooting > Troubleshooting – Incorrect Data
  PPT
Troubleshooting – Incorrect Data
 
It can be helpful to also find an example that does not have the issue as a baseline to compare results to, but finding a problematic record is key. If the issue is being raised by a customer, ask them for a specific example, if they are willing to provide one. Some customers will just look at the total from 3 million records and say that the result is wrong. That provide much information to go on. If at all possible enlist their aid in finding a specific record that can be pointed at to say, “That record is wrong.”
Troubleshooting – Incorrect Data
Troubleshooting – Incorrect Data
 
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 – Incorrect Data
Troubleshooting – Incorrect Data
Troubleshooting – Incorrect Data
Troubleshooting – Incorrect Data