ABAPIMPORT_PARAMETERLIST - IMPORT PARAMETERLIST

General Data in Customer Master   General Material Data  
This documentation is copyright by SAP AG.

IMPORT - parameter_list

Short Reference

Syntax

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

Additions

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

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

3. ... (ptab)

Effect

A datacluster 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 willbe ignored and the data object dobj retains its current value. The data objects dobj musthave 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 conversionrule 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 componentis 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-conforminitialvalues. A substructure of the target structure must not have more components than the respective substructure in the source structure.
  

When structures are exported, information is stored as to whether the structure contains componentsthat were adopted using the statement INCLUDEor adopted in the ABAP Dictionary from other structures. A structure into which data is imported mustalso 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 ofthe uppermost hierarchy level were adopted using INCLUDE does the target structure not necessarily need to be set up with the identical INCLUDE statements.

When importing from internal tables with non-unique table keys, the sequence of duplicate lines in relation to these keys is not retained.

The additions specified under conversion_optionsallow additional conversions and define other conversion rules. If structured data with same-type components are imported intoUnicode systems, and these components were exported in aMDMP system and vice versa, a specialtext language rule applies.

Note

The rule that a target structure at the highest level may have more components than the source structurecan 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.

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 objectsdobj. 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 aheader line, not the header line, but thetable body is addressed.

Notes

• It is recommended to use = instead of TO because = is also used in other ABAP statements for transferring data.
  
• Outside of classes, and if the identifier does not contain an address specification such as aninstance component selector or anoffset/length specification, theobsoleteshort form dobj1 dobj2... can still 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 dynamic case, the parameter list is copied from the two-column internal table ptab - whosecolumns must be character-type. In the first column in ptab, the names of the parameters, and,in the second, the data objects in uppercase 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 parameter_list can be used in the dynamicform. In this case, the parameters are searched for implicitly in the cluster under the name of the specified data object.

Note

Outside of classes, a single-column internal table can also be used for parameter_list. This is the dynamic variant of theobsoleteshort form in which the data objects stored in the data cluster are searched for based on the name of the data objects specified in the table.

Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.


Length: 7797 Date: 20120522 Time: 065138     triton ( 271 ms )