ABAP_SYNTAX_OBS TABLES> dbtab. ... EXPORT> parameter_list> TO DATABASE$|${SHARED MEMORY$}$|${SHARED BUFFER$} $[CLIENT cl$] ID id> $[COMPRESSION ${ON$|OFF$}$]. ... IMPORT> parameter_list> FROM DATABASE$|${SHARED MEMORY$}$|${SHARED BUFFER$} $[CLIENT cl$] ID id> $[conversion_options>$].>
What does it do? If the addition FROM wa> or TO wa> is not specified in exports or imports using the media database table or shared memory, the ABAP runtime framework attempts to transport the components between SRTF2>> and CLUSTR>> of the table work area> declared using TABLES dbtab>. If the table work area is not found, these components are not transported.
Latest notes:
In global classes, it is not possible to use table work areas anyway. In local classes of programs other than class pools>, the implicit mechanism is applied to any table work areas of their compilation unit>.
The implicit use of table work areas is obsolete and hence the short forms shown here should no longer be used for data transports. Instead, it is recommended that FROM wa> and TO wa> are specified explicitly if the components between SRTF2> and CLUSTR> are written or read. ABAP_HINT_END