Converting to SAP S/4HANA: Custom Code Migration

1
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
2

The tool ABAP Test Cockpit (ATC), can be used to analyze the impact of conversion to
SAP S/4HANA, on custom code. ATC facilitates the adaption of the custom code to
SAP S/4HANA.
Would you like to learn about how you can use the ABAP test Cockpit to manage your
custom code activities related to SAP S/4HANA conversion? If so, follow this interactive
demo.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
3

(1) Enter ATC and press Enter.

(2) Choose Execute.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
4

The ABAP Test Cockpit opens.

Here you can find all the activities that can help you with analyzing your custom code.
(3) To schedule a new ATC check, double-click Schedule Run.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
5

(4) To schedule the job that checks the custom code of the source system, you have to
create a run series, with a Code Inspector Check Variant. The Code Inspector Check
Variant determines the checking criteria.
In this demo, the run series S4HANA_READINESS with the Code Inspector Check
Variant S4HANA_READINESS_REMOTE is already created. Select it.
(5) Choose Schedule.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
6

(6) Choose Execute.

The job scheduling is a success.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
7

(7) Choose Back.

(8) To view the details of the ATC checks, double-click Monitor and Control Runs.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
8

To display the log of the ATC check that you previously scheduled, you can enter it as
the run series.
In this demo, the run series S4HANA_READINESS is entered for you.
(9) Choose Execute.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
9

The ATC Run Monitor screen opens.

Here you can find the list of ATC checks scheduled and other details such as State,
Duration, Run Series.
(10) To see the results of an ATC check, select it.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
10

(11) Choose Result.

Here, you can view all the issues in the custom code that were collected during the ATC
check. The system also lists the Object Names where the error was found. These
objects have to be adjusted for SAP S/4HANA conversion.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
11

(12) To view additional information about an issue, double-click its Check Title cell.
In this demo, double-click the Check Title cell for the first issue.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
12

The details of the error displays. Here you can view the details of the issue such as the
Priority of the error, the program name and the line number where the error was found.
In this demo, there is a priority 1 error in line number 302 of the custom program
ZENGCHG0. In the SAP S/4HANA the field length for MATNR is 40 but the program
has a field length of 18.
(13) To navigate to the location in the code where error occurred, choose Display
Object.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
13

Here you can see that the error occurred in the code line 302 of the program
ZENGCHG0.
Note: From SAP NetWeaver 7.51 and higher, you can navigate to your source system
via RFC connection and adjust your code from ATC.
(14) To navigate to the declaration of the internal table type of the variable rtab, double-
click it.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
14

Here, you can you see that in the internal table type declaration, the length of the field
MATNR is 18 characters.
The ATC check resulted in an error because the MATNR field length in SAP S/4HANA
is 40 characters.
(15) Choose Exit.
CONVERTING TO SAP S/4HANA: CUSTOM CODE MIGRATION
15

This concludes the interactive demo.