Workik.

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

The Simplification List: What Changed in S/4HANA

Explore the SAP Simplification Database and run transaction SYCM to evaluate critical functional changes affecting legacy custom ABAP programs.

When you prepare to migrate custom code to SAP S/4HANA (SAP Business Suite 4 SAP HANA), you must first understand what SAP changed in the core software. SAP compiled thousands of functional and architectural changes into a collection called the Simplification List. For an ABAP (Advanced Business Application Programming) developer, this document is not just release notes. It is the inventory of every table, transaction, function module, and business process that behaves differently or no longer exists.

Previous lesson: S/4HANA Conversion Approaches and Your Custom Code | Next lesson: Finding Unused Custom Code with SCMON and SUSG


What Is the Simplification List

The Simplification List describes the differences between SAP ECC (ERP Central Component) 6.0 and SAP S/4HANA. SAP publishes a dedicated Simplification List for each S/4HANA release. Each entry in the list represents a Simplification Item.

A Simplification Item covers a specific functional or architectural change. For example, it explains changes in data structures, replaced transactions, or consolidated functional areas. Each item explains the business impact, the technical impact on custom developments, and the steps required to transition.

Think of the Simplification List like an urban redevelopment plan. When a city replaces a roundabout with an overpass, it publishes the exact detours and structural modifications drivers and bus routes must follow. Custom programs are your routes, and simplification items show which roads no longer exist.

Each simplification item points directly to business processes and ABAP repository objects. When Harbor Supply Co. evaluates its 4,000 custom repository objects, the development team uses these items to identify which custom reports and interfaces will break during conversion.

Common Mistake: Do not treat the Simplification List as an optional manual for functional analysts. Technical consultants must read the technical impact sections to know whether their custom tables, views, and database access logic need rewrites.


The Simplification Database and ATC

Reading a PDF document containing hundreds of pages is impractical when scoping thousands of custom objects. SAP solved this by converting the technical metadata of the Simplification List into a structured repository called the Simplification Database.

The Simplification Database contains machine readable records of all modified, replaced, and deleted SAP objects. This database is downloaded into your central check system as a zip archive and imported through transaction SYCM or the ABAP Test Cockpit (ATC). ATC is SAP's standard tool for quality checks and static code analysis.

When you run ATC checks against your custom code, the check engine compares your ABAP statements against this database. The check engine flags any custom statement that references an obsolete database table, calls a deleted function module, or uses a modified data element.

The flow works in three stages:

  1. The Simplification List documents each change for people to read.
  2. The Simplification Database holds the same changes as structured data inside your check system.
  3. ATC and transaction SYCM scan your custom ABAP code against that database and report every conflict.

Pro Tip: Always verify that your central check system has imported the latest content for your exact target S/4HANA release before you run code inspections.


Analyzing Impact with Transaction SYCM

Transaction SYCM gives you an overview of how your custom code relates to the Simplification Database. While ATC provides an itemized list of code errors, transaction SYCM allows you to explore simplification items and search for custom object references directly.

In transaction SYCM, you can:

  • Display all simplification items imported into your system.
  • Filter items by application component, such as Sales and Distribution (SD) or Materials Management (MM).
  • Display the custom objects in your system that reference simplified SAP objects.
  • Inspect the specific SAP objects that trigger each finding.

At Harbor Supply Co., running transaction SYCM shows that the custom inventory report ZMM_STOCK_MOVES references classic inventory tables, while ZSD_ORDER_STATUS references old status tables. Transaction SYCM groups these occurrences by simplification item, giving project leads a clear view of which functional areas require the most remediation effort.

Quick Challenge: Open transaction SYCM in your check system and filter by the MM-IM (Inventory Management) component to review all simplified objects affecting goods movements.


Understanding Finding Categories

When the Simplification Database identifies custom code conflicts, it classifies them into distinct finding categories. Understanding these categories helps you prioritize fixes.

The two most common technical categories are:

  1. Functionality not available: The referenced SAP transaction, program, or function module has been removed completely without an in-place technical surrogate. Your code will trigger a syntax error or a runtime dump if called.

  2. Syntactically incompatible change of existing functionality: The object still exists, but its signature, interface, or underlying structure changed in an incompatible way. Examples include data type length modifications or changed parameters in standard function modules.

Finding CategoryMeaningTypical Impact on Code
Functionality not availableSAP object or transaction was removed entirelySyntax error or runtime dump (CALL_FUNCTION_NOT_FOUND)
Syntactically incompatible changeObject exists but signature or structure changedSyntax error during compilation

In Harbor Supply Co.'s codebase, calls to old transaction codes fall under "Functionality not available", whereas references to extended fields fall under "Syntactically incompatible change".


Anatomy of a Simplification Item: A Practical Example

To resolve an ATC finding, you must know how to interpret a simplification item. Every item outlines the reason for change, the replacement architecture, and the required actions.

Consider the simplification of classic inventory transaction MB11. In SAP ECC, custom programs often call transaction MB11 via CALL TRANSACTION or submit background jobs to record goods movements.

In S/4HANA, transaction MB11 is not available. The single transaction MIGO is the unified replacement for goods movements.

If Harbor Supply Co. has a legacy wrapper program that executes MB11, the code fails in S/4HANA:

abap
Copy

The simplification item instructs developers to stop calling MB11. For automated or programmatic goods movements, the recommended solution is to use standard application programming interfaces, such as standard BAPIs (Business Application Programming Interfaces), or modern post routines instead of calling obsolete dynpro screens:

abap
Copy

Checking the simplification item provides the direct business context and technical path required to replace obsolete transactions with clean API calls.


Try It Yourself

Review this custom code snippet taken from Harbor Supply Co.'s shipping package. The program checks status and calls an obsolete transaction:

abap
Copy

Answer the following questions to verify your understanding:

  1. Which two Simplification List issues are present in this short code fragment?
  2. Which category does the MB11 call fall under in the Simplification Database?
  3. Where can you find the exact replacement guidance for both issues?

Suggested answers:

  1. First, the code selects directly from table VBUK, which is no longer used for sales status in S/4HANA. Second, it calls transaction MB11, which is not available in S/4HANA.
  2. The MB11 call falls under the category "Functionality not available".
  3. You can review the corresponding items in transaction SYCM or search the Simplification Database within your central ATC system.

In the next lesson, Finding Unused Custom Code with SCMON and SUSG, you will learn how to monitor production ABAP execution and eliminate obsolete programs before conversion.

Was this lesson helpful?