Training Excel Report
The Training 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.
Obsolete
This spreadsheet all the used SAP standard transactions from the As-Is system that are either not available, or have been superseded by another transaction in the To-Be system. It includes each transaction’s program name, type, usage count, description, application area and development class.
- The OBS column is set to O if a transaction is obsolete in the To-Be system, or to R if a replacement transaction could be found. In this case, the replacement transaction is shown in the NEWTCODE column, and its description is shown in the NEWDESC column.
- The REL column indicates whether the transaction or its associated program is relevant. Non-relevant transactions or programs include IMG customizing activity programs, and objects matched in the UsedObjectsToIgnore External Data Source.
The Obsolete report is helpful in determining which transactions should be tested, and which transactions have been replaced with more current transactions in the upgraded system. It may also assist in deciding whether a custom development is really needed, or whether the new transaction may satisfy all the requested requirements.
System Info
This spreadsheet describes the As-Is and To-Be systems used in the analysis.