SAP EXPORT IMPORT - Obsolete ABAP Statements

Warning: Undefined variable $saptab in /customers/9/5/e/s4hd.com/httpd.www/sap/abap-statements/index.php on line 47

Warning: file_get_contents(/customers/9/5/e/s4hd.com/httpd.www/global/php/adxcode.txt): Failed to open stream: No such file or directory in /customers/9/5/e/s4hd.com/httpd.www/global/php/helpers.php on line 89

Get Example source ABAP code based on a different SAP table

Warning: Undefined variable $prev in /customers/9/5/e/s4hd.com/httpd.www/sap/abap-statements/index.php on line 63
• EXPORT - short form ABAP Statement
• IMPORT - short form ABAP Statement

EXPORT, IMPORT, Short Form of the Parameter List

ABAP_SYNTAX_OBS
EXPORT dobj1 dobj2 ... TO medium $[COMPRESSION${ON$|OFF$}$].

IMPORT dobj1 dobj2 ... FROM medium $[ conversion_options$].

What does it do?
If the parameter lists of the statements EXPORT or IMPORT use the short form

dobj1 dobj2 ...

instead of

p1 = dobj1 p2 = dobj2 ...

or

p1 FROM$|TO dobj1 p2 FROM$|TO dobj2

the parameters are stored or searched for implicitly in the cluster under the name of the specified data object.
This short form is only allowed outside of classes and only if the name does not contain an address specified using an instance component selector or an offset/length specification . If the short form is possible, it can be mixed with the correct form:
dobj1 p2 = dobj2 ...
This short form is prone to errors since the current name is used as an ID for the stored data. When imported into another context, the names of the exporting context must be known and specified identically.

Latest notes:
If the parameter list is specified dynamically in an internal table ptab, the short form is also supported outside of classes by specifying a single-column table. Just like the static short form, this is now also obsolete.
ABAP_HINT_END

Return to menu