How to remediate: Unchecked SY-SUBRC
Database operations or function module calls without checking SY-SUBRC return code.
Is this issue in your codebase?
A1 scans all 30 rules across your custom ABAP — results in minutes.
What changes in S/4HANA
Silent failures cause data inconsistency. S/4HANA introduces new error conditions that ECC never raised.
Before and after: ABAP code example
* ECC: no SY-SUBRC check — silent failure
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING input = lv_raw
IMPORTING output = lv_formatted.
" continue processing with potentially empty lv_formatted * S/4HANA: always check return code
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING input = lv_raw
IMPORTING output = lv_formatted
EXCEPTIONS others = 4.
IF sy-subrc <> 0.
RAISE EXCEPTION TYPE cx_sy_conversion_error
MESSAGE 'Alpha conversion failed for input'(001).
ENDIF. Effort estimate and common pitfalls
Effort estimate
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
- ! Forgetting to update all occurrences in the same program
- ! Not running ATC after the change to confirm the finding is resolved
Related rules to check
Missing AUTHORITY-CHECK
Programs reading/writing sensitive data without AUTHORITY-CHECK statements.
Missing FOR ALL ENTRIES guard
FOR ALL ENTRIES IN without an initial-table check returns the full table when the driver table is empty.
Obsolete ABAP statements
Use of obsolete ABAP syntax: MOVE, COMPUTE, WRITE TO, SORT BY ASCENDING/DESCENDING without field list.
Find every instance of this issue in your codebase
The A1 scanner checks all 30 compatibility rules — including Unchecked SY-SUBRC — 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.