U.02 - Analyze Custom Code Quality
This workflow retrieves custom Programs, Includes and Function Modules from the specified SAP system, and performs a quality analysis of the ABAP code associated with these objects. The code is analyzed in order to identify potential quality issues in the following categories, which are part of the Upgrade analysis scenario.
| Column | Description |
|---|---|
| 700+ Kernel Systems | Identifies issues specific to SAP kernel release 700 and later releases. |
| ABAP Failures | Identifies ABAP code that may cause runtime errors in SAP 4.7 or later releases. |
| ABAP Objects | Identifies issues specific to ABAP objects. |
| BDC Interfaces | Identifies the use of CALL TRANSACTION and CALL DIALOG statements. |
| Complexity | Analyzes the complexity of the ABAP source code. |
| Documentation | Highlights issues relating to ABAP source code documentation. |
| Fan-in / Fan-out | Highlights objects that have a high fan-in or fan-out value (greater than 5). The fan-in value of an object is the number of other objects that are referencing it. Multiple references from the same object are counted as one access. The fan-out value of an object is the number of other objects that are referenced in it. Multiple references to the same object are counted as one access. |
| HANA | Identifies issues specific to SAP HANA ABAP source code. |
| Missing Code | Identifies issues specific to SAP HANA ABAP source code. |
| Obsolete Features | Identifies obsolete features in the ABAP source code. |
| Performance | Highlights issues that may affect the performance of ABAP source code. |
| Reliability | Highlights issues relating to the reliability of ABAP source code. |
| Runtime Error | Identifies potential runtime errors in the ABAP source code. |
| SAP internal use token | Identifies ABAP tokens that are intended for SAP internal use only. |
| Security | Highlights security issues in the ABAP source code. |
| Unreferenced Objects | Identifies unreferenced ABAP functions and includes. |
The results are stored in four Table datasets, which provide data for the Development and Testing Dashboard reports and Excel spreadsheets.
Creating RFC Destinations
Before you begin, you will need to create an RFC Destination for the SAP system you wish to analyze. S
Preparing the Workflow
To prepare the U.02 - Analyze Custom Code Quality workflow, drag its workflow template from the Templates folder into your own workspace, and modify the workflow as follows:
To specify the Current or As-Is system:
-
Select the System 1 parameter and choose ‘Edit RFC Destination’ from its context menu to display the RFC Destination dialog.
-
Select the RFC Destination for the system to analyze, then click ‘Save’.
To specify the scenarios, categories and rules to use in the analysis:
-
Select the AAQ Select List parameter and choose ‘Edit AAQ Select List’ from its context menu to display the AAQ Select List dialog.
-
Select one or scenarios, categories and rules from the hierarchy, then click ‘Save’.
Save the workflow using the ‘Save’ toolbar button.
Running the Workflow
To run the U.02 - Analyze Custom Code Quality workflow, click the 'Run' toolbar button, choose ‘Run Now’ from the diagram’s context menu, or press F5. The currently running workflow action is marked with an animated display. When the workflow execution has completed, select any of the following Table datasets and choose ‘View Details’ from their context menus to display the table contents.
-
Object Quality Score Card
-
Rule Break Summary
-
Rule Break Detail
-
BDC Interfaces
These tables are returned to the Run Complete Analysis workflow, and provide data for the Development and Testing Dashboard reports and Excel spreadsheets.