Testing Excel Report
The Testing Excel Report includes the following spreadsheets.
Standard
This spreadsheet lists used standard programs and transactions on the As-Is system that will impacted by screen changes on the To-Be system following an upgrade. The report list each used program and transaction, with its usage count and percentage change score that is based on a comparison of its component screens. The change score for a program or transaction is calculated as follows:
(Different + In1 + In2) / Total number of component screens * 100
In1 is the number of component screens that exist on the As-Is system only. In2 is the number of component screens that exist on the To-Be system only. Different refers to the number of component screens that are different on each of the systems.
The Standard report allows you to verify which standard SAP programs have had user interface changes introduced, and helps to provide an idea of the testing resources required for the upgrade. The report should be broken down by Application Area and given to the appropriate Functional Leads to review.
Custom
This spreadsheet identifies used programs and transactions that depend on SAP objects with significant differences on the As-Is and To-Be systems. Each used transaction or program is listed, followed by the SAP object that impacts it, and the comparison status of the impacting object on the As-Is and To-Be systems. The impacting object name is shown as a hyperlink which allows a detailed comparison report to be displayed. The user who last changed the program or transaction is also shown.
The Custom report lists the impacted programs, functions, includes, structures and tables called by your used custom programs. It is important to understand how these objects will respond to the custom programs in the upgraded system.
Interfaces
This spreadsheet lists the number of custom BDC interfaces on the As-Is system (identified by their use of CALL TRANSACTION or CALL DIALOG statements), and the number of standard and custom IDOC segments that would be impacted on the To-Be system following an upgrade. The count values provide an indication of the testing effort required.
System Info
This spreadsheet describes the As-Is and To-Be systems used in the analysis.