sap-abap

Use table expressions with OPTIONAL or DEFAULT, such as VALUE #( itab[ key = value ] OPTIONAL ), or check first with line_exists( itab[ key = value ] ). This avoids the CX_SY_ITAB_LINE_NOT_FOUND exception raised by direct access to a missing line.

ABAP Cloud restricts the language to released SAP APIs and prohibits statements like WRITE, MOVE...TO, DESCRIBE TABLE, and sy-datum. Use the XCO library for date and time, if_oo_adt_classrun for output, and RAP for transactional scenarios.

REDUCE and FILTER require ABAP 7.40 SP08 or higher. Most other constructor operators like VALUE, NEW, CONV, COND, and SWITCH are available since 7.40 SP02, while FINAL inline declarations require 7.50.

Implement get_global_authorizations for operation-level checks and get_instance_authorizations for instance-level checks in the behavior handler. Use AUTHORITY-CHECK with the relevant object and ACTVT codes, and return if_abap_behv=>auth-allowed or auth-unauthorized.

No, WITH statements (CTEs) require ABAP 7.51 or higher. On 7.40 systems, use subqueries or select into temporary internal tables and combine results in ABAP instead.

Common causes are using sy-datum or sy-uzeit instead of cl_abap_context_info or XCO methods, WRITE statements instead of out->write, and unreleased APIs. Run ATC with the ABAP_CLOUD_READINESS variant in ADT to list all findings.