SAP LOGEXP BOUND

Get Example source ABAP code based on a different SAP table
  


ARTICLE
• IS BOUND ABAP_RELAT_EXPR
• IS NOT BOUND ABAP_RELAT_EXPR

rel_exp - IS BOUND

Syntax
ABAP_KEY ... ref IS [NOT] BOUND ...

Effect
This predicate expression checks whether a reference variable contains a valid reference. A reference variable must be specified for ref. This is a functional operand position.
A data reference is valid if it can be dereferenced.
An object reference is valid if it points to an object.
When using addition NOT, the expression is true if the reference variable does not contain a valid reference.

Note
A non-initial reference variable that contains a heap reference is generally always valid (since it keeps an object alive). Only heap references that point to rows from internal tables can become invalid when rows are deleted. A data reference variable that contains a stack reference, on the other hand, can become invalid even if the reference data object is removed from the stack.

Example
The logical expression in the IF statement is false. The data reference dref contains a reference to a deleted table row. DATA: dref TYPE REF TO data,
itab TYPE TABLE OF ...

FIELD-SYMBOLS <(><<)>fs> TYPE ANY.

dref = REF #( itab[ ... ] ).

...

CLEAR itab.

...

IF dref IS BOUND.
ASSIGN dref->* TO <(><<)>fs>.
ENDIF.