What is the "Unassigned field symbol access" issue in S/4HANA migration?

ASSIGN or FIELD-SYMBOL without checking IS ASSIGNED causes GETWA_NOT_ASSIGNED dumps. Runtime dumps in production. Common cause of ST22 short dumps after S/4HANA migration.

How much effort does it take to fix "Unassigned field symbol access"?

Remediation effort is rated S — Small (hours). Severity: HIGH.

Which tool checks for Unassigned field symbol access automatically?

The s4ready.ai A1 Readiness Scanner checks for Unassigned field symbol access (and 29 other rules) automatically across your custom ABAP codebase. Results include object-level findings with severity and effort estimates.

HIGH Effort: S — Small (hours) Error Handling

How to remediate: Unassigned field symbol access

ASSIGN or FIELD-SYMBOL without checking IS ASSIGNED causes GETWA_NOT_ASSIGNED dumps.

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

Runtime dumps in production. Common cause of ST22 short dumps after S/4HANA migration.

Before and after: ABAP code example

Before (ECC)

* ECC: no IS ASSIGNED check — GETWA_NOT_ASSIGNED dump
FIELD-SYMBOLS: <ls_item> TYPE ty_item.
READ TABLE lt_items ASSIGNING <ls_item>
  WITH KEY matnr = lv_matnr.
lv_price = <ls_item>-netpr.  " dump if not found

After (S/4HANA)

* S/4HANA: guard every field symbol before access
FIELD-SYMBOLS: <ls_item> TYPE ty_item.
READ TABLE lt_items ASSIGNING <ls_item>
  WITH KEY matnr = lv_matnr.
IF <ls_item> IS ASSIGNED.
  lv_price = <ls_item>-netpr.
ELSE.
  lv_price = 0.
ENDIF.

Effort estimate and common pitfalls

Effort estimate

S — Small (hours)

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

MEDIUM S

Unchecked SY-SUBRC

Database operations or function module calls without checking SY-SUBRC return code.

MEDIUM S

Obsolete ABAP statements

Use of obsolete ABAP syntax: MOVE, COMPUTE, WRITE TO, SORT BY ASCENDING/DESCENDING without field list.

HIGH XL

Dynamic ABAP (GENERATE SUBROUTINE POOL)

Runtime code generation via GENERATE SUBROUTINE POOL or EXECUTE PROGRAM is restricted in ABAP Cloud.

Find every instance of this issue in your codebase

The A1 scanner checks all 30 compatibility rules — including Unassigned field symbol access — across your custom ABAP objects and produces a prioritised remediation backlog.

Scan your codebase for this issue free →

← All remediation rules Resources →

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.