Performing the Custom Code Analysis

Objective

After completing this lesson, you will be able to perform the custom code analysis.

Custom Code Analysis

The Major Technical Steps

The SAP standard changes in many ways when performing an SAP S/4HANA Conversion. In some areas, the entire data model changes. Often, however, the modifications and the own development won't work anymore because it's integrated with the SAP standard.

Why Custom Code Adoption is Necessary
Custom Code Migration Overview

Custom Code Scoping: Custom code scoping enables you to determine the ABAP custom code that is frequently used and must be taken over to SAP S/4HANA. Unused custom code can be deleted using deletion transport requests during the system conversion. Scoping enables you to reduce the number of custom codes to be migrated and to minimize the efforts of the custom code adaptation.

Custom Code Analysis: Custom code analysis enables the developer to identify the custom code that must be adapted in the context of the system conversion to SAP S/4HANA.

Custom Code Adaptation (Functional Adaptation): After the system conversion, the developers must perform the functional adaptations in the custom code. In the system conversion, the developers must adapt any modifications with SPDD and SPAU. After this, the ABAP Test Cockpit (ATC) must be used with SAP S/4HANA checks in ABAP development tools for Eclipse. The result is a list of ATC findings that relate to SAP S/4HANA simplifications and refer to SAP Notes that describe how to solve the issues. Based on these ATC findings, the developers can start adapting the custom code using quick fixes in a semi-automated way.

Performance Tuning: Finally, the developers need to check which business processes, for example, performance of critical database queries, need to be optimized in SAP HANA DB. To do this, the developers need to check which SQL statements can be optimized. The relevant performance data for all SQL statements executed in the productive system is displayed. Here, the developers can find the most expensive business processes and the most frequently used SQL statements.

To perform the custom code analysis, a central check system is needed. There are three possibilities: an AS ABAP 752 system, an SAP S/4HANA Server 1809 and above, or an app in SAP Cloud Platform can be used.

ATC: Terms

You can use one central ATC check system for several SAP system landscapes (groups) with different releases.

ABAP Test Cockpit (ATC)

For setting up and performing the custom code migration, use the Custom Code Migration Guide.

In the checked SAP system, the SAP Notes 2485231, 2270689, and 2190065 have to be implemented.

The central check SAP system must be SAP_BASIS 7.52 and above. In the central check SAP system, the SAP Notes 2436688, and 2364916 have to be implemented. These SAP Notes contain many other SAP Notes, to be implemented manually.

In the central check SAP system, download and upload the Simplification Database.

Import the Simplification Database as a ZIP File into the central check SAP system.

Upload Simplification Data

Download the Simplification Database from the SAP Support Portal using SAP Note 2241080.

Log on to your SAP system where you want to perform the custom code checks.

Upload the Simplification Database via transaction SYCM: choose Simplification DatabaseImport from ZIP File.

Configuring the Central Check System

To run the analysis In the SAP system, perform the configuration for the Remote Code Analysis in ATC:

  1. Call transaction ATC.
  2. Double-click System Role. Choose Settings and choose DisplayChange. Select ATC Checks by Object Providers Only and choose Save.
  3. Go back to the initial screen of ATC.
  4. Double-click Object Providers.
  5. Add a new system group as follows: 1. Double-click the item System Groups, 2. Switch to change mode (table is cross-client), 3. Choose New Entries.
  6. Enter an ID and a Description for the system group to be added.
  7. Save the new entry.

Add new object providers as follows:

  1. Double-click the item RFC Object Providers.
  2. Switch to change mode and then choose New Entries.
  3. Enter an ID, a Description, a System Group, an RFC Connection, and an SAP System.
  4. Save the new entry.

Add a correction system as follows:

  1. Double-click the item Correction System.
  2. Switch to change mode and choose New Entries.
  3. Enter an ID, an RFC Destination, a System Group, and an SAP System.
  4. Save the new entry.
Performing Central Check Runs

To perform the analysis in the SAP system, schedule a Run Series for the Remote Code Analysis in ATC:

  1. Go back to the initial screen of ATC.
  2. Double-click Schedule Runs.
  3. Choose Create.
  4. Enter a name for the Run Series.
  5. As Check Variant enter S4HANA_READINESS_REMOTE.
  6. As Object Provider, enter the one you created.
  7. As Package, enter Z*, for example.
  8. Choose Save – do not leave this screen.
  9. Mark the Run Series that you created and choose Schedule and the Run Series you created.
  10. Choose Execute.
Evaluating the Results: Example

Evaluate the results of the Remote Code Analysis in ATC via transaction ATC:

  1. Go back to the initial screen of ATC.
  2. Double-click Monitor and Control Runs. Double-click the run and check the results. Also, change to Statistic View.

You can also evaluate the results via transaction SE80. Choose UtilitiesSettings. Select ATC Result Browser and confirm. Choose the button ATC Result Browser and check the results.