Impacted Custom Code app

The Impacted Custom Code app identifies the used custom code impacted by SAP changes during the build phase of a Support Pack or Enhancement Pack upgrade. An ABAP quality analysis is performed for the used impacted custom code in the As-is system, using the specified quality categories.

A user with LiveCompare Editor privileges must prepare this app by running the Create Object Links Cache workflow for the ‘As-is’ RFC Destination, and making sure that performance history data is available for the ‘Production’ RFC Destination. See the ‘Prerequisites’ section below for details.

DevOps categories

Development.

Prerequisites

Before running the Impacted Custom Code app for the first time, you will need to run the Create Object Links Cache workflow from the Prerequisites package to create an object links cache database for the As-is system. Check the system’s RFC Destination in the LiveCompare hierarchy first, and select the OLC tab to verify whether an object links cache database has already been created. The Create Object Links Cache workflow may be run incrementally to update the object links cache database with any recent object dependency changes.

You will also need to make sure that performance history data is available on the RFC Destination selected for the ‘Production’ system. Select the RFC Destination in the LiveCompare hierarchy and click the PHD tab. Select the source for performance history data, and if necessary the number of months of data to retrieve, then click ‘Update Data’. The performance history data may also be retrieved using a schedule. See the Retrieve performance history data help topic for details.

Run the app

To run the Impacted Custom Code app, select the app from the Apps screen and create an app variant. Complete the variant screen as follows:

  • Set the ‘As-is’ field to the RFC Destination for your As-Is system.

  • Set the ‘To-be’ field to the RFC Destination for your To-Be system.
  • Set the ‘Production’ field to the RFC Destination for your Production system.
  • Edit the ‘AAQ Select List’ parameter if required to specify the quality scenarios, categories and rules to be used in the analysis.

Click ‘Run’. When the variant has completed, its results may be accessed from the App Cockpit screen.

App results

The Impacted Custom Code app generates a Dashboard report which includes the following charts.

IMPACT

  • The Impacted by Type column chart provides a summary of the impacted objects, grouped by object type. The number of used and impacted objects is indicated for each type.
  • The Impactful Objects column chart provides a summary of the impacting SAP objects, grouped by object type.
  • The SPDD & SPAU column chart provides a summary of the objects that may need to be adjusted using transactions SPDD and SPAU following an upgrade.

QUALITY

  • The Analyze ABAP Quality column chart provides a summary of the quality rule violations in the used impacted custom code from the As-is system, grouped by rule category.

USAGE

  • The Standard vs. Custom pie chart displays a usage summary for the standard and custom code objects on the As-is system.
  • The Top DevClasses (Used Custom) column provides a summary of the used custom code assigned to the top 5 development classes on the As-is system.
  • The Used vs. Unused Custom pie chart displays a usage summary for the used and unused custom code objects on the As-is system.

The Dashboard report also includes links to the following reports:

Details

This Excel report includes the following spreadsheets:

Help

This spreadsheet provides help for each of the spreadsheet reports.

Home

This spreadsheet includes the charts displayed in the app’s Dashboard report, a summary of the RFC Destinations for the As-is, To-be and Production systems, and a date summary of the performance history data retrieved from the Production system.

Impact

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.

Imp~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.

Imp~SPAU SPDD

This spreadsheet identifies SAP objects on the As-is system that have been modified, and are included in one or more support packs or transports. Objects with an ADJUST_TYPE of SPAU may need to be adjusted using SAP transaction SPAU following an upgrade; objects with an ADJUST_TYPE of SPDD may need to be adjusted using SAP transaction SPDD following an upgrade.

Quality

This spreadsheet provides a summary of the ABAP quality results for each of the used impacted custom objects with code on the As-is system. The name of each object is listed along with its score for each of the quality categories used in the analysis.

Qual~Details

This spreadsheet provides details for the ABAP quality analysis performed for each of the used impacted custom objects with code on the As-is system. The appropriate line of ABAP code is shown for each object for which a rule violation occurred.

Qual~BDC

This spreadsheet provides details for ABAP quality rule violations in the for rules in the ‘BDC Interfaces’ category. CALL TRANSACTION and CALL DIALOG identified in used impacted custom objects with code on the As-is system. 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.

Usage

This spreadsheet lists the objects that are used on the As-is system according to the available performance history data obtained from the Production system. Each used program and transaction is listed, along with its application area, development class, total usage count, number of users, top user and top usage. Business critical objects are obtained from the Business Critical Objects External Data Source.

Analysis Input Data

This Excel report contains a copy of the input parameters used to produce the app’s Dashboard report. The value of each input parameter is stored in a separate worksheet, which is named after the parameter whose value it contains.

Standard apps