Ansicht
Dokumentation
ABAPCHECK_PROCESSING_BLOCKS - CHECK PROCESSING BLOCKS
ABAP Short Reference rdisp/max_wprun_time - Maximum work process run timeThis documentation is copyright by SAP AG.
CHECK, processing_block
CHECK log_exp.
Effect
If the statement CHECK is listed outside a loop and log_exp is false, it terminates the current processing block. Any logical expression can be specified for log_exp.
After the processing block is exited, the runtime framework behaves in the same way as when the processing block is exited in the regular way, with the exception of the event block LOAD-OF-PROGRAM and the reporting event block GET. In particular, the output parameters of procedures are passed on to the bound actual parameters.
- The event block LOAD-OF-PROGRAM cannot be exited using CHECK.
- After the reporting event block GET is terminated using CHECK, any subordinate nodes in the hierarchy structure of the linked logical database are no longer processed. The logical database reads the next line of the current node or next higher node, if it has reached the end of the hierarchy level.
Only use RETURN to exit procedures
Notes
- In a procedure (a method, function module, or subroutine), CHECK log_exp works outside a loop in the same way as:
-
IF NOT log_exp.
RETURN.
ENDIF.
- A further variant of the statement CHECK for exiting processing blocks is CHECK
SELECT-OPTIONS, which can only be used in GET event blocks for logical databases.
Example
This example shows a case where CHECK can be used outside a loop. At the start of a procedure, a prerequisite for executing the procedure is checked and the procedure exited if the check is not successful. In this case, the procedure must not be executed in the background.
General Data in Customer Master SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 3099 Date: 20240423 Time: 174726 sap01-206 ( 44 ms )
