In the previous lessons, you learned how to follow each step to validate your data transition. But what if something goes wrong in one of the steps?
In this lesson, you will learn how to troubleshoot discrepancies in the Evaluate Data step of your data transition validation project.
Difference in the Records
For starters, watch a video explaining how to check for discrepancies shown in the result tab of the Data Evaluation step as "difference." This means there are a number of records that are different in the source and target systems.
Missing in Target
Now watch a video where you learn how to verify the situation in the case your data evaluation results show there are records missing in the target system.
Unexpected in Target
This time, the video below shows a situation in which your report shows unexpected records in the target system.
As you saw in the examples above, the data transition validation tool offers relevant information about your system data. If you want to double-check, you can use transaction code SE38. Also, to actually solve these discrepancies, you need to address the application team and show them the details as produced in the report.
Summary
After this lesson, you can verify the different types of discrepancies shown in the Data Evaluation report.