- SAP Managed Tags:
In part two of this series, I will share with you some helpful tips for setting up the DTV project Step 4 Project Global Data and Step 5 Define test specifications.
In this blog I provide insights based on my Finance perspective and what I believe to be significant from my experience with testing the tool. You should however be aware that DTV is also able to gather data from other functional areas, such as Plant Maintenance, Material Management, Sales, Warehouse Management, and Production Planning (as of the DTV 1.4 release). The tips I provide here may not be directly applicable to areas outside of Finance.
My DTV project
Step 4 - Project Global Data
The fields that are outlined under Project Global Data define the values that will be used to specify limitations for all the reports in the project. For financial data I suggest including (at a minimum) Company Code selections into this section. This will help prevent out-of-memory errors in the Simulation step when the report may attempt to access too much data at runtime.
Step 5 - Define Test Specification
In this section, you can enter additional filter parameters to limit the report data required for the specific business case.
In this blog, I will highlight several tabs that I consider significant and that had a deep influence on my tests. For an complete explanation of the test specifications tabs and functionality of the tool, please refer the Business data reconciliation using DTV tool - SAP Community blog post.
To start defining the test specification, highlight (click on) a specific report and the specification details are displayed at the bottom of the screen
Test Specification>Condition tab
The fields that are outlined in this tab determine the parameters that will be used to execute the report. These parameters can be single values or ranges.
The Conditions tab can also be defined for the pre and post converted system. In my case I entered parameters for the “ERP” system (pre-converted system) and for these reports I entered the same parameters for the “S/4HANA” ((post-converted system).
The mandatory report fields will appear automatically. If you need to add more, press <F4> to view the full list of accessible fields.
Test Specification>Variant tab
If you are interested in using a variant to execute the report then define its use in this section.
DTV is specifically designed to process most reports with an ALV output lists. It is therefore essential when using a variant that that variant specifies an “ALV Grid" output type.
SE38>RFBILA00 Variant ZSTEP04
Test Specification >Output Keys tab
The Output Keys define the specific fields that are used by DTV for comparison of data in the ERP and S/4HANA system.
If the Output Keys are not defined (the tab is blank), then the report output’s field catalog keys will be considered for comparison by default.
Even though the DTV tool may not explicitly display the field catalog output keys, you can see them in Step 6 - Evaluate Data.
Conclusion
In summary, Data Transition Validation (DTV) is a tool available for SAP S/4HANA conversion and upgrade projects. The tool can help organize and automate data collection (before and after conversion/upgrade). DTV eliminates the manual reconciliation efforts by automatically determining if the values in the ERP system (before) and S/4HANA systems (after) align and match. Only after data validation is certified and determined to be accurate and complete should the conversion/upgrade project be confidently re-opened to the business user community.
Please “like” if you found this blog post interesting!
Please add in the comment section any additional topics you think are valuable to have included in this and future blog posts.
– Brought to you by the S/4HANA RIG
