ABAP Keyword Documentation →  ABAP - Reference →  Processing External Data →  Data Clusters →  EXPORT 

EXPORT - parameter_list

Short Reference

Other versions: 7.31 | 7.40 | 7.54

Syntax

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

Extras

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

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

3. ... (ptab)

Effect

A data cluster can be defined statically by a list in the form p1 = dobj1 p2 = dobj2 ... or p1 FROM dobj1  p2 FROM dobj2 ... and dynamically by specifying a parenthesized internal table ptab. If the data cluster is too big for the memory, an exception is raised.

Note

To export objects that are referenced by reference variables, use the statement CALL TRANSFORMATION to serialize and export these objects if the class of these objects implements the interface IF_SERIALIZABLE_OBJECT.

Addition 1

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

Addition 2

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

Effect

In the case of a static export, the content of the data object dobj is stored under the name p in the cluster. The name of a parameter p can contain a maximum of 255 characters. The variants p1 = dobj1 p2 = dobj2 ... and p1 FROM dobj1  p2 FROM dobj2 ... have the same meaning. You can use all data types except reference types for the data object dobj or data types that contain reference types as components. If a data object dobj is an internal table with a header line, not the header line, but the table body is addressed.

Programming Guideline

Alternative Language Constructs

Notes

• The use of = is recommended rather than FROM, since = is also used by other ABAP statements to pass data.
• Outside of classes, and if the label does not contain an address specification such as an instance component selector or an offset/length specification, the obsolete short form dobj1 dobj2... can be used in the static variant. Here, all data objects are implicitly stored under their name in the data cluster.
  

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 have to be of the type "character". The first column in ptab must contain the names of the parameters, and the second must contain the data objects in uppercase. If the second column is initial, then the name of the parameter in the first column has to 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, a non-handleable exception is raised.

Note

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 save the data objects listed in the table to the data cluster (implicitly using their names).