Kontakt

Ansicht
Dokumentation

ABAPTYPES_LOB_HANDLE - TYPES LOB HANDLE

ABAPTYPES_LOB_HANDLE - TYPES LOB HANDLE

CPI1466 during Backup   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

TYPES, LOB HANDLE

Short Reference



TYPES dtype TYPE dbtab$|view
                 lob_handle_type FOR lob_handle_columns
                $[ lob_handle_type FOR lob_handle_columns
                 ...                                   $].

Effect

Derivation of a LOB handle structure as a work area for working with streaming and locators in. dbtab expects a DDIC database table defined in the ABAP Dictionary or a DDIC database view defined for view in ABAP Dictionary.

The column specifications lob_handle_columns are used to determine LOBs from dbtab. The statement creates a deep structure that is constructed for all columns that are not among the specified columns exactly as it is constructed for a regular TYPE reference to dbtab. For the LOBs included in the specified columns, a component with the same name is created as the LOB handle component. The static type of the LOB handle components is a class or an interface that is determined by the type specification lob_handle_type, to which the respective specified column is assigned.

The combination options of the additions specified under lob_handle_columns and lob_handle_type are determined by the following rules:

  • A LOB handle structure can be derived for either reading or writing statements only.

  • A structure for writes can only contain the type specifications WRITER and LOCATOR.

  • The definition of the LOB handle components must be mutually exclusive, which means that columns must not be assigned to inappropriate types or a column cannot be assigned to multiple types.
  • The definition of LOB handle components must not contain redundancies. A set of LOB handle components must be produced for each specification of:
... lob_handle_type FOR lob_handle_columns ...
This set of LOB handle components must not overlap with another set of LOB handle components of a different specification.
  • The definition of the LOB handle components must be specified with as few specifications as possible. If the same set of LOB handle components can be created by one rather than multiple specifications, the more comprehensive option must be used.

Apart from the rules specified under lob_handle_columns and lob_handle_type, the following general restrictions also apply:

  • At least one column must be specified.
  • The type specifications for the first three specified columns for LOB handle components for reads or the first two columns for LOB handle components for writes must be different
  • In each case, only one column specification ALL ... COLUMNS can be made, in which BLOB or CLOB are specified.
  • The column specification ALL BLOB$|CLOB COLUMNS includes all BLOBs or CLOBs. When specified, a single BLOB or CLOB cannot be specified in a column specification COLUMNS ... for the same static type.
  • The column specification ALL OTHER COLUMNS includes all columns that are not specified individually. ALL OTHER BLOB COLUMNS or ALL OTHER CLOB COLUMNS cannot be specified at the same time.
  • The column specification ALL COLUMNS includes all LOBs and can therefore only be specified on its own.

Notes

  • LOB handle structures can also be defined using appropriate typing of components between BEGIN OF and END OF.
  • LOB handle structures can also be derived in the ABAP Dictionary. Transaction SE11 offers such a function for DDIC database tables or views containing LOBs.
  • If dbtab does not contain any LOBs that match the specified columns, no LOB handle components are created, and the statement creates a regular work area.
  • If LOBs are added to dbtab that match the specified columns ALL $[OTHER$] ..., LOB handle components are also created for these.

Example

Declaration of types for work areas with LOB handle components for a writer stream and a reader stream for the column PICTURE and a locator for all LOBs in the DDIC database table DEMO_BLOB_TABLE.

Deriving LOB Handle Structures






Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 8389 Date: 20240426 Time: 114100     sap01-206 ( 107 ms )