Workik.

SAP S/4HANA Custom Code Migration: An ABAP Developer's Guide

Running S/4HANA Readiness Checks with ABAP Test Cockpit

Execute ABAP Test Cockpit checks using the S4HANA_READINESS variant and navigate the Custom Code Migration app to prioritize migration findings.

You have collected usage data and scoped out obsolete programs. Now you face the active codebase that must run on SAP S/4HANA. To find syntax breaks, removed tables, and obsolete function modules before cutover weekend, you use the ABAP Test Cockpit (ATC).

Previous lesson: Finding Unused Custom Code with SCMON and SUSG | Next lesson: Fixing Common S/4HANA Custom Code Findings


Remote ATC Architecture and Setup

Your SAP ECC 6.0 system lacks the modern static analysis checks and the Simplification Database needed to detect S/4HANA incompatibilities. Running a readiness check directly inside an old ECC system will not work.

Instead, SAP uses a remote ATC architecture. A central check system connects to your ECC system through Remote Function Call (RFC) destinations.

In this setup:

  1. The central check system (SAP_BASIS 7.52 or higher, or S/4HANA 1809 or higher) holds the Simplification Database and the S4HANA_READINESS check variant.
  2. It connects to your ECC system through an RFC destination.
  3. It reads the custom code from ECC, checks it, and stores the findings centrally without changing the ECC system.

The central check system can be a dedicated NetWeaver AS ABAP 7.52 system, an existing sandbox on SAP S/4HANA 1809 or higher, or the SAP Business Technology Platform (SAP BTP) ABAP environment.

Pro Tip: Set up a dedicated RFC user in the checked ECC system with authorization for standard ATC extractor functions. Never use a dialog user with broad admin rights for scheduled runs.


Configuring the S4HANA_READINESS Check Variant

The ABAP Test Cockpit relies on check variants to determine what rules to apply. While the standard variant DEFAULT covers general code quality, S/4HANA migrations require the dedicated S4HANA_READINESS check variant.

This variant combines Code Inspector checks specifically built around data model adjustments:

  • Simplification Database Checks: Detects calls to obsolete transactions, deleted function modules, and replaced tables like VBUK or KONV.
  • Field Length Extensions: Flags hardcoded references to material numbers (MATNR) that assume 18 characters instead of 40 characters.
  • Database Operations: Identifies native SQL, database hints, and unconstrained queries on cluster tables.

To inspect or maintain the variant in the central system, open transaction ATC or transaction SCI. The variant comes pre-configured by SAP, but you must make sure your central system has imported the latest Simplification Database content from SAP.

Common Mistake: Running the check variant S4HANA_READINESS before importing the Simplification Database zip file into transaction SYCM. If the content is missing or outdated, the results are incomplete, giving you false confidence.


Running Readiness Checks in ABAP Development Tools

Developers do not need to log into the central check system to see their errors. You can run ATC directly inside ABAP Development Tools (ADT) in Eclipse.

Right-click your custom package or program in the Project Explorer, such as ZSD_ORDER_STATUS. Navigate to Run As, select ABAP Test Cockpit With..., and choose the S4HANA_READINESS check variant configured against your central system.

abap
Copy

When the check completes, results display in the ATC Problems view at the bottom of Eclipse.

Double-clicking a finding navigates directly to the offending line of code. The view groups issues by priority, object, and package. It also displays a direct link to the relevant SAP Note explaining the architectural change and remediation path.

Quick Challenge: Open an active custom program in ADT. Run ATC using your local variant, then re-run with S4HANA_READINESS. Compare the difference in flagged statements.


Scoping and Prioritising with the Custom Code Migration App

When Harbor Supply Co. runs ATC across all 4,000 custom objects, the result is thousands of findings. Sorting through that volume in transaction ATC or the ADT list view creates friction.

The Custom Code Migration app is a SAP Fiori application built on top of remote ATC. It is available on SAP BTP or on an on-premise S/4HANA system (1809 or higher) connected to your ECC landscape.

The app turns raw ATC findings into a dashboard where you can:

  • See how many custom objects are in scope and how many are out of scope because they are unused.
  • Group findings by priority, from blockers to advisory warnings.
  • Filter findings by SAP Note, application component and quick fix availability.
  • Track progress as findings are fixed over time.

You can upload aggregated usage data from transaction SUSG into the app. The app automatically marks unused code as out of scope.

Instead of remediating 4,000 objects, your team focuses on the active 1,600 objects. You can slice findings by SAP Note, application component, or whether an automated quick fix exists.

Try This: In the Custom Code Migration app, filter the findings to those with a quick fix available, then group them by SAP Note. This gives your development team an immediate batch of mechanical fixes that can be resolved quickly.


Triage Strategy: Priority 1, 2, and 3 Findings

Not every ATC finding requires immediate remediation before technical conversion. Understanding finding priorities prevents project delays.

Priority 1: Technical Blockers

These findings represent syntax errors or missing repository objects that prevent code from compiling on SAP S/4HANA.

Examples include programs using statements or types that SAP completely removed from the dictionary. If a Priority 1 issue is ignored, the affected program cannot run after the conversion and fails as soon as someone uses it. Resolve these before or during cutover.

Priority 2: Functional Incompatibilities

The code compiles, but it will fail at runtime or produce incorrect business data.

For Harbor Supply Co., ZSD_PRICE_EXPORT reading from KONV or ZSD_ORDER_STATUS reading from VBUK falls here. The queries might return empty sets or dump because the underlying data structures shifted to tables like PRCD_ELEMENTS and VBAK. These must be remediated and thoroughly regression-tested.

Priority 3: Performance and Modernization Warnings

These are non-breaking operational issues. Examples include database hints written for another database platform, or obsolete statements that still execute. Priority 3 items can often be scheduled for cleanup after the core technical conversion is complete.


Try It Yourself

Review this finding report extracted from an ATC run on Harbor Supply Co.'s custom order management package:

Object Name: ZSD_ORDER_STATUS
Check: S/4HANA: Search for usages of simplified objects
Finding: Table VBUK is obsolete in SAP S/4HANA.
Severity: Priority 2
Quick Fix: Available

Object Name: ZMM_STOCK_MOVES
Check: S/4HANA: Field length extensions
Finding: Parameter declared with CHAR18 instead of MATNR. See SAP Note 2215424.
Severity: Priority 2
Quick Fix: Available

Object Name: ZSD_PRICE_EXPORT
Check: S/4HANA: Search for database operations
Finding: Database hint for another database platform is ignored on SAP HANA.
Severity: Priority 3
Quick Fix: Not Available
  1. Identify which findings represent automated adjustments versus manual redesign.
  2. Determine which finding must be remediated first to avoid inaccurate data processing in reporting interfaces.
  3. Formulate the replacement strategy for ZSD_ORDER_STATUS using modern open SQL on the document header table.

In the next lesson, Fixing Common S/4HANA Custom Code Findings, you will learn how to apply automated quick fixes in ADT and resolve manual readiness findings across your codebase.

Was this lesson helpful?