MEDIUM Effort: XL — Extra Large (2+ weeks) UI/UX

How to remediate: SAP GUI-dependent UI

Programs using CALL SCREEN, CALL DIALOG, classic dynpros, or SAP List Viewer (ALV) classic.

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

SAP strategy is Fiori. SAP GUI programs work in S/4HANA but are not strategic for new development.

Before and after: ABAP code example

Before (ECC) 
* ECC: classic dynpro screen
MODULE status_0100 OUTPUT.
  SET PF-STATUS 'MAIN'.
  SET TITLEBAR  'T01'.
ENDMODULE.
MODULE user_command_0100 INPUT.
  CASE sy-ucomm.
    WHEN 'SAVE'. PERFORM save_data.
    WHEN 'BACK'. LEAVE TO SCREEN 0.
  ENDCASE.
ENDMODULE.
After (S/4HANA) 
* S/4HANA strategic direction: RAP + Fiori Elements
* 1. Define CDS entity with @UI annotations
* 2. Generate RAP Business Object (managed scenario)
* 3. Expose via OData V4 service binding
* 4. Fiori Elements generates the UI — no ABAP screen code needed
@UI.headerInfo: { typeName: 'Sales Order' }
define root view entity ZI_SalesOrder
  as select from vbak { ... }

Effort estimate and common pitfalls

Effort estimate

XL — Extra Large (2+ weeks)

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

  • ! Architectural dependencies that require multiple teams
  • ! Data migration requirements alongside code changes
  • ! Extended regression and integration test cycles
  • ! Potential need for parallel run before cutover

Related rules to check

LOW S

Reports called via SE38/SA38 pattern

Z/Y reports without proper transaction codes, called directly via SE38/SA38.
HIGH L

ABAP Cloud restricted object access

Access to SAP internal objects without C1 release status. These are blocked in ABAP Cloud.
MEDIUM S

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 SAP GUI-dependent UI — 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.