Ansicht
Dokumentation

ABAPEXPORT_DATA_CLUSTER_PARAM - EXPORT DATA CLUSTER PARAM

ABAPEXPORT_DATA_CLUSTER_PARAM - EXPORT DATA CLUSTER PARAM

CL_GUI_FRONTEND_SERVICES - Frontend Services   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

EXPORT, parameter_list

Short Reference



... ${p1 = dobj1 p2 = dobj2 ...$}
  $| ${p1 FROM dobj1 p2 FROM dobj2 ...$}
  $| (ptab) ...

Additions

1. ... p1 = dobj1 p2 = dobj2 ...

2. ... p1 FROM dobj1 p2 FROM dobj2 ...

3. ... (ptab)

Effect

A data cluster can be defined statically by a parameter list in the form p1 = dobj1 p2 = dobj2 ... or p1 FROM dobj1  p2 FROM dobj2 ... and dynamically by specifying a parenthesized internal table ptab. Here the system searches for the data stored in the data cluster under the names p1, p2, .... The case of the names in the data clusters depends on how they are specified in the ABAP runtime framework. If specified statically (b1, b2, ...), uppercase is used. If specified dynamically in rtab, the case used there is used.

If the data cluster is too big for the memory, an exception is raised.

Addition 1

... p1 = dobj1 p2 = dobj2 ...

Addition 2

... p1 FROM dobj1 p2 FROM dobj2 ...

Effect

In static cases, the content of the data objects dobj is stored under the names p1, p2, ... in the cluster. The name of a parameter p1, p2, ... is converted to uppercase letters and can have a maximum of 255 characters. The specifications p1 = dobj1 p2 = dobj2 ... and p1 FROM dobj1  p2 FROM dobj2 ... have the same meaning. All data types can be used for the data object dobj, except reference types or data types that contain reference types as components. If a data object dobj is an internal table with a header line, the table body is addressed instead of the header line. When an enumerated object is used, the enumerated value is flagged as an enumerated type and saved in the basic type.

Alternative Language Constructs

Notes

  • The use of = is recommended rather than FROM, since = is also used by other ABAP statements to pass data.
  • To export objects referenced by reference variables, these can first be serialized using the statement CALL TRANSFORMATION and then exported. In instances of classes, the class must implement the interface IF_SERIALIZABLE_OBJECT.

Example

Export of three numbers to a data cluster of the DDIC database table DEMO_INDX_BLOB and import of the same three numbers to the components of a structure.

Addition 3

... (ptab)

Effect

In the dynamic case, the parameter list is specified in an index table ptab with two columns. These columns can have any name and must be of the type "character". The first column in ptab must contain the names of the parameters, and the second must list the data objects in any case. The names of the data objects are used exactly as specified in the first column of ptab. If the second column is initial, the name of the parameter in the first column must match the name of a data object. The data object is then stored under its name in the cluster. If the first column of ptab is initial, an uncatchable exception is raised.

Notes

  • Data objects whose names contain lowercase letters in the data cluster cannot be read using the static variant of the specified parameters of the statement IMPORT.
  • Outside of classes, a single-column internal table for parameter_list can also be used. This is the dynamic variant of the obsolete short form used to store the data objects listed in the table to the data cluster implicitly under their names.

Example

Dynamic export of data to a data cluster on the DDIC database table DEMO_INDX_BLOB. The names in the first column of ptab contain lowercase letters, which means that the data can only be imported by being specified dynamically. The second column, on the other hand, is not case-sensitive.






ABAP Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 6425 Date: 20240614 Time: 033704     sap01-206 ( 110 ms )