importing internal table from one program to another program

[Former Member]

Hi everybody,

i have one small doubt.

i am using submit statement and passing the values from this program to another program selection screen. in that program logic is written.In that program one internal table values are being exported to the memory id of that program. now i have to import that internal table values into my program by using import statement. i am using the following syntax

import itab from menory id 'program name'.

but i am getting an error saying program name is unknown.

what is the exat syntax for this .

thanking you,

giri.

[Former Member]

Hi,

Try this!

e.g.

IMPORT itab FROM MEMORY ID '<program name>'.

program name should be in uppercase.

[GauthamV]

hi,

check these statements.

IMPORT - Get data

Variants:

1. IMPORT obj1 ... objn FROM DATA BUFFER f.

2. IMPORT obj1 ... objn FROM INTERNAL TABLE itab.

2. IMPORT obj1 ... objn FROM MEMORY.

3. IMPORT obj1 ... objn FROM SHARED MEMORY itab(ar) ID key.

4. IMPORT obj1 ... objn FROM SHARED BUFFER itab(ar) ID key.

5. IMPORT obj1 ... objn FROM DATABASE dbtab(ar) ID key.

6. IMPORT obj1 ... objn FROM DATASET dsn(ar) ID key.

7. IMPORT obj1 ... objn FROM LOGFILE ID key.

8. IMPORT DIRECTORY INTO itab FROM DATABASE dbtab(ar) ID key.

9. IMPORT (itab) FROM ... .

In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. For more details, see Storing Cluster Tables.

Variant 1

IMPORT obj1 ... objn FROM DATA BUFFER f.

Extras:

1. ... = f (for each object to be imported)

2. ... TO f (for each object to be imported)

3. ... ACCEPTING PADDING

4. ... ACCEPTING TRUNCATION

5. ... IGNORING STRUCTURE BOUNDARIES

6. ... IGNORING CONVERSION ERRORS

7. ... REPLACEMENT CHARACTER c

8. ... IN CHAR-TO-HEX MODE

9. ... CODE PAGE INTO f1

10. ... ENDIAN INTO f2

The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas.

See You Cannot Use Implicit Field Names in Clusters.

Effect

Imports the data objects obj1 ... objn from the data buffer declared. The data buffer must be of type XSTRING . The data objects obj1 ... objn can be fields, structures, complex structures, or tables. The system imports all the data that has been stored in the data buffer f using the EXPORT ... TO DATA BUFFER statement and is listed here. It also checks that the structure used in the IMPORT statement matches the one in the EXPORT statement.

The Return Code is set as follows:

SY-SUBRC = 0:

The existing data objects in the data cluster specified were imported. The rest remain unchanged. (In some circumstances, this may mean that no data objects were imported).

SY-SUBRC = 4:

The data objects could not be imported. The contents of all the objects remain unchanged.

Addition 1

... = f (for each object to be imported)

Addition 2

... TO f (for each object to be imported)

Effect

The object is stored in the field f.

Addition 3

... ACCEPTING PADDING

Effect

This addition allows you to append new fields to the end

of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.

Addition 4

... ACCEPTING TRUNCATION

Effect

This addition allows you to shorten the last CHAR

fields, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).

Addition 5

... IGNORING STRUCTURE BOUNDARIES

Effect

This addition means that only the fragment sequence is

relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.

You cannot use this addition with either addition 3 (enlarge structure) or addition 4 (shorten structure), since it specifies that structure and include boundaries are to be ignored.

From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.

Addition 6

...IGNORING CONVERSION ERRORS

Effect

This addition prevents the system from triggering a

runtime error, if an error occurs when the character set is converted. '#' is used as a replacement character.

Addition 7

... REPLACEMENT CHARACTER c

Effect

The replacement character is used if a particular

character cannot be converted when the character set is converted.

This addition can only be used in conjunction with addition 6.

Addition 8

... IN CHAR-TO-HEX MODE

Effect

Not all character-type fields are converted. To convert

a field, you must create a field (or structure) that is identical to the exported field or structure, except that all its character-type components must be replaced with hexadecimal fields.

You can only use this addition in Unicode programs, to allow you to import camouflaged binary data as single-byte characters.

Moreover, you cannot use this addition in conjunction with the additions 3, 4, 5, 6, or 7.

Addition 9

... CODE PAGE INTO f1

Effect

The code page of the exported data is stored in the

character-type field f1 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition.

Addition 10

... ENDIAN INTO f2

Effect

The byte order (LITTLE or BIG) of the

exported data is stored in the field f2 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition. The field f2 must have the type ABAP_ENDIAN, which is defined in the type group ABAP. For this reason, the type group ABAP must be included in the ABAP program using a TYPE-POOLS statement.

Variant 2

IMPORT obj1 ... objn FROM INTERNAL TABLE itab.

Extras:

1. ... = f (for each object to be imported)

2. ... TO f (for each object to be imported)

3. ... ACCEPTING PADDING

4. ... ACCEPTING TRUNCATION

5. ... IGNORING STRUCTURE BOUNDARIES

6. ... IGNORING CONVERSION ERRORS

7. ... REPLACEMENT CHARACTER c

8. ... IN CHAR-TO-HEX MODE

9. ... CODE PAGE INTO f1

10. ... ENDIAN INTO f2

The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See No implicit field names in cluster.

Effect

Imports the data objects obj1 ... objn (fields, structures, complex structures, or tables) from the specified internal table itab. The first column in the internal table must be of the predefined type INT2 and the second must be type X. To define the first column you must refer to a data element in the ABAP Dictionary that has the predefined type INT2.

All data that was stored in the internal table itab using EXPORT ... TO INTERNAL TABLE and listed, is imported. The system checks that the EXPORT and IMPORT structures match.

The Return Code is set as follows:

SY-SUBRC = 0:

The existing data objects in the specified data cluster were imported, the rest remain unchanged (it is possible that no data object was imported).

SY-SUBRC = 4:

The data objects could not be imported.

The contents of all listed objects remain unchanged

Addition 1

... = f (for each object to be imported)

Addition 2

... TO f (for each object to be imported)

Effect

Places the object in the field f.

Addition 3

... ACCEPTING PADDING

Effect

This addition allows you to add new fields to the ends

of structures, even to substructures and internal tables (the additional fields are filled with initial value during the IMPORT). It also allows you to increase the size of existing fields (C, N, X, P, I1, and I2) and to map Char fields to STRING type fields or byte fields to XSTRING type fields.

Addition 4

... ACCEPTING TRUNCATION

Effect

This addition allows you to shorten the last CHAR

field or omit the last component on the highest level (till Release 4.6 this was possible without specifying an addition).

Addition 5

... IGNORING STRUCTURE BOUNDARIES

Effect

This addition means that only the page order is

relevant, that is any substructures match. With this addition, the system also ignores alignment changes arising from the Unicode conversion (for example, due to subsequent insertion of named includes).

This addition rules out any subsequent structural enhancements (addition 3) or structural shortening (addition 4) because with this addition it is the structural limits and include limits that are to be ignored.

As from Release 6.10, the include information will also be stored in the dataset, so that it is possible to also check whether the includes match, that is substructures and includes (named or unnamed) are treated the same. When importing data that was exported in a Release lower than 6.10, the includes are not checked.

Addition 6

...IGNORING CONVERSION ERRORS

Effect

This addition has the effect that an error in the

character set conversion does not cause a runtime error. The system uses "#" as a replacement character.

Addition 7

... REPLACEMENT CHARACTER c

Effect

The system uses the specified replacement character if a

character cannot be converted during a character set conversion. If this addition is not specified, the system uses "#" as a replacement character.

This addition can only be used in conjunction with addition 6.

Addition 8

... IN CHAR-TO-HEX MODE

Effect

No character type fields are converted. For this you

must create a field or structure that is identical to the exported field or exported structure, except that all character type fields must be replaced with hexadecimal fields.

This addition, which is only allowed in programs with a set Unicode flag, allows you to import binary data disguised as single byte characters. This addition cannot be used in conjunction with additions 3, 4, 5, 6, and 7.

Addition 9

... CODE PAGE INTO f1

Effect

The codepage of the exported data is stored in the

character-type field f1 (for example, to be able to analyze the data imported with the addition IN CHAR-TO-HEX MODE).

Addition 10

... ENDIAN INTO f2

Effect

The byte order (LITTLE or BIG) of the

exported data is stored in the field f2 (for example, to be able analyze the data imported using the addition IN CHAR-TO-HEX MODE). The field f2 must be of type ABAP_ENDIAN, defined in type group ABAP. You must therefore include the type group ABAP in the ABAP program with a TYPE-POOLS statement.

Variant 3

IMPORT obj1 ... objn FROM MEMORY.

Extras:

1. ... = f (for each object to be imported) 2. ... TO f (for each object to be imported)

3. ... ID key

4. ... ACCEPTING PADDING

5. ... ACCEPTING TRUNCATION

6. ... IGNORING STRUCTURE BOUNDARIES

The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See You Must Enter Identification and Cannot Use Implicit Field Names inClusters

Effect

Imports data objects obj1 ... objn (fields, structures, complex structures or tables) from a data cluster in the ABAP memory (see EXPORT). Reads in all data without an ID that was exported to memory with "EXPORT ... TO MEMORY.". In contrast to the variant IMPORT FROM DATABASE, it does not check that the structure matches in EXPORT and IMPORT.

The Return Code is set as follows:

SY-SUBRC = 0:

The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that no data objects were imported).

SY-SUBRC = 4:

The data objects could not be imported, probably because the ABAP memory was empty.

The contents of all objects remain unchanged.

Note

You should always use the addition 3 (... ID key) with the statement. Otherwise, the effect of the variant is not certain (EXPORT statements in different parts of a program overwrite each other in the ABAP memory), since it exists only for reasons of compatibility with R/2.

Additional methods for selecting and deleting data clusters in the ABAP memory are provided by the system class CL_ABAP_EXPIMP_MEM.

Please consult Data Area and Modularization Unit Organization documentation as well.

Addition 1

... = f (for each object to be imported)

Addition 2

... TO f (for each object to be imported)

Effect

The object is placed in field f.

Addition 3

... ID key

Effect

Imports only data stored in ABAP memory under the ID key.

Notes

The key, key, must be a character-type data object (but not a string).

The Return Code is set as follows:

SY-SUBRC = 0:

The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that no data objects were imported).

SY-SUBRC = 4:

The data objects could not be imported, probably because an incorrect ID was used.

The contents of all objects remain unchanged.

Addition 4

... ACCEPTING PADDING

Effect

This addition allows you to append new fields to the end of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.

Addition 5

... ACCEPTING TRUNCATION

Effect

This addition allows you to shorten the last CHAR field, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).

Addition 6

... IGNORING STRUCTURE BOUNDARIES

Effect

This addition means that only the fragment sequence is relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.

You cannot use this addition with either addition 3 (enlarge structure) or addition 4 (shorten structure), since it specifies that structure and include boundaries are to be ignored.

From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.

Related

EXPORT TO MEMORY, DELETE FROM MEMORY, FREE MEMORY

Variant 4

IMPORT obj1 ... objn FROM SHARED MEMORY itab(ar) ID key.

Extras:

1. ... = f (for each object to be exported) 2. ... TO f (for each object to be exported)

3. ... CLIENT g (before ID key)

4. ... TO wa (after itab(ar) or ID key )

5. ... ACCEPTING PADDING

6. ... ACCEPTING TRUNCATION

7. ... IGNORING STRUCTURE BOUNDARIES

The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas.

See You Cannot Use Implicit Field Names in Clusters and You Cannot Use Table Work Areas.

Effect

Imports the data objects obj1 ... objn (fields, structures, complex structures, or tables) from shared memory. The data objects are read using the ID key from the area ar in the table itab - c.f. EXPORT TO SHARED MEMORY). You must use itab to specify a database table although the system reads from a memory table with the appropriate structure.

The Return Code is set as follows:

SY-SUBRC = 0:

The existing data objects in the data cluster specified were imported. The rest remain unchanged. (In some circumstances, this may mean that no data objects were imported).

SY-SUBRC = 4:

The data objects could not be imported. You may have used the wrong ID. The contents of all the objects remain unchanged.

Notes

The table dbtab named according to SHARED MEMORY must be declared using TABLES (except in addition 2).

The structure of fields (field symbols and internal tables) to be imported must match the structure of the objects exported in the dataset. The objects must be imported under the same names as those under which they were exported. Otherwise, they will not be imported.

The key length consists of: the client (3 digits, but only if tab is client-specific); area (2 characters); ID; and line number (4 bytes). It must not exceed 64 bytes - that is, the ID must not be longer than 55 characters, if the table is client- specific.

The key, key, must be a character-type data object (but not a string).

Additional methods for selecting and deleting data clusters in the shared memory are provided by the system class CL_ABAP_EXPIMP_SHMEM.

Please consult Data Area and Modularization Unit Organization documentation as well.

Addition 1

... = f (for each object to be imported)

Addition 2

... TO f (for each object to be imported)

Effect

The object is stored in the field f.

Addition 3

... CLIENT g (before ID key)

Effect

The data is imported from client g (provided the import/export table is tab client-specific). The client, g must be a character-type data object (but not a string).

Addition 4

... TO wa (after itab(ar) or ID key)

Effect

You need to use this addition if user data fields have been stored in the application buffer and are to be read from there. The work area wa is used instead of the table work area. The target area must correspond to the structure of the called table tab.

Addition 5

... ACCEPTING PADDING

Effect

This addition allows you to: append new fields to the end of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.

Addition 6

... ACCEPTING TRUNCATION

Effect

This addition allows you to shorten the last CHAR fields, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).

Addition 7

... IGNORING STRUCTURE BOUNDARIES

Effect

This addition means that only the fragment sequence is relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.

You cannot use this addition with either addition 4 (enlarge structure) or addition 5 (shorten structure), since it specifies that structure and include boundaries are to be ignored.

From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.

Related

EXPORT TO SHARED MEMORY, DELETE FROM SHARED MEMORY

Variant 5

IMPORT obj1 ... objn FROM SHARED BUFFER itab(ar) ID key.

Extras:

1. ... = f (for each object to be exported) 2. ... TO f (for each object to be exported)

3. ... CLIENT g (before ID key)

4. ... TO wa (last addition or after itab(ar))

The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas.

See Cannot Use Implicit Fieldnames in Clusters und Cannot Use Table Work Areas.

Effect

Imports data objects obj1 ... objn (fields or

tables) from the cross-transaction application buffer. The data objects are read in the application buffer using the ID key of the area ar of the buffer area for the table itab (see EXPORT TO SHARED BUFFER). You must use dbtab to specify a database table although the system reads from a memory table with an appropriate structure.

The Return Code is set as follows:

SY-SUBRC = 0:

The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this means that no data objects were imported).

SY-SUBRC = 4:

The data objects could not be imported, probably because an incorrect ID was used.

The contents of all objects remain unchanged.

Example

Import two fields and an internal table from the application buffer with the structure INDX:

TYPES: BEGIN OF ITAB3_LINE,

CONT(4),

END OF ITAB3_LINE.

DATA: INDXKEY LIKE INDX-SRTFD VALUE 'KEYVALUE',

F1(4),

F2(8) TYPE P DECIMALS 0,

ITAB3 TYPE STANDARD TABLE OF ITAB3_LINE,

INDX_WA TYPE INDX.

• Import data.

IMPORT F1 = F1 F2 = F2 ITAB3 = ITAB3

FROM SHARED BUFFER INDX(ST) ID INDXKEY TO INDX_WA.

• After import, the data fields INDX-AEDAT and

• INDX-USERA in front of CLUSTR are filled with

• the values in the fields before the EXPORT

• statement.

Notes

You must declare the table dbtab, named after DATABASE using a TABLES statement.

The structure of the fields, structures, and internal tables to be imported must match the structure of the objects exported to the dataset. Moreover, the objects must be imported with the same name used to export them. Otherwise, the import is not performed.

The maximum total key length is 64 bytes. It must include: a client if the table is client-specific (3 characters); an area (2 characters); identification; and line counter (4 bytes). This means that the number of characters available for the identification of a client-specific table is 55 characters.

The key, key, must be a character-type data object (but not a string).

Additional methods for selecting and deleting data clusters in the cross-transaction application buffer are provided by the system class CL_ABAP_EXPIMP_SHBUF.

Please consult Data Area and Modularization Unit Organization documentation as well.

Addition 1

... = f (for each object to be imported)

Addition 2

... TO f (for each object to be imported)

Effect

The object is placed in the field f

Addition 3

... CLIENT g (after dbtab(ar))

Effect

Takes the data from the client g (if the import/export table dbtab is client-specific). The client g must be a character-type data object (but not a string).

Addition 4

... TO wa (as the last addition or after itab(ar))

Effect

You need to use this addition if you want to save user data fields in the application buffer and then read them from there later. The system uses a work area wa instead of a table work area. The target area must have the same structure as the table tab.

Example

DATA: INDX_WA TYPE INDX,

F1.

IMPORT F1 = F1 FROM SHARED BUFFER INDX(AR)

CLIENT '001' ID 'TEST'

TO INDX_WA.

WRITE: / 'AEDAT:', INDX_WA-AEDAT,

/ 'USERA:', INDX_WA-USERA,

/ 'PGMID:', INDX_WA-PGMID.

Variant 6

IMPORT obj1 ... objn FROM DATABASE dbtab(ar) ID key.

Extras:

1. ... = f (for each object to be imported)

2. ... TO f (for each object to be imported)

3. ... CLIENT g (before ID key )

4. ... USING form

5. ... TO wa (last addition or after dbtab(ar))

6. ... MAJOR-ID id1 (instead of ID key)

7. ... MINOR-ID id2 (with MAJOR-ID id1 )

8. ... ACCEPTING PADDING

9. ... ACCEPTING TRUNCATION

10. ... IGNORING STRUCTURE BOUNDARIES

11. ... IGNORING CONVERSION ERRORS

12. ... REPLACEMENT CHARACTER c

13. ... IN CHAR-TO-HEX MODE

14. ... CODE PAGE INTO f1

15. ... ENDIAN INTO f2

The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Implicit Fieldnames in Clusters and Cannot Use Table Work Areas.

Effect

Imports data objects obj1 ... objn (fields, structures, complex structures, or tables) from the data cluster with ID key in area ar of the database table dbtab (see EXPORT TO DATABASE).

The Return Code is set as follows:

SY-SUBRC = 0:

The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that not data objects were imported).

SY-SUBRC = 4:

The data objects could not be imported, probably because an incorrect ID was used.

The contents of all objects remain unchanged.

Example

Import two fields and an internal table:

TYPES: BEGIN OF TAB3_TYPE,

CONT(4),

END OF TAB3_TYPE.

DATA: INDXKEY LIKE INDX-SRTFD,

F1(4), F2 TYPE P,

TAB3 TYPE STANDARD TABLE OF TAB3_TYPE WITH

NON-UNIQUE DEFAULT KEY,

WA_INDX TYPE INDX.

INDXKEY = 'INDXKEY'.

IMPORT F1 = F1

F2 = F2

TAB3 = TAB3 FROM DATABASE INDX(ST) ID INDXKEY

TO WA_INDX.

Notes

You must declare the table dbtab, named after DATABASE, using the TABLES statement (except in addition 5).

The structure of fields, field strings and internal tables to be imported must match the structure of the objects exported to the dataset. In addition, the objects must be imported under the same name used to export them. If this is not the case, either a runtime error occurs or no import takes place.

Exception: You can lengthen or shorten the last field if it is of type CHAR, or add/omit CHAR fields at the end of the structure.

The key, key, must be a character-type data object (but not a string).

Additional methods for selecting and deleting data clusters in the database table specified are provided by the system class CL_ABAP_EXPIMP_DB.

Addition 1

... = f (for each object to be imported)

Addition 2

... TO f (for each object to be imported)

Effect

The object is placed in field f.

Addition 3

... CLIENT g (before the ID key)

Effect

Data is taken from the client g (in client-specific import/export databases only). Client g must be a character-type data object (but not a string).

Example

DATA: F1,

WA_INDX TYPE INDX.

IMPORT F1 = F1 FROM DATABASE INDX(AR) CLIENT '002' ID 'TEST'

TO WA_INDX.

Addition 4

... USING form

Note

This statement is for internal use only.

Incompatible changes or further developments may occur at any time without warning or notice.

Effect

Does not read the data from the database. Instead, calls the FORM routine form for each record read from the database without this addition. This routine can take the data key of the data to be retrieved from the database table work area and write the retrieved data to this work area. The name of the routine has the format <name of database table>_<name of form>; it has one parameter which describes the operation (READ, UPDATE or INSERT). The routine must set the field SY-SUBRC in order to show whether the function was successfully performed.

Addition 5

... TO wa (after key or after dbtab(ar))

Effect

You need to use this addition if you want to save user data fields in the cluster database and then read from there. The system uses the work area wa instead of a table work area. The target area entered must have the same structure as the table dbtab.

Example

DATA WA LIKE INDX.

DATA F1.

IMPORT F1 = F1 FROM DATABASE INDX(AR)

CLIENT '002' ID 'TEST'

TO WA.

WRITE: / 'AEDAT:', WA-AEDAT,

/ 'USERA:', WA-USERA,

/ 'PGMID:', WA-PGMID.

Addition 6

... MAJOR-ID id1 (instead of the ID key).

Addition 7

... MINOR-ID id2 (with MAJOR-ID id1)

This addition is not allowed in an ABAP Objects context. See Cannot Use Generic Identification.

Effect

Searches for a record the first part of whose ID (length of id1) matches id1 and whose second part - if MINOR-ID id2 is also declared - is greater than or equal to id2.

Addition 8

... ACCEPTING PADDING

Effect

This addition allows you to append new fields to the end of structures, sub-structures, and internal tables. The IMPORT statement fills the additional fields with initial values; make existing fields (C, N, X, P, I1, and I2) longer; map character-type fields to STRING-type fields; or to map byte-type fields to XSTRING-type fields.

Addition 9

... ACCEPTING TRUNCATION

Effect

This addition allows you to shorten the last CHAR fields, or to omit the last component at the top level. (Until Release 4.6, you could do this without using an addition).

Addition 10

... IGNORING STRUCTURE BOUNDARIES

Effect

This addition means that only the fragment sequence is relevant - that is, that any sub-structures match. If you use this addition, the system ignores any alignment changes necessitated by Unicode - such as inserting named includes.

You cannot use this addition with either addition 8 (enlarge structure) or addition 9 (shorten structure), since it specifies that structure and include boundaries are to be ignored.

From Release 6.10 onwards, the include information is stored in datasets, so that the system can also check that includes match - that is, that sub-structures and includes (named or unnamed) are treated equally. When data is imported in a Release prior to 6.10, includes are not checked.

Addition 11

...IGNORING CONVERSION ERRORS

Effect

This addition prevents the system from triggering a runtime error, if an error occurs when the character set is converted. '#' is used as a replacement character.

Addition 12

... REPLACEMENT CHARACTER c

Effect

The replacement character is used if a particular character cannot be converted when the character set is converted. If you do not use this addition, '#' is used as a replacement character.

This addition can only be used in conjunction with addition 11.

Addition 13

... IN CHAR-TO-HEX MODE

Effect

All character-type fields are not converted. To convert a field, you must create a field (or structure) that is identical to the exported field or structure, except that all its character-type components must be replaced with hexadecimal fields.

You can only use this addition in Unicode programs, to allow you to import camouflaged binary data as single-byte characters. Moreover, you cannot use this addition in conjunction with the additions 8, 9, 10, 11, and 12.

Addition 14

... CODE PAGE INTO f1

Effect

The code page of the exported data is stored in the character-type field f1 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition.

Addition 15

... ENDIAN INTO f2

Effect

The byte order(LITTLE or BIG) of the exported data is stored in the field f2 - for example, to analyze data that has been imported with the IN CHAR-TO-HEX MODE addition. The field f2 must have the type ABAP_ENDIAN, which is defined in the type group ABAP. For this reason, the type group ABAP must be included in the ABAP program using a TYPE-POOLS statement.

Variant 7

IMPORT obj1 ... objn FROM DATASET dsn(ar) ID key.

This variant is not allowed in an ABAP Objects context. See Cannot Use Clusters in Files

Note

This variant is no longer supported and cannot be used.

Variant 8

IMPORT obj1 ... objn FROM LOGFILE ID key.

Note

This statement is for internal use only.

Incompatible changes or further developments may occur at any time without warning or notice.

Extras:

1. ... = f (for each field f to be imported) 2. ... TO f (for each field f to be imported)

The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Implicit Field Names in Clusters

Effect

Imports data objects (fields, field strings or internal tables) from the update data. You must specify the update key assigned by the system (with current request number) as the key.

The key, key, must be a character-type data object (but not a string).

The Return Code is set as follows:

SY-SUBRC = 0:

The existing data objects in the data cluster specified were imported. The rest remain unchanged (in some circumstances, this may mean that no data objects were imported).

SY-SUBRC = 4:

The data objects could not be imported. An incorrect ID may have been used.

The contents of all objects remain unchanged.

Addition 1

... = f (for each object to be imported)

Addition 2

... TO f (for each object to be imported)

Effect

The object is placed in field f.

Variant 9

IMPORT DIRECTORY INTO itab FROM DATABASE dbtab(ar) ID key.

Extras:

1. ... CLIENT g (after dbtab(ar)) 2. ... TO wa (last addition or after dbtab(ar))

The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Table Work Areas.

Effect

Imports an object directory stored under the specified ID with EXPORT TO DATABASE into the table itab. The internal table itab may not have the type HASHED TABLE or ANY TABLE.

The key, key, must be a character-type data object (but not a string).

The Return Code is set as follows:

SY-SUBRC = 0:

The directory was successfully imported.

SY-SUBRC = 4:

The directory could not be imported, probably because an incorrect ID was used.

The internal table itab must have the same structure as the Dictionary structure CDIR (INCLUDE STRUCTURE).

Addition 1

... CLIENT g (before ID key)

Effect

Takes data from the client g (only with client-specific import/export databases). Client g must be a character-type data object (but not a string).

Addition 2

... TO wa (last addition or after dbtab(ar))

Effect

Uses the work area wa instead of the table work area. When you use this addition, you do not need to declare the table dbtab, named after DATABASE using a TABLES statement. The work area entered must have the same structure as the table dbtab.

Example

Directory of a cluster consisting of two fields and an internal table:

TYPES: BEGIN OF TAB3_LINE,

CONT(4),

END OF TAB3_LINE,

BEGIN OF DIRTAB_LINE.

INCLUDE STRUCTURE CDIR.

TYPES END OF DIRTAB_LINE.

DATA: INDXKEY LIKE INDX-SRTFD,

F1(4),

F2(8) TYPE P decimals 0,

TAB3 TYPE STANDARD TABLE OF TAB3_LINE,

DIRTAB TYPE STANDARD TABLE OF DIRTAB_LINE,

INDX_WA TYPE INDX.

INDXKEY = 'INDXKEY'.

EXPORT F1 = F1

F2 = F2

TAB3 = TAB3

TO DATABASE INDX(ST) ID INDXKEY " TAB3 has 17 entries

FROM INDX_WA.

...

IMPORT DIRECTORY INTO DIRTAB FROM DATABASE INDX(ST) ID INDXKEY

TO INDX_WA.

Then, the table DIRTAB contains the following:

NAME OTYPE FTYPE TFILL FLENG

-

---

F1 F C 0 4

F2 F P 0 8

TAB3 T C 17 4

The meaning of the individual fields is as follows:

NAME:

Name of stored object

OTYPE:

Object type (F: Field, R: Field string / Dictionary structure, T: Internal table)

FTYPE:

Field type (C: Character, P: Packed, ...)

Field strings and internal tables have the type C.

TFILL:

Number of internal table lines filled

FLENG:

Length of field in bytes

With internal tables: Length of header line.

Variant 10

IMPORT (itab) FROM ... .

Effect

Specifies the objects to be imported as the internal table itab. You can use this variant instead of the static object lists in the "... FROM DATA BUFFER ", "... FROM MEMORY", "... FROM SHARED MEMORY",

"... FROM SHARED BUFFER", " ... FROM DATABASE", and "... FROM DATASET" variants. You can use all of the additions from these static variants in this 'dynamic' variant. The table itab may not have the type HASHED TABLE or ANY TABLE.

Note

Structure of the internal table itab:

The first column contains the objects names in the data cluster (corresponds to obj1 ...objn in the static case). The second column contains the name in the program if this is different (corresponding to the field f in the FROM f addition). If the table only has one column, or the second column only contains blanks, this corresponds to a static IMPORT without a TO addition. In any case, the first column of the table (and the second, if applicable) should have the type CHAR or STRING.

Example

TYPES: BEGIN OF OBJ_LINE,

CLUSTERNAME(30),

PROGRAMNAME(10),

END OF OBJ_LINE,

BEGIN OF B_LINE,

FIELD_1 TYPE I,

FIELD_2(1) TYPE N,

END OF B_LINE.

DATA: OBJ_TAB TYPE STANDARD TABLE OF OBJ_LINE,

OBJ_WA TYPE OBJ_LINE,

B_PROG TYPE STANDARD TABLE OF B_LINE,

B_WA TYPE B_LINE,

A(10),

C_PROG LIKE SYST.

MOVE: 'A' TO OBJ_WA-CLUSTERNAME.

APPEND OBJ_WA TO OBJ_TAB. CLEAR OBJ_WA.

MOVE: 'B' TO OBJ_WA-CLUSTERNAME,

'B_PROG' TO OBJ_WA-PROGRAMNAME.

APPEND OBJ_WA TO OBJ_TAB. CLEAR OBJ_WA.

MOVE: 'C' TO OBJ_WA-CLUSTERNAME,

'C_PROG' TO OBJ_WA-PROGRAMNAME.

APPEND OBJ_WA TO OBJ_TAB. CLEAR OBJ_WA.

IMPORT (OBJ_TAB) FROM MEMORY ID 'ABCD'.

The dynamic EXPORT statement corresponds to the static IMPORT statement

IMPORT A = A B = B_PROG C = C_PROG FROM MEMORY ID 'ABCD'.

This imports the field A into field A, the internal table B into internal table B_PROG and the structure C into structure C_PROG.

The Return Code is set as follows:

SY-SUBRC is set in exactly the same way as in a static IMPORT.

Exceptions

The exceptions of the statement IMPORT are described in IMPORT Exceptions.

Additional help

Reading Data Objects from Memory

Creating a Table of Contents for a Data Cluster

Reading Data Objects from a Cluster Database

[Former Member]

Hi,

YOu need to use export and import memory.

Thanks,

Sriram Ponna.

[Former Member]

hey check this link

PS: award pts if Helps

[Former Member]

in program 1:

export p1 = name_table_here to memory id '123'.

in program 2:

import p1= name_table_here from memory id '123'.

id is random, but needs to be the same in both statements.

Hope that helps.

[Former Member]

SUBMIT zefl_soff_update_single

WITH so_objid IN fin_tran

AND RETURN

EXPORTING LIST TO MEMORY.

CALL FUNCTION 'LIST_FROM_MEMORY'

TABLES

listobject = t_list

EXCEPTIONS

not_found = 1.

IF sy-subrc NE 0.

ENDIF.

REFRESH t_ascii.

CALL FUNCTION 'LIST_TO_ASCI'

TABLES

listasci = t_ascii " list converted to ASCII

listobject = t_list

EXCEPTIONS

empty_list = 1

list_index_invalid = 2

OTHERS = 3.

IF sy-subrc NE 0.

ENDIF.

LOOP AT t_ascii.

WRITE : t_ascii-f1.

ENDLOOP.

this will help.........U

Reward IF...................

Regards

Anbu