10Steps2S4 – Installed Base Conversion
Version: 1.0 – February 2024
STEP08 – Custom Code adaptation
Table of Contents
1 Introduction ................................................................................................................................... 3
2 Documentation Links ...................................................................................................................... 4
3 Local checks using ABAP Test Cockpit (ATC) ....................................................................................... 5
3.1 Remove ATC inconsistencies ............................................................................................................ 5
3.2 Import the simplification database ................................................................................................... 5
3.3 System role .................................................................................................................................... 6
3.4 Fix error “CCA is not filled yet” ......................................................................................................... 6
3.5 Configuring and scheduling Local ATC Run Series ............................................................................... 7
3.6 Check the result.............................................................................................................................. 8
4 Custom Code adaptation ............................................................................................................... 10
4.1 Connect to ADT and access the result.............................................................................................. 10
4.2 Quick Fixes in ADT ........................................................................................................................ 14
4.3 Mass enabled Quick Fixes .............................................................................................................. 17
1 Introduction
After you did the system conversion to SAP S/4HANA with Software Update Manager (SUM) we recommend to run ATC
with SAP HANA and SAP S/4HANA checks. After that you need to carry out functional adaptation based on the ATC results.
In this step you need to fix SAP HANA and SAP S/4HANA findings. Adapt your custom ABAP code, using the findings of
the SAP HANA and SAP S/4HANA checks (ATC results). Findings of SAP S/4HANA checks are related to S/4HANA
Simplifications. Each simplification requires a different approach to solve findings. Therefore, findings of SAP S/4HANA
checks refer to a SAP Note which describes how you can solve them.
10Steps2S4 – Installed Base Conversion P age |3
2 Documentation Links
Below are the links to various S/4HANA On Premise documentation to be used as reference to the installation.
Documentation
SAP S/4HANA System Conversion – Custom code adaptation process
10Steps2S4 – Installed Base Conversion P age |4
3 Local checks using ABAP Test Cockpit (ATC)
To check for ATC findings in the converted system, you need to configure a local ATC run series that checks the
requested development objects.
3.1 Remove ATC inconsistencies
1. Go to transaction SA38 and execute the report SATC_CORRECT_INCONSISTENT_IX
2. The report does not provide any output hence if you don’t see any result but just a redirect to the same screen
from which you executed the program it means everything was executed successfully,
3.2 Import the simplification database
To check your custom code against the SAP S/4HANA simplifications, you need to import the Simplification Database
into the Central Check System.
1. Open the SAP Support Launchpad with the following URL
https://launchpad.support.sap.com/#/softwarecenter/search/CCMSIDB
2. Download the latest version of Simplification Database form the result.
3. Transfer the file to the terminal server.
NOTE: In case you are not authorized to download the file from the SAP Download Center you can find a recent
version of the Simplification Database in the Terminal Server (10.0.0.41) located in the folder
„C:\temp\10Steps2S4“ and named „ CCMSIDB00P_17-80001018.zip“.
4. In your converted system (K<XX> where XX is your group number) call transaction “SYCM”
5. In the menu select the option More → Simplification Database → Import ZIP File
6. Choose the ZIP file downloaded previously and confirm
7. Confirm and accept the warning to access to the file.
10Steps2S4 – Installed Base Conversion P age |5
8. Wait the program to complete and check the successful execution.
NOTE: The import may take up to 40 minutes.
9. To check the import, go back to main screen of transaction SYCM and in menu Simplification
Database and select option Show Overview
10. In the overview screen you can select multiple items and press Show items for selection to see the
associated objects.
3.3 System role
1. Run transaction ATC.
2. On the left menu select the option System Role.
3. Check that the option Local ATC Checks Only.
4. If not change the configuration to the option Local ATC Checks Only and save.
3.4 Fix error “CCA is not filled yet”
This step is required to resolve an error shown in transaction ATC and related to a bug.
Note 3242711 - ST-PI SP20 Corrections: ATC and Custom Code Cluster Service provides more information.
1. Call transaction SNOTE
2. Download and implement SAP Note 3242711
3. When required provide a new Transport Request to include the note implementation
4. Confirm the successful note implementation
10Steps2S4 – Installed Base Conversion P age |6
3.5 Configuring and scheduling Local ATC Run Series
Now that the Simplification Database is updated you can proceed by creating a new local series in ATC.
1. Run transaction ATC.
2. In the navigation pane, expand the nodes ATC Administration → Runs and double-click the Schedule Runs
entry. The screen that appears displays a list of existing run series.
3. Choose the Create button in the toolbar.
4. Enter a name for the new series and confirm.
5. Specify the following entries for the new run series:
6. Save the configuration.
7. In the list of run series, select the run series in question and click the Schedule button in the toolbar.
8. In the dialog that appears, choose Set to Active Result.
9. Adapt the settings for the Life Span of the series and for Execution to your needs. Otherwise, leave these
settings unchanged.
10. Choose Execute in Background (F9) to schedule the run series and choose “Immediate” in the schedule.
10Steps2S4 – Installed Base Conversion P age |7
3.6 Check the result
Now that the analysis has been executed successfully, we can check the result from ABAP Test Cockpit.
1. Call transaction ATC
2. Select “Monitor and Control runs” and wait until your planned run is set to State: Completed
3. Select your run from the list and press the button
4. Now we have access to the results. Here you can check the different object in detail by double-clicking in the
entries. In the details you can also see the note number containing information about the type of fix
potentially required.
5. Select all objects and then press the button (Change Contact Person) and insert your username in the
resulting pop-up (e.g. 10STEPS2S4). This will assign all these results to your user for further analysis and
resolution. You can use this functionality to organize the work in a project and assign different objects or
categories to different developers.
10Steps2S4 – Installed Base Conversion P age |8
6. If you click the button “Statistics View” you will get access to a summary of the resulted items organized by the
different category checks.
7. If you expand the different categories, you can see the single checks and double clicking on it you have the list
of objects containing the potential issue.
8. If you now click on the object name you will be redirected to the source code where you will be able to see the
code directly with the relevant instructions highlighted.
9. Now you can continue the analysis by selecting the different objects listed and verifying what is the impact and
the required fix.
10Steps2S4 – Installed Base Conversion P age |9
4 Custom Code adaptation
In this exercise, you’ll
• Use ATC in ABAP Development Tools for Eclipse
• Check your custom programs for SAP S/4HANA readiness with ATC
Work with your ATC results and fix the ATC findings one by one.
4.1 Connect to ADT and access the result
1. Double click on the Eclipse icon
on the desktop to launch the
ABAP Development tools for
Eclipse
➔ If not defined, select a
dedicated workspace. (e.g.
C:\temp\10Steps2S4\WSxx)
2. From the menu Windows
choose Perspective, Open
Perspective, and then other..
3. Select ABAP and confirm with
Open.
4. Close the Welcome screen to
see the new perspective with all
the relevant sections.
10Steps2S4 – Installed Base Conversion P a g e | 10
5. Create an ABAP Project, the
central interface between the IDE
and the ABAP backend system.
6. In the next screen select your
system or fill all the details to
connect to your converted
S/4HANA system
7. You are asked to provide the
logon information for your
system.
Client: 100
User: 10steps2s4
Password: jk366SAP
Click Finish button.
The ABAP Project will be added
in the left column.
10Steps2S4 – Installed Base Conversion P a g e | 11
8. Now go to the menu Window and
navigate to Show view and select
Other…
9. Search for ATC and select the
view ATC Result Browser.
Click Open to confirm.
10. Switch to the tab ATC Result
Browser.
Expand the folder and click on
Active Results…
10Steps2S4 – Installed Base Conversion P a g e | 12
11. Choose Group By → Check to
display the ATC findings sorted
by the different checks of the
check variant
S4HANA_READINESS.
12. Select the check group
S/4HANA: Search for S/4
related syntax errors and
choose Recheck in the context
menu.
13. You can now select – by double
clicking on - the first result for
example and see the description
in the right tab.
At the same time the source
code will be opened in the main
screen and all the errors are
highlighted in red together with
the description.
10Steps2S4 – Installed Base Conversion P a g e | 13
4.2 Quick Fixes in ADT
1. In the result right click on the
“Active result: …“ entry and
select “Recheck”.
This will run a new check
that can take up to 10
minutes to be completed.
At the end of the check a
new tab will be opened with
the title “ATC Problems”.
2. Right click the first error you
can find with the icon
For example Field
“VBTYP_AUFTR” is
unknown.
Click the option “Quick
Fix…”.
10Steps2S4 – Installed Base Conversion P a g e | 14
3. In this case the quick fix
proposes the solution to
replace the table with a
corresponding view.
Confirm with Finish.
4. Now we need to activate the
new version of the program
by using the activate button
in the main bar.
The system will ask you to
select a transport request or
create a new one.
5. Now right click on the same
result on the “ATC Problems”
tab and select the option
“Recheck”.
10Steps2S4 – Installed Base Conversion P a g e | 15
6. Now the error is disappeared
and for the same program
we just have additional
warnings.
In this case if you right click
on one of the warnings and
try the Quick Fix option you
will see that only the pseudo
comment to ignore the
warning is offered.
10Steps2S4 – Installed Base Conversion P a g e | 16
4.3 Mass enabled Quick Fixes
1. In the ATC Problems tab you
can now switch back to the
previous result by clicking the
last part of the path “Last Check
Run” on the top and selecting
the previous result.
2. Group objects by check and select
all entries in Errors.
3. Select all entries in this check
(CTRL+Click). Once all content is
selected right-click in any of the
entries and from the menu select
“Recommended Quick Fixes…”
10Steps2S4 – Installed Base Conversion P a g e | 17
4. In the result screen you can check
all available Quick Fixes that can be
applied in a mass way.
5. By clicking on “Group by Object”
you can check the Quick Fixes that
will be applied for every object.
6. In the Post Processing section you
can see that by default the
procedure also includes the
activation of the objects and a new
check run to verify the result.
Activate both checkboxes and press
Next to continue.
10Steps2S4 – Installed Base Conversion P a g e | 18
7. In the next screen you can see the
list of affected object and the
transport request automatically
selected to contain all the changes.
Press Next to continue.
8. If you don’t see a transport request
automatically assigned you can
create a new one by clicking on the
Browse button and entering the
required details.
9. In this step you can check the code
fixes that will be applied.
After checking the details press
Finish to apply all the fixes.
10. Wait for the process to be
completed. This can take up to 5
minutes.
10Steps2S4 – Installed Base Conversion P a g e | 19
11. Once the process is completed you
can select again all results from one
check group and choose the option
“Recommended Quick Fixes…” to
check for additional
recommendations.
12. You can now continue to check the
additional errors (you should see
around 138) and solve them
manually by looking at the code and
referring the notes for additional
information.
13. ATC Result Browser gives you the
best overview to proceed with the
corrections.
10Steps2S4 – Installed Base Conversion P a g e | 20
www.sap.com/contactsap
© 2024 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or
for any purpose without the express permission of SAP SE or an SAP affiliate
company.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors. National
product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or SAP
affiliate company products and services are those that are set forth in the
express warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional
warranty.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. All other product
and service names mentioned are the trademarks of their respective
companies. Please see www.sap.com/corporate-
en/legal/copyright/index.epx for additional trademark information and
notices.