STOP

Short Reference

Syntax

STOP.

Effect

The statement STOP is only to be used in executable programs and in the following event blocks:

• AT SELECTION-SCREEN (without additions)
  
• START-OF-SELECTION
  
• GET
  

You leave these event blocks via STOP, and the runtime environment triggers the event END-OF-SELECTION.

Note

The statement STOP is forbidden in methods and, since Release 6.10, leads to an uncatchable exception during the processing of screens called with CALL SCREEN and in programs not called with SUBMIT.

Example

Ending the event blocks GET sbook after max postings have been issued, and branching to END-OF-SELECTION.

NODES: sflight, sbook.
DATA: bookings TYPE i,
      max TYPE i VALUE 100.
GET sflight.
  WRITE: / sflight-carrid, sflight-connid, sflight-fldate.
GET sbook.
  bookings = bookings + 1.
  WRITE: / sbook-bookid, sbook-customid.
  IF bookings = max.
    STOP.
  ENDIF.
END-OF-SELECTION.
  ULINE.
  WRITE: / 'First', bookings, 'bookings'.

Exceptions

Non-Catchable Exceptions

• Cause: The statement STOP was run outside the processing of a type 1 program.
  Runtime Error: STOP_NO_REPORT
  
• Cause: The statement STOP was run during the processing of a screen and therefore outside the allowable events.
  Runtime Error: STOP_WITHIN_CALLED_DYNPRO