Development Excel Report
The Development Excel Report includes the following spreadsheets.
Used
This spreadsheet lists the objects that are used on the As-Is system according to the available performance history data. Each used program and transaction is listed, along with its application area, development class, standard or custom flag, usage count (in the USAGE column), last modifier details and relevance flag. Non-relevant transactions are specified in the UsedObjectsToIgnore External Data Source.
The USERS and LOCATIONS columns refer to user statistics, which are not calculated for the report. These columns are set to contain the default value 0.
High volume programs and transactions run by a large number of users should be reviewed by the Project Manager and Functional Leads to verify if they are applicable to the upgrade. This may affect the scope of testing if critical executables are not already included in the scope.
Unused
This spreadsheet lists custom objects on the As-Is system that are unused according to the available performance history data. Each unused program and transaction is listed, along with its application area, development class and last modifier details. Custom objects that are not programs are removed from the results. These include subroutine pools, module pools, and function groups unless they are associated with a custom transaction code.
The Unused spreadsheet should not be taken at face value, and all the identified programs and transactions should not be deleted from the upgraded system. It may be possible that some of them were run outside the time period for which performance history data was available. Instead, the report should be split up by application area (or development class if this provides a better segmentation), and each subset handed to the Functional Leads or ABAP Developers for review. Based upon their Yes/No feedback, the set of programs and transactions that may be retired during the upgrade can be readily identified.
Because there is so much work involved after an upgrade, this report will help you save a large amount of time by identifying which code is no longer required in the To-Be system. It will eliminate the need to continue managing potentially thousands of unused programs and transactions after any upgrade service packs or support stacks have been applied.
Impacted~Top Down
This spreadsheet identifies used custom 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.
Impacted~Bottom Up
This spreadsheet identifies used custom programs and transactions that depend on SAP objects with significant differences on the As-Is and To-Be systems. Each SAP object is listed, followed by the used transaction or program it impacts, 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.
Impacted~SSFO
This spreadsheet identifies smart forms that depend on SAP objects with significant differences on the As-Is and To-Be systems. Each smart form 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 Impacted~Top Down, Impacted~Bottom Up and Impacted~SSFO reports list the impacted programs, functions, includes, structures and tables called by smart forms or your used custom programs. It is important to understand how these objects will respond to the smart forms or custom programs in the upgraded system.
BDC
This spreadsheet identifies custom objects that call SAP transactions using the CALL TRANSACTION statement, or dialog modules using the CALL DIALOG statement. Each CALL TRANSACTION or CALL DIALOG statement is shown, along with its line number in the source code, and the name of the called transaction or dialog module. The VARIABLE column is set to Y for transactions or dialog modules that are called using a variable.
This report shows that custom code can be dramatically affected by an upgrade. Standard SAP transactions are used by custom code. If a standard SAP transaction is changed following an upgrade, then the custom code that uses it will be affected and may fail at runtime.
Complexity
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying each object’s code complexity. Each object is given a complexity score and assigned to either the Good, Bad or Ugly complexity category.
Source code for objects in the Ugly or Bad categories may be reviewed to identify any possible performance improvements.
HANA
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying issues that relate to HANA environment. Each HANA rule violation is listed, along with the matching token, the source code that violated the rule, and its associated line number.
The source code should be reviewed to identify any possible coding improvements.
ABAP Objects
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying issues that relate to ABAP objects. Each ABAP Objects rule violation is listed, along with the matching token, the source code that violated the rule, and its associated line number.
The source code should be reviewed to identify any possible coding improvements.
700+
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying issues that relate to kernel systems 700 and above. Each 700+ rule violation is listed, along with the matching token, the source code that violated the rule, and its associated line number.
The source code should be reviewed to identify any possible coding improvements.
Documentation
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying documentation issues. Each Documentation rule violation is listed, along with object that violated the rule.
The source code should be reviewed to identify any possible documentation improvements.
Error
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying issues that may cause runtime errors. Each Error rule violation is listed, along with the matching token, the source code that violated the rule, and its associated line number.
The source code should be reviewed to correct the issues that may cause runtime errors.
Failures
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying issues that may cause ABAP failures. Each Failures rule violation is listed, along with the matching token, the source code that violated the rule, and its associated line number.
The source code should be reviewed to identify serious ABAP failures. These may result in performance issues or system dumps.
Fan-in Fan-out
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code. Each Fan-in Fan-out rule violation is listed, along with object that violated the rule.
The source code should be reviewed to identify any possible coding improvements.
Missing
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying ABAP structures or statements that have missing code. Each Missing rule violation is listed, along with the matching token, the source code that violated the rule, and its associated line number.
The source code should be reviewed to identify any possible coding improvements.
Internal
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying ABAP tokens that are intended for SAP internal use only. Each Internal rule violation is listed, along with the matching token, the source code that violated the rule, and its associated line number.
The source code should be reviewed to remove any ABAP tokens that are intended for SAP internal use only.
Obsolete
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying obsolete features. Each Obsolete rule violation is listed, along with the matching token, the source code that violated the rule, and its associated line number.
The source code should be reviewed to remove any obsolete features.
Performance
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying performance issues. Each Performance rule violation is listed, along with the matching token, the source code that violated the rule, and its associated line number.
The source code should be reviewed to implement the identified performance improvements where possible.
Reliability
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code identifying documentation issues. Each Reliability rule violation is listed, along with the matching token, the source code that violated the rule, and its associated line number.
The source code should be reviewed to identify any possible coding improvements.
Security
This spreadsheet reports on custom objects on the As-Is system and performs a quality analysis of their associated ABAP code, identifying security issues. Each Security rule violation is listed, along with the matching token, the source code that violated the rule (if applicable), and its associated line number (if applicable).
The rule violations should be reviewed to identify whether any security improvements could be made.
SPDD
This spreadsheet identifies SAP objects on the As-Is system that have been modified, and are included in one or more imported support packs or transports. Objects in this report have a type of ENQU, SHLP, TYPE, INTF, TABL, VIEW, DOMA, DTEL or TTYP. These objects may need to be adjusted using transaction SPDD.
SPAU
This spreadsheet identifies SAP objects on the As-Is system that have been modified, and are included in one or more imported support packs or transports. Objects in this report have types other than those in the SPDD report. These are repository (ABAP) objects that may need to be adjusted using transaction SPAU. Click a link in the OBJ_NAME column to display an Object Differences report for the selected object.
The SPDD and SPAU reports should be reviewed to identify support pack or transport objects that may need to be tested following an upgrade.
System Info
This spreadsheet describes the As-Is and To-Be systems used in the analysis.