What does it do? These additions define which columns of the database table or the view dbtab> are declared as LOB handle components> when deriving a LOB handle structure> using the statement TYPES>>.
COLUMNS blob1 blob2 ... clob1 clob2 ...> specifies individual BLOBs> blob1>, blob2>, ... or CLOBs> clob1>, clob2>, ... These must exist in dbtab>.
ALL OTHER BLOB$|CLOB COLUMNS> This specifies all BLOBs> or CLOBs> in dbtab> that are not covered when individual columns are specified. In the statement TYPES>>, at least one individual column blob> or clob> must be specified using COLUMNS ...>
ALL BLOB$|CLOB COLUMNS> specifies all BLOBs> or CLOBs> of dbtab>.
ALL OTHER COLUMNS> This specifies all LOBs> in dbtab> that are not covered when individual columns are specified. In the statement TYPES>>, at least one individual column must be specified using COLUMNS ...>
ALL COLUMNS> This specifies all LOBs> in dbtab>. No other columns can be specified in the statement TYPES>> after the column specification ALL OTHER ...> The combination options of the column specifications with each other below and with the types specified using lob_handle_type>> are explained in the statement TYPES>>.
Latest notes: Columns of the data type GEOM_EWKB>> are not supported as BLOBs>. NON_V5_HINTS ABAP_HINT_END
ABAP_EXAMPLE_VX5 Demonstration of various column specifications in the definition of LOB-Handle components. ABEXA 00728 ABAP_EXAMPLE_END