Ask the database for only the rows that satisfy the task

The dispatch analyst needs open orders created since a chosen date. Filtering at the database keeps irrelevant rows out of the result and makes the rule visible in one place.

Add predicates incrementally

Start with one comparison:

WHERE status = 'OPEN'

Add a date condition with AND:

WHERE status = 'OPEN'
  AND createdat >= @since_date

For alternatives, use parentheses to make precedence clear:

WHERE status = 'OPEN'
  AND ( carriercode = @carrier_a OR carriercode = @carrier_b )

Do not assume capitalization or text semantics without checking the field’s type and collation. Use a typed host variable for user-provided values rather than concatenating values into a SQL string.

Ranges and optional filters

ABAP range tables can express sets of include/exclude conditions in supported ABAP SQL contexts. A plain WHERE is often easiest for a small fixed rule; use ranges when the user/business logic genuinely supplies a set. Optional criteria should be expressed deliberately rather than by building unsafe dynamic SQL.

Practice

Add the status predicate, date predicate, and table target, then count rows in result. This checker verifies the statement patterns only.

Sources

• SAP Samples, ABAP SQL
• SAP Help Portal, ABAP SQL

Version note: SQL condition capabilities and expression support vary by release and source type.

SELECT FROM zi_dispatch_order
  FIELDS dispatchorder, status, createdat
  WHERE status = 'OPEN'
    AND createdat >= @since_date
  INTO TABLE @DATA(orders).
DATA(result) = lines( orders ).

WRITE result.

out->write( result ).