Variants
1. EXPORT obj1 ... objn TO MEMORY.
2. EXPORT obj1 ... objn TO DATABASE dbtab(ar) ID key.
3. EXPORT obj1 ... objn TO DATASET dsn(ar) ID key.
Variant 1
EXPORT obj1 ... objn TO MEMORY.
Additions
1. ... FROM g (for each field to be exported)
2. ... ID key
Effect
Exports the objects obj1 ... objn (fields, structures or tables) as a data cluster to ABAP/4 memory . If you call a transaction, report or dialog module (with CALL TRANSACTION , SUBMIT or CALL DIALOG ), the contents of ABAP/4 memory are retained, even across several levels. The called transaction can then retrieve the data from there using IMPORT ... FROM MEMORY . Each new EXPORT ... TO MEMORY statement overwrites any old data, so no data is appended.
If the processing leaves the deepest level of the call chain, the ABAP/4 memory is released.
Note
The header lines of internal tables cannot be exported, because specifying the name of an Internal table with a header line always exports the actual table data.
Addition 1
... FROM g (for each object to be exported)
Effect
Exports the contents of the data object g and stores them under the name specified before FROM .
Addition 2
... ID key
Effect
Stores the exported data under the ID key in ABAP/4 memory . You can then use the ID to read it in again (with IMPORT ). The ID can be up to 32 characters long.
Note
If you store data both with and without an ID , the data stored without an ID remains separate and you can re-import it (using IMPORT without ID ).
RELATED POST
SAP ABAP SYNTAX FOR EXEC
CRM Middle ware System Architecture
CRM Middle ware Enhancement
1. EXPORT obj1 ... objn TO MEMORY.
2. EXPORT obj1 ... objn TO DATABASE dbtab(ar) ID key.
3. EXPORT obj1 ... objn TO DATASET dsn(ar) ID key.
Variant 1
EXPORT obj1 ... objn TO MEMORY.
Additions
1. ... FROM g (for each field to be exported)
2. ... ID key
Effect
Exports the objects obj1 ... objn (fields, structures or tables) as a data cluster to ABAP/4 memory . If you call a transaction, report or dialog module (with CALL TRANSACTION , SUBMIT or CALL DIALOG ), the contents of ABAP/4 memory are retained, even across several levels. The called transaction can then retrieve the data from there using IMPORT ... FROM MEMORY . Each new EXPORT ... TO MEMORY statement overwrites any old data, so no data is appended.
If the processing leaves the deepest level of the call chain, the ABAP/4 memory is released.
Note
The header lines of internal tables cannot be exported, because specifying the name of an Internal table with a header line always exports the actual table data.
Addition 1
... FROM g (for each object to be exported)
Effect
Exports the contents of the data object g and stores them under the name specified before FROM .
Addition 2
... ID key
Effect
Stores the exported data under the ID key in ABAP/4 memory . You can then use the ID to read it in again (with IMPORT ). The ID can be up to 32 characters long.
Note
If you store data both with and without an ID , the data stored without an ID remains separate and you can re-import it (using IMPORT without ID ).
RELATED POST
SAP ABAP SYNTAX FOR EXEC
CRM Middle ware System Architecture
CRM Middle ware Enhancement
No comments :
Post a Comment