Skip to Content
Product Information

Conversion to S/4HANA 1809FPS0 – t5 – Custom Code Migration

This blog is for the detailed steps for Custom Code Migration (CCM) for step t5 of conversion to S/4HANA 1809FPS0/FPS1 is an optional step. The steps are shown for Custom Code Analysis to estimate efforts required for the Custom Code Adaptation. As part of custom code migration there is also a step to be done after the system conversion in SPDD/SPAU.

Download the Custom Code Migration User Guide 1809 FPS0 / Custom Code Migration User Guide 1809 FPS1 for reference

Please find other blogs as follows:

S/4HANA  SQUARE  ONE

NEW INSTALLATION        PART 1 – MP   PART 2 –  Installation
PART 3 –  BP Activation
S/4HANA 1809 fps1  fps0 fps1  fps0 fps1  fps0
S/4HANA 1709 fps2  fps1  fps0 fps2  fps1  fps0 fps2  fps1  fps0 -US
fps2  fps1  fps0 -DE
S/4HANA 1610 fps2  fps0 fps2  fps0 fps2  fps1  fps0 -US
fps2  fps1  fps0 -DE
S/4HANA 1511 fps2  fps1
S/4HANA UPGRADE   t2 – MP t3 – SIC
t4 – CCM t5 – SUM
S/4HANA 1809 link link link link
SYSTEM CONVERSION t2 –  RC t3 – MP t4 – SIC
t5 – CCM t6 – SUM 
S/4HANA 1809 link link link link EHP7/hdb
EHP6/db6
EHP5/ora
EHP6/mss
S/4HANA 1610 FPS0 link link link
S/4HANA ON-PREM APPLIANCE INSTALL USING MEDIA ACTIVATE FROM CAL
S/4HANA 1709 FPS1 link link
S/4HANA CLOUD      CPM  MASTER  CONTENT   EMAIL
OUTPUT MANAGEMENT link  link  link link

STEP 1: APPLY NOTES IN CHECKED SYSTEM

The checked system can have either of Software components – SAP_BASIS 7.00, 7.01, 7.02, 7.31, 7.40, 7.50, 7.51 or 7.52.

TIP: First 2 notes below are big and if you get “Note Incomplete” or “Error occurred while downloading SAP Note xxxxx” please try downloading again individually and if it still doesn’t work, download from launchpad /upload in snote manually. To give you an idea of size – 2485231 is 4MB , 2270689 is 11MB, 2190065 is 1.6MB and 2196792 is 1MB

APPLY FIRST NOTE  2485231 – Remote ATC Checks of Modifications and Enhancements

Create Function Group SCA_ABAP_CHECK_MODINFO

Get Access Key

Checkmark Confirmed and continue – 2 times

Check and set as below:

Create Function Group SCA_REMOTE_DATA_ACCESS

Checkmark on Copy Changes for first 2 items

Click on Activate Anyway

APPLY SECOND NOTE 2270689 – RFC Extractor for performing static checks

This note is HUGE and you may face errors while downloading. Try downloading the note from browser and then upload in SNOTE.

Create Function Group SABP_COMP_PROCS_E

Activate the function group SABP_COMP_PROCS_E.

Checkmark on Copy Changes for first 2 items

Click on Activate Anyway –  6 times

Start Report RS_ABAP_INIT_ANALYSIS and Confirm step.

APPLY THIRD NOTE 2190065 – ATC/CI: Remote Code Analysis – Object Provider Stub

This note was already implemented by other notes.

APPLY FOURTH NOTE 2196792 – RFC-Stub for CVA/SLIN-Remote

Under package SLIN, create subpackage S_CVA_BSP

Under package SLIN, create Function Group SLIN_REMOTE_RESOURCES

Activate Function Group SLIN_REMOTE_RESOURCES

Create Function Group CVA_BSP_REMOTE_RESOURCES

Activate Function Group CVA_BSP_REMOTE_RESOURCES

The object tree should look like this:

Checkmark on Copy Changes for first 3 items

Create a user in Checked system with below authorizations. like CCM_CHECKED.

This completes the steps for the Checked system.

STEP 2: APPLY NOTES IN CENTRAL CHECK SYSTEM

The Central Check system should have Software component SAP_BASIS 7.52 or higher. In case you already have a S/4HANA sandbox, you could use it. Also you can use a S/4HANA Fully activated Appliance on-prem or in CAL, it just requires Netweaver 7.52.

We will use CAL solution which is SAP NetWeaver AS ABAP 7.52 SP01 on SAP ASE 16.0 from below:

Below config is fine to reduce cost.

Activate Instance and login as user DDIC, copy user DDIC to create user S4HCONV so notes can be applied. Ensure RFC SAPOSS is configured and working.

The 2 notes are not to be applied in Checking system using SNOTE but contain information related to notes which are to be applied.

APPLY FIRST NOTE 2436688 – Recommended SAP Notes for using SAP S/4HANA custom code checks in ATC

Since this is a Netweaver 7.52 SP1 system we have to apply the notes, if your system is different Netweaver/SP level, the notes to be applied may be completely different.

2578127 – Pseudo comments for S/4HANA custom code checks
2577440 – Improvements in S/4HANA custom code check “S/4HANA: Search for S/4 related syntax errors”
2569135 – S/4HANA custom code check “S/4HANA: Search for S/4 related syntax errors” reports syntax warnings
2573527 – S/4HANA custom code check for buffered DB table access

All above notes do not have manual steps.

APPLY SECOND NOTE 2364916 – Recommended SAP Notes for using ATC to perform remote analysis

Since this is a Netweaver 7.52 SP1 system we have to apply the notes, if your system is different Netweaver/SP level, the notes to be applied may be completely different.

2423013 – Code-Inspector-Test Checksum-Infrastructure
2527903 – Remote analysis (for central check system)
2587593 – ATC: Checkability of Modifications and Enhancements in Remote Checks – Developer Scenario
2614006 – ATC remote check fails in developer scenario

APPLY THIRD NOTE 2659194 – Check variant for SAP S/4HANA 1809 custom code checks

STEP 3: IMPORT THE SIMPLIFICATION DATABASE

FIRST – download the CCMSIDB from Service Marketplace. Open Software Download Center and search for CCMSIDB

SECOND – Import the Simplification Database into Central Checking System

enter tCode SYCM

After clicking Open, there is a message Loading ZIP C:\CCMSDB00P_7-8000101. The  there is a message – Downloading simplification notes ….

You should get message below:

THIRD – you can now display the content of the simplification database. Click the Overview button.

The simplification items are grouped by Simplification Category.

FOURTH – If you click on Show Items for Selection, you can view the Simplification Database content with displayed list by SAP Object Type, Simplification Category and relevant SAP Note Number.

FIFTH – Set the role of the Central Check System

Enter tCode ATC => System Role => Change System Role

SIXTH – Create System Groups tCode ATC => ATC Administration => Setup => Object

Select (1) System Groups, (2) Change, (3) New Entries, (4) enter System Group details as below:

SEVENTH – Enter tCode SM59, create RFC destination, Connection Type 3  in the Central Checking system to point to the Checked system.

EIGHTH – Create RFC Object Providers tCode ATC => ATC Administration => Setup => Object Providers

STEP 4: RUN ATC CHECKS FROM CENTRAL CHECKING SYSTEM

FIRST – Configure remote ATC runs series tCode ATC => Runs => Schedule Runs , Create Series Name CONV1

SECOND – Select Check Variant S4HANA_READINESS_1809 and Save the configuration.

TIP: After System Conversion, on your S/4HANA 1809 system you can run local analysis, it is recommended to use variant S4HANA_READINESS because this performs also the syntax check related to simplified objects.

STEP 5: SCHEDULE A REMOTE ATC RUN SERIES

Select the run series and click Schedule button on toolbar.

STEP 6: MONITOR ATC RUN SERIES

In the navigation pane in transaction ATC, expand the nodes ATC Administration Runs and double-click Monitor and Control RunsLeave the run series field empty and execute (F8)


The ATC Run Monitor view is displayed. The view shows the status of check runs as running, finished, or failed.

STEP 7: ANALYZE ATC RUN RESULTS

tCode ATC => ATC Administration => Runs => Manage Results

  1. In the navigation pane in transaction ATC, expand the nodes ATC Administration Runs and double-click Manage Results.
  2. Leave the run series field empty and choose Execute (F8).
  3. In the ATC Manage Results view is displayed. The view shows a list of ATC run results from your requested period of time. A list of all ATC findings is displayed in transaction SE80.
  4. Choose Statistics View
  5. In the ATC Manage Results view, select a run series and choose Display to inspect the results.
    Choose Statistic to group the ATC findings (for example, by SAP Note Number).
    The ATC findings are grouped by the selected statistics
  6. Double-click a statistics group to display the list of ATC findings assigned to the selected statistics.
  7. Double-click an ATC finding to open detailed information. Here you can find the SAP Note number referring to a dedicated SAP Note and the referenced object.
  8. Click the object name to navigate to the source code to see where the incompatible code occurs

LANDSCAPE CONSIDERATIONS:

In the preparation phase the ABAP Test Cockpit is used to analyse custom code impact of HANA database and S/4HANA. After that in the Realization phase, the SUM tool is used to conduct system conversion and combined database migration to HANA.   Here you need to adapt your ABAP custom code to the new S/4HANA software and optimize performance of SAP HANA databaase by performing application-specific follow-up activities and working with tools like transaction
SPAU and SPDD to adapt the modifications and enhancements.

The SPAU and SPDD transports created in development system are later used in subsequent systems in the landscape QAS and PROD.

ADDITIONAL REFERENCE:

BLOGS
ABAP Call Monitor (SCMON) – Analyze usage of your code
What you can do today to prepare your custom code for SAP S/4HANA
SAP S/4HANA System Conversion – Custom code adaptation process
Remote Code Analysis in ATC – Technical Setup step by step

GUIDES:
Custom Code Migration Guide for SAP S/4HANA 1809         <= pdf

VIDEO:
Custom Code Adaptation for SAP S/4HANA

Thank you. Hope you enjoyed the blog !

Mahesh Sardesai
Product Expert – S/4HANA

 

 

 

Be the first to leave a comment
You must be Logged on to comment or reply to a post.