MEDIUM Effort: M — Medium (days) Deprecated APIs

How to remediate: Obsolete function modules

Usage of function modules flagged as obsolete in SAP S/4HANA simplification list.

Is this issue in your codebase?

A1 scans all 30 rules across your custom ABAP — results in minutes.

Scan your codebase free →

What changes in S/4HANA

Obsolete FMs may not exist or behave differently in S/4HANA. Released API replacements exist.

Before and after: ABAP code example

Before (ECC)
* ECC: FM flagged as obsolete in simplification list
CALL FUNCTION 'HR_GET_LEAVE_DATA'
  EXPORTING
    pernr   = lv_pernr
  IMPORTING
    result  = lt_leave.
After (S/4HANA)
* S/4HANA: check released replacement in API hub
* Use the ABAP Cloud API or released RAP BO
* Verify replacement name in SAP Business Accelerator Hub
* Example pattern with released class:
DATA(lo_api) = NEW cl_hcm_leave_api( ).
lo_api->get_leave_data(
  EXPORTING iv_pernr = lv_pernr
  IMPORTING et_leave = DATA(lt_leave) ).

Effort estimate and common pitfalls

Effort estimate

M — Medium (days)

Estimate is per affected object. Total effort scales with the number of occurrences in your codebase. Use the A1 scan to get an object-level count before estimating the full project.

Common pitfalls

  • ! Missing related objects that contain the same pattern
  • ! Not testing edge cases after replacing the API
  • ! Skipping regression tests for dependent programs

Related rules to check

Find every instance of this issue in your codebase

The A1 scanner checks all 30 compatibility rules — including Obsolete function modules — across your custom ABAP objects and produces a prioritised remediation backlog.

Scan your codebase for this issue free →

SAP, S/4HANA and ABAP are trademarks of SAP SE. s4ready.ai is an independent solution and is not affiliated with, endorsed by, or sponsored by SAP SE.