Best practices to follow during DTV implementation

abhyarthana · ‎2024 May 30

Best practices to follow during DTV implementation

Data Transition Validation or DTV tool can expedite the data validation process by pointing out the differences between source and target system state, hence eases the reconciliation process. Drawing experience from many different customers, we came up with some of the best practices customers can follow for optimum result.

These are some of the best practices which can be followed for maximum benefits.

During the conversion or upgrade planning

Understand the scope of the DTV tool early in the project planning phase. Check the blog for more information regarding the tool Business data validation using DTV tool
Finalize the test scope, which means finalize the reports which you would like to validate using DTV tool early in the project planning.

Finalize the data scope(volumes) that you want to validate, for example how many company codes, GL accounts, Fiscal year etc. should be used during the DTV configuration.
Use DTV tool for data validation in each cycle of the project (such as dress rehearsal, performance run cycle etc.) and improve the DTV run time (execution time) in each cycle to get optimum effect in the production run.
It is worth to mention that initial DTV test set up consume some time and this “estimated time” must be included in the project planning phase.

During DTV System preparation

It is recommended to use the latest and greatest version of the DTV tool. More info in SAP Note: 3117879 - Data Transition Validation DTV Tool - Central Note

Ensure to implement all DTV related SAP Notes for smooth execution.
Utilize the system resources such as executing server and executing group wisely to fine tune the performance of the DTV execution time.
Maintain optimal number of background jobs. The reports are executed via background jobs in DTV.
Make sure to maintain recommended values for SHMA configuration and memory parameter set up (RZ11)
- rdisp/PG_KEEP - value = 30
- rdisp/PG_MAXFS - value = 256000
- rdisp/PG_SHM - value = 256000
- abap/shared_objects_size_MB - value = 1800

You can also follow SAP Note 3226794 - SYSTEM_SHM_AREA_OBSOLETE error while using the DTV tool

Import the latest pre-delivered content.3258383 - DTV : SAP Pre- delivered Content

In the initial cycles, it would be good to have a copy of the source system post DTV source execution for reconciliation purposes later in the project (not mandatory, but recommended)
Make use of project export/ import functionality of DTV tool to save time and effort. Once a project is configured in one system, it can be exported and then imported to the subsequent system of the system landscape easily with this functionality.

During DTV configuration

For faster extraction and good performance split the data into small chunks to avoid long running jobs. e.g., Create multiple entry for company code in global project data
- Starting DTV 1.6 release, the tool introduces work item level execution which can be leveraged for data splitting.
- Check blog for more details: Work Item Level Execution in DTV - SAP Community
Import the report multiple times in case of different variant configured for same report.
If you are using variant for report execution, make sure it exists in all the systems where DTV runs.

DTV works only for the ALV (output type) and background executable reports. Make sure the variant you choose for report output is not classical list but one of the ALV outputs. For example: RFBILA00, by default has List output. If you use this in variant, then DTV will not result any data.
You can create multiple project global data definition for the same parameter. For example, company_code for fixed assets, company code for MM, and have different set of relevant company codes.
DTV executes a given report for each combination of values for the split parameter maintained. Hence you can control the granularity/ data volume of the execution by providing appropriate splits.
If the same parameter is specified in Split , variant and conditions : DTV will evaluate as mentioned in the help documentation
Use Simulation, until you find the right split size. It is not needed to execute Simulation post this.
- You can entirely skip executing Simulation in the final cycle and directly perform extraction
Ensure to define same input parameter for source and target system.
Ensure not to change the project global data in target system.
Make use of exclude parameter to specify fields that would be excluded from the validation.
Custom report with ALV output can also be validated using DTV tool starting DTV 1.4 Business Data Validation of Custom Reports using DTV

For custom reports, adjust the output keys in case the evaluation is not happening with the right keys.

During DTV execution

If Simulation is executed for any report, you can use the Import Simulation Results to avoid a second time extraction. Check the blog for more information on simulation Simulation made easy in DTV 1.4
The result data shows only 10 K records on load. In case you want to see all the records, click on the refresh button in the ALV toolbar.

Post DTV Execution

“DTV is not a reconciliation tool, but is a validation tool”, hence, in case of differences pointed out by the tool, user may/should consider following below steps as a quick check.
- Run the report in SE38 with same input parameters.
- Then, compare the results (obtained from SE38) with the DTV tool results.
- Reconcile the results in both source (copy of a source system) and target system to ensure the correctness of the tool.

Conclusion

DTV is an easy-to-use yet powerful tool which can help in business data reconciliation by showing the differences between the source and the target system automatically. After a successful Evaluation, DTV can only point out the discrepancies in the Target system (if any) and it is up to the users to perform the reconciliation.