IMPORT - parameter_list

Syntax

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

Extras:

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

2. ... p1 TO dobj1 p2 TO dobj2 ...

3. ... (ptab)

Effect

A data cluster can be read statically by a list in the form p1 = dobj1 p2 = dobj2 ... or p1 TO dobj1 p2 TO dobj2 ... and dynamically through the specification of a bracketed, internal table ptab.

If a parameter p is specified and it is not stored in the data cluster, the specification will be ignored and the data object dobj retains its current value. The data objects dobj must have the same data type as the parameter p of the cluster, in the standard version. With internal tables, only the row type and not the table type is relevant. The following exceptions apply:

• With data objects of the type c, different lengths are allowed. Then the appropriate conversion rule from the conversion table for source field type c applies.
  
  
• If, in structures, the data types of all components (except for the last one) match and this component is of the type c, it can be extended or abbreviated according to the conversion rule from the conversion table for source field type c. Alignment gaps in front of this component are considered part of the component.
  
  
• If the structures otherwise have the same type and the target structure at the highest level has more components than the source structure in the data cluster, the superfluous components are supplied with type-conform initial values. A substructure of the target structure must not have more components than the respective substructure in the source structure.
  

As of Release 6.10, when structures are exported, there is also information stored as to whether the structure contains components that were adopted using the statement INCLUDE or adopted in the ABAP Dictionary from other structures. A structure into which data is iported must, since Release 6.10, also match the structure in the data cluster with regard to components adopted using INCLUDE. Only for structures that were stored prior to Release 6.10 and structures where all the components of the uppermost hierarchy level were adopted using INCLUDE does the target structure not necessarily need to be set up with the identical INCLUDE statements.

The additions specified under conversion_options allow additional conversions and define other conversion rules. If structured data with same-type components are imported into Unicode systems, and these components were exported in a MDMP system and vice versa, a special text language rule applies.

Note

The rule that a target structure at the hightest level may have more components than the source structure can cause problems in relation to structures defined in the ABAP Dictionary if the structure there is marked as enhanceable. Therefore, this situation triggers a warning message in the enhanced program check since Release 6.40.

Addition 1

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

Addition 2

... p1 TO dobj1 p2 TO dobj2 ...

Effect

In the static case, the contents of the cluster parameter p are read and passed to the data objects dobj. The syntax styles p1 = dobj1 p2 = dobj2 ... and p1 TO dobj1 p2 TO dobj2 ... are the same. If a data object dobj is an internal table with a header line, not the header line, but thetable body is addressed.

Note

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 abbreviated form dobj1 dobj2 ... can be used in the static variant. Here the parameters are searched for implicitly in the cluster under the name of the specified data object.

Addition 3

... (ptab)

Effect

In the dyanamic case, the parameter list is adopted from the two-clumn internal table ptab - whose columns must be character-type. In the first column in ptab, the names of the parameter, and, in the second, the data objects must be listed. If the first column of ptab is initial or an object name is listed twice, an exception that cannot be handled will be triggered.

Outside of classes, a single-column internal table for