Import Internal Table

Hi guys...
How can I import a internal table in a method of Badi?
For example:
I have the itab_ekpo that I export to memory in a especific program and need to import this table.
Hw can I do this in a method ?
tks
flavio

Hi,
If the table data is filled in same session and BADI is called is in same session then you use simple EXPORT TO MEMORY-ID and IMPORT TO MEMORY-ID statement.
Else if both are done in different session then use EXPORT using INDX table and IMPORT the DATABASE INDX in your BADI.
Please see the F1 documentation for the keyword help.
Regards,
SRinivas

Similar Messages

Importing internal table in Adobe Interactive Forms

Hi all,
at the moment I do my first steps in AIF.
I have created a report and select dd02l, dd03l and dd04l.
dd02l is a structure. dd03l and dd04l are internal tables.
How can I import internal tables into my function module with getting a runtime error? Fields and structures are no problem?
I have defined both internal tables as importing parameter in my form interface because I cannot define internal tables ;o(
Thx 4 help & regards
Michael

hi,
find attached document it will helpful for u go to link
1.https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c2567f2b-0b01-0010-b7b5-977cbf80665d
2.https://www.sdn.sap.com/irj/sdn/abap-elearning
thanks reward if helpful

Export & Import internal table data across the programs

Hi All,
I have two different reports,let say ZPRO1 & ZPRO2. I want to export internal table data of ZPRO1 to ZPRO2 and then I want to do some calculations in ZPRO2 with the imported internal table data(ZPRO1).
If I use 'SUBMIT' or CALL TRANSACTION syntax ZPRO1 is displaying..but I want to use only internal table data of ZPRO1.
Pls advise.
Pranitha.

Hi,
Please follow the simple code and try to solve your issue.
Code in program1
types: begin of ty_itab,
       matnr type matnr,
       end of ty_itab.
data: it_itab type table of ty_itab,
      wa_itab type ty_itab,
      it_itab1 type table of ty_itab.
select matnr from mara into table it_itab.
export it_itab to shared buffer indx(st) id 'ABC'.
Code in program2
types: begin of ty_itab,
       matnr type matnr,
       end of ty_itab.
data: it_itab type table of ty_itab,
      wa_itab type ty_itab.
import it_itab from shared buffer indx(st) id 'ABC'.
loop at it_itab into wa_itab.
write:/ wa_itab-matnr.
endloop.
Please delete shared buffer indx(st) id 'ABC', once we don't need the internal table data.
Regards
Dande

Regarding Exporting and Importing internal table

Hello Experts,
I have two programs:
1) Main program: It create batch jobs through open_job,submit and close job.Giving sub program as SUBMIT.
I am using Export IT to memory id 'MID' to export internal table data to sap memory in the subprogram.
The data will be processed in the subprogram and exporting data to sap memory.I need this data in the main program(And using import to get the data,but it is not working).
Importing IT1 from memory id 'MID' to import the table data in the main program after completing the job(SUBMIT SUBPROGRAM AND RETURN).
Importing is not getting data to internal table.
Can you please suggest something to solve this issue.
Thank you.
Regards,
Anand.

Hi,
This is the code i am using.
DO g_f_packets TIMES.
* Start Immediately
       IF NOT p_imm IS INITIAL .
         g_flg_start = 'X'.
       ENDIF.
       g_f_jobname = 'KZDO_INHERIT'.
       g_f_jobno = g_f_jobno + '001'.
       CONCATENATE g_f_jobname g_f_strtdate g_f_jobno INTO g_f_jobname
                                              SEPARATED BY '_'.
       CONDENSE g_f_jobname NO-GAPS.
       p_psize1 = p_psize1 + p_psize.
       p_psize2 = p_psize1 - p_psize + 1.
       IF p_psize2 IS INITIAL.
         p_psize2 = 1.
       ENDIF.
       g_f_spname = 'MID'.
       g_f_spid = g_f_spid + '001'.
       CONDENSE g_f_spid NO-GAPS.
       CONCATENATE g_f_spname g_f_spid INTO g_f_spname.
       CONDENSE g_f_spname NO-GAPS.
* ... (1) Job creating...
       CALL FUNCTION 'JOB_OPEN'
         EXPORTING
           jobname          = g_f_jobname
         IMPORTING
           jobcount         = g_f_jobcount
         EXCEPTIONS
           cant_create_job = 1
           invalid_job_data = 2
           jobname_missing = 3
           OTHERS           = 4.
       IF sy-subrc <> 0.
         MESSAGE e469(9j) WITH g_f_jobname.
       ENDIF.
* (2)Report start under job name
       SUBMIT (g_c_prog_kzdo)
              WITH p_lgreg EQ p_lgreg
              WITH s_grvsy IN s_grvsy
              WITH s_prvsy IN s_prvsy
              WITH s_prdat IN s_prdat
              WITH s_datab IN s_datab
              WITH p1      EQ p1
              WITH p3      EQ p3
              WITH p4      EQ p4
              WITH p_mailid EQ g_f_mailid
              WITH p_psize EQ p_psize
              WITH p_psize1 EQ p_psize1
              WITH p_psize2 EQ p_psize2
              WITH spid     EQ g_f_spid
              TO SAP-SPOOL WITHOUT SPOOL DYNPRO
              VIA JOB g_f_jobname NUMBER g_f_jobcount AND RETURN.
*(3)Job closed when starts Immediately
       IF NOT p_imm IS INITIAL.
         IF sy-index LE g_f_nojob.
           CALL FUNCTION 'JOB_CLOSE'
             EXPORTING
               jobcount             = g_f_jobcount
               jobname              = g_f_jobname
               strtimmed            = g_flg_start
             EXCEPTIONS
               cant_start_immediate = 1
               invalid_startdate    = 2
               jobname_missing      = 3
               job_close_failed     = 4
               job_nosteps          = 5
               job_notex            = 6
               lock_failed          = 7
               OTHERS               = 8.
           gs_jobsts-jobcount = g_f_jobcount.
           gs_jobsts-jobname = g_f_jobname.
           gs_jobsts-spname   = g_f_spname.
           APPEND gs_jobsts to gt_jobsts.
         ELSEIF sy-index GT g_f_nojob.
           CLEAR g_f_flg.
           DO.                         " Wiating untill any job completion
             LOOP AT gt_jobsts into gs_jobsts.
               CLEAR g_f_status.
               CALL FUNCTION 'BP_JOB_STATUS_GET'
                 EXPORTING
                   JOBCOUNT                         = gs_jobsts-jobcount
                   JOBNAME                          = gs_jobsts-jobname
                IMPORTING
                   STATUS                           = g_f_status
*            HAS_CHILD                        =
*          EXCEPTIONS
*            JOB_DOESNT_EXIST                 = 1
*            UNKNOWN_ERROR                    = 2
*            PARENT_CHILD_INCONSISTENCY       = 3
*            OTHERS                           = 4
               g_f_mid = gs_jobsts-spname.
               IF g_f_status = 'F'.
                 IMPORT gt_final FROM MEMORY ID g_f_mid .
                 FREE MEMORY ID gs_jobsts-spname.
                 APPEND LINES OF gt_final to gt_final1.
                 REFRESH gt_prlist.
                 CALL FUNCTION 'JOB_CLOSE'
                   EXPORTING
                     jobcount             = g_f_jobcount
                     jobname              = g_f_jobname
                     strtimmed            = g_flg_start
                   EXCEPTIONS
                     cant_start_immediate = 1
                     invalid_startdate    = 2
                     jobname_missing      = 3
                     job_close_failed     = 4
                     job_nosteps          = 5
                     job_notex            = 6
                     lock_failed          = 7
                     OTHERS               = 8.
                 IF sy-subrc = 0.
                   g_f_flg = 'X'.
                   gs_jobsts1-jobcount = g_f_jobcount.
                   gs_jobsts1-jobname = g_f_jobname.
                   gs_jobsts1-spname   = g_f_spname.
                   APPEND gs_jobsts1 TO gt_jobsts.
                   DELETE TABLE gt_jobsts FROM gs_jobsts.
                   EXIT.
                 ENDIF.
               ENDIF.
             ENDLOOP.
             IF g_f_flg = 'X'.
               CLEAR g_f_flg.
               EXIT.
             ENDIF.
           ENDDO.
         ENDIF.
       ENDIF.
       IF sy-subrc <> 0.
         MESSAGE e539(scpr) WITH g_f_jobname.
       ENDIF.
       COMMIT WORK .
     ENDDO.

Memory Limitation on EXPORT & IMPORT Internal Tables?

Hi All,
I have a need to export and import the internal tables to memory. I do not want to export it to any data base tables. is there a limitation on the amount of memroy that is can be used for the EXPORT & IMPORT. I will free the memory once I import it. The maximum I expect would be 13,000,000 lines.
Thanks,
Alex (Arthur Samson)

You don't have limitations, but try to keep your table as small as possible.
Otherwise, if you are familiar with the ABAP OO context, try use Shared Objects instead of IMPORT/EXPORT.
<a href="http://help.sap.com/saphelp_erp2004/helpdata/en/13/dc853f11ed0617e10000000a114084/frameset.htm">SAP Help On Shared Objects</a>
Hope this helps,
Roby.

Problem in Importing Internal Table

Dear All,
I am exporting Internal table from Program1 as follows:
REPORT ZEXPORT_TEST                            .
TYPES: BEGIN OF ITAB,
      MATNR TYPE MARA-MATNR,
      MATKL TYPE MARA-MATKL,
      END OF ITAB.
DATA:IT TYPE TABLE OF ITAB .
SELECT MATNR MATKL FROM MARA INTO TABLE IT UP TO 10 ROWS.
EXPORT IT TO MEMORY ID 'EAI1'.
WRITE:/'Exported Successfully'.
And I am Importing same internal table into program2
REPORT ZIMPORT_TEST .
TYPES: BEGIN OF ITAB,
      MATNR TYPE MARA-MATNR,
      MATKL TYPE MARA-MATKL,
      END OF ITAB.
DATA:IT TYPE TABLE OF ITAB,
     IT1 TYPE TABLE OF ITAB,
     WA TYPE ITAB.
IMPORT IT1 FROM MEMORY ID 'EAI1'.
IT[] = IT1[].
LOOP AT IT INTO WA.
WRITE:/ wa-matnr,
        / WA-MATKL.
ENDLOOP.
WRITE:/'Imported Successfully'.
But progam1 exporting correctly the return code is 0 but program2 is not importing sucessfully return code is 4.
Kindly help me to import.
Thanks in Advance.

Hi friend,
When u use 'Export' and 'Import' statements, it refers local sap memory.
So u need to use SUBMIT ZIMPORT_TEST AND RETURN statement immediately after 'Export'.
i.e.
Report ZEXPORT_TEST.
EXPORT IT TO MEMORY ID 'EAI1'.   < -
Exported to common local sap memory
SUBMIT ZIMPORT_TEST AND RETURN . <---- Controls goes to next program, within same session.
Report ZIMPORT_TEST.
IMPORT IT from MEMORY ID 'EAI1'. <----
Imports data from common local sap memory.
If u want to run two independent reports one exporting, another importing, then u have to use
'SET' and 'GET' parameter concept which refers global sap memory.
Thanks..
Edited by: Sap Fan on Feb 27, 2009 4:56 AM
Edited by: Sap Fan on Feb 27, 2009 4:56 AM

Importing internal table from one program to another program

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.

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 struc

Importing internal table from diffrent program

HI experts,
i have two ALV report zprograms . My requirements is i have to write a report in that report i want to pass input screen parameters to each report and get their final intarnal table without generating ALV. How is it possible.
my question is i want to call any program and export values of thier screen parameter and get the final internal table as export.
Pls Help. THanks in advace
Ajay Kuamr

Hello Ajay,
In each of the report you can EXPORT the internal table contents to SAP memory & IMPORT the table contents in the third program.
You have to use SUBMIT statements for each report & get back the internal table using IMPORT statements.
For further details explore SDN.
BR,
Suhas

Importing internal table data from FM to eCATT test script

Hi all,
I am working on Workflow project where by i need to post invoices related to purchase orders sent as scanned imaages. Incase all the data in the incoming invoice(scanned) is correct then i am using BAPI_INCOMING_INVOICE_CREATE to post the invoice.
But when the data is wrong, i need to give the user MIRO transaction pre-populated with the invoice details so that he manually corrects them(after verification) and posts the invoice.
I understand MIRO is an ENJOY transaction hence BDC doesn't work properly(i have tried with all kinds of options on recording and the problem comes incase of multiple POs) hence i choose to use eCATT.
The recording worksfine but my real problem is the PO data (multiple PO details for same invoice) is in table form. In all my previous objects related to eCATT we used to upload the file, hence no problem of importing tables.
But now as i'll call this test script from a function module which has all the POs in the form of internal table, i need to import this into my test script.
Please any body tell me how to proceed in this case or please suggest me a better a way to record the MIRO.
Thank you,
Lakshmi Narayana.S

Hello Raj,
First of all thank you for your inputs.
Yes, I know about Parking an invoice. even i am using it in some scenarios.
If everything on the invoice matches with the values in SAP then i am posting it using BAPI invoice_create also.
But for some scenarios like if the PO on the invoice doesnot match with actual PO then i need to create a work item in the Accounts Payable user's inbox and he will change invoice data manually (after getting confirmation and correction) and post it using MIRO.
Here i need to pre-populate the MIRO with the invoice data so that he can correct and post it.
Hence i was trying to write a BDC and as MIRO is an Enjoy transaction i thought writing a BDC is not a good idea (i tried writing BDC but had problems) hence i am using eCATT.
Hope i am clear about my problem. Any inputs to solve this are welcome.
Thanks,
Lakshmi Narayana.S

Import   internal table problem

Hi..
I have 2 programs with me.
In the first program my code is like this
REPORT Y_TEST1.
DATA:
BEGIN OF FS_DATA,
    NUMBER   TYPE I,
    NAME(30) TYPE C,
END OF FS_DATA.
DATA:
T_DATA LIKE STANDARD TABLE OF FS_DATA.
DEFINE APPEND_TABLE.
FS_DATA-NUMBER = &1.
FS_DATA-NAME = &2.
APPEND FS_DATA TO T_DATA.
CLEAR FS_DATA.
END-OF-DEFINITION.
APPEND_TABLE 1 'HARISH'.
APPEND_TABLE 2 'MAHESH'.
APPEND_TABLE 3 'SURESH'.
APPEND_TABLE 4 'WAJID'.
APPEND_TABLE 5 'SANKAR'.
APPEND_TABLE 6 'SATISH'.
APPEND_TABLE 7 'CHANDU'.
APPEND_TABLE 8 'VEERESH'.
EXPORT T_DATA TO MEMORY ID 'NAM'.
SUBMIT Y_TEST1_CALLED.
And my Second Program code is ..
REPORT Y_TEST1_CALLED.
DATA:
    FS_DATA(30).
DATA:
T_DATA LIKE STANDARD TABLE OF FS_DATA.
IMPORT T_DATA FROM MEMORY ID 'NAM' . ******ERROR
LOOP AT T_DATA INTO FS_DATA.
WRITE: / FS_DATA.
ENDLOOP.
These are the programs that i have here in
second Prog i am getting Shortdump as Types mis match ..
but according to my requirement i need to get the data into itab t_data without changing structure of the internal tables ,
here I need to use any of options in IMPORT
{ { { {[ACCEPTING PADDING] [ACCEPTING TRUNCATION]}
        | [IGNORING STRUCTURE BOUNDARIES] }
        [IGNORING CONVERSION ERRORS [REPLACEMENT CHARACTER rc]] }
    | [IN CHAR-TO-HEX MODE] }
    [CODEPAGE INTO cp]
    [ENDIAN INTO endian].
what i need to use and how ......
i think correct option is IGNORING CONVERSION ERRORS but it is giving syntax error ..can any one send me the proper code and my system is ECC 5.

Hi Pasupulati,
Please try it in this way. I have already done it in my one requirement.
Hi,
Please use it in this way,
*& First Prog----
data: char4(4) type c.
EXPORT char4 TO MEMORY ID 'ZOT'.
*& Other Prog---
Data: char4(4) type c.
IMPORT char4 FROM MEMORY ID 'ZOT'.
Once you get the output.
Then Free the Memory
syntax is:
Free memory id 'ZOT'.

Import internal table from query to report

Hi,
I have to import an internal table% G00 with its contents from a query in a custom report. I use the import statement but I do not acknowledgment the table. You can help me.
thanks

Hi,
standard program behind the query does not have any EXPORT statement statement behind it so it does not make sense to IMPORT. It'll never IMPORT.
You can use the following way:
    SUBMIT (report_name) USING SELECTION-SCREEN <sel_screen_number> EXPORTING LIST TO MEMORY AND RETURN.
and then use
CALL FUNCTION 'LIST_FROM_MEMORY'
    TABLES
      listobject = list_tab
    EXCEPTIONS
      not_found = 1
      OTHERS     = 2.
IF sy-subrc = 0 AND list_tab IS NOT INITIAL.
   CALL FUNCTION 'LIST_FREE_MEMORY'.
      CALL FUNCTION 'LIST_TO_ASCI'
        TABLES LISTOBJECT = list_tab
                      LISTASCI   = output.
     FREE MEMORY ID '%_LIST'.
ENDIF.
output is your output table.

Import internal table in submit program via job

Hi,
I'm submitting in a backgroudn job a program wich does a CALL TRANSACTION, this program submited reads ITBDC table importing table from memory ID 'itbdc' but this is empty, why in background job processing it can´t read data from memory because It seems it reads from another place or it's not reading anything!
Thanks!!

REPORT report2.
DATA: text       TYPE c LENGTH 10,
      rspar_tab TYPE TABLE OF rsparams,
      rspar_line LIKE LINE OF rspar_tab,
      range_tab LIKE RANGE OF text,
      range_line LIKE LINE OF range_tab.
rspar_line-selname = 'SELCRIT1'.
rspar_line-kind    = 'S'.
rspar_line-sign    = 'I'.
rspar_line-option = 'EQ'.
rspar_line-low     = 'ABAP'.
APPEND rspar_line TO rspar_tab.
range_line-sign   = 'E'.
range_line-option = 'EQ'.
range_line-low    = 'H'.
APPEND range_line TO range_tab.
range_line-sign   = 'E'.
range_line-option = 'EQ'.
range_line-low    = 'K'.
APPEND range_line TO range_tab.
SUBMIT report1 USING SELECTION-SCREEN '1100'
               WITH SELECTION-TABLE rspar_tab
               WITH selcrit2 BETWEEN 'H' AND 'K'
               WITH selcrit2 IN range_tab
               AND RETURN.

Internal table export and import in ECC 5.0 version

Hi friends,
I am trying to export and import internal table from one program to other program.
The below export and import commands are not working when I run the program in background (using SUBMIT zxxxx via JOB name NUMBER number..)
EXPORT ITAB TO MEMORY id 'ZMATERIAL_CREATE'.
IMPORT ItAB FROM MEMORY ID 'ZMATERIAL_CREATE'.
Normally it should work. Since Its not working I am trying with another alternative..
i.e EXPORT (ptab) INTERNAL TABLE itab.
My sap version is ECC 5.0.
For your information, here I am forwarding sap help. Pls have a look and explain how to declare ptab internal table.
+Extract from SAP help+
In the dynamic case the parameter list is specified in an index table ptab with two columns. These columns can have any name and have to be of the type "character". In the first column of ptab, you have to specify the names of the parameters and in the second column the data objects. If the second column is initial, then the name of the parameter in the first column has to match the name of a data object. The data object is then stored under its name in the cluster. If the first column of ptab is initial, an uncatchable exception will be raised.
Outside of classes you can also use a single-column internal table for parameter_list for the dynamic form. In doing so, all data objects are implicitly stored under their name in the data cluster.
My internal table having around 45 columns.
pls help me.
Thanks in advance
raghunath

The export/import should work the way you are using it. Just make sure you are using same memory id and make sure its unique - meaning u are using it only for this itab purpose and not overwriting it with other values. Check itab is not initial before you export in program 1 - then import it in prog2 with same memory id...also check case, I am not sure if its case sensitive...
Here is how you use the second variant...
Two fields with two different identifications "P1" and "P2" with the dynamic variant of the cluster definition are written to the ABAP Memory. After execution of the statement IMPORT, the contents of the fields text1 and text2 are interchanged.
TYPES:
BEGIN OF tab_type,
    para TYPE string,
    dobj TYPE string,
END OF tab_type.
DATA:
id    TYPE c LENGTH 10 VALUE 'TEXTS',
text1 TYPE string VALUE `IKE`,
text2 TYPE string VALUE `TINA`,
line TYPE tab_type,
itab TYPE STANDARD TABLE OF tab_type.
line-para = 'P1'.
line-dobj = 'TEXT1'.
APPEND line TO itab.
line-para = 'P2'.
line-dobj = 'TEXT2'.
APPEND line TO itab.
EXPORT (itab)     TO MEMORY ID id.
IMPORT p1 = text2
       p2 = text1 FROM MEMORY ID id.

How do we Use Internal table in Global Memory ?

Hi All ,
Can anyone help me with how to create and use an internal table in SAP global memory ?
Regards,
Ranjita

Hi,
Try with GET PARAMETER AND SET PARAMETER
Refer the below link,
Export Import Internal tables across two z programs
Regards,
Vijay

IMPORT Statement Issue (Internal Table)

Hi All,
I am using an IMPORT statement to get all the data from other report's internal table. Now whenever this (the other report's internal table) is changed (for field addition, etc), my report throws a dump. Hence, everytime I have to add these fields in my program as well.
Is there any way by which I can include the whole internal table of that report in my program just like
'INCLUDE STRUCTURE VBRK'.
Thanks in advance

Hi, CHeck this code related to your problem..This will helpful to you...
I have done this program earlier..I hope it will helpful to u..
This programa calling the other program to import the data..
Check it out...
*" Tables declarations.................................................
TABLES:
spfli.
*" Type declarations...................................................
Type declaration of the structure to hold data from table SPFLI     *
TYPES:
BEGIN OF type_s_spfli,
    carrid LIKE spfli-carrid,          " Carrier Id
    connid LIKE spfli-connid,          " Connection Number
    cityfrom LIKE spfli-cityfrom,      " City from
    cityto LIKE spfli-cityto,          " City to
    airpfrom LIKE spfli-airpfrom,      " Airport from
    airpto LIKE spfli-airpto,          " Airport to
    countryfr LIKE spfli-countryfr,    " Country from
    countryto LIKE spfli-countryto,    " Country to
END OF type_s_spfli.
Data Declaration...................................................*
     Field String To Hold Flight Details Record from SPFLI          *
DATA
fs_spfli TYPE type_s_spfli.
Data Declaration...................................................*
     Internal Table To Hold Flight Details Records from SPFLI       *
DATA
t_spfli LIKE STANDARD TABLE OF fs_spfli.
TYPES:
BEGIN OF types_s_itab,
    carrid LIKE sflight-carrid,        " Carrier id
    connid LIKE sflight-connid,        " Connection number
    fldate LIKE sflight-fldate,        " Flight date
END OF types_s_itab.
Data Declaration...................................................*
     Field String To Hold Flight Details Record from SFLIGHT        *
DATA
fs_itab TYPE types_s_itab.
Data Declaration...................................................*
     Internal Table To Hold Flight Details Records from SFLIGHT     *
DATA
t_itab LIKE STANDARD TABLE OF fs_itab.
*" Type declarations...................................................
Type declaration of the structure to hold data from table SBOOK     *
TYPES:
BEGIN OF type_s_sbook,
   carrid LIKE sbook-carrid,           " Carrier Id
   connid LIKE sbook-connid,           " Connection Number
   fldate LIKE sbook-fldate,           " Flight date
   bookid LIKE sbook-bookid,           " Booking number
   loccuram LIKE sbook-loccuram,       " Local currency
   loccurkey LIKE sbook-loccurkey,
   order_date LIKE sbook-order_date,   " Booking date
END OF type_s_sbook.
Data Declaration...................................................*
     Field String To Hold Flight Details Record from BOOK           *
DATA
fs_sbook TYPE type_s_sbook.
Data Declaration...................................................*
     Internal Table To Hold Flight Details Records from SBOOK       *
DATA
t_sbook LIKE STANDARD TABLE OF fs_sbook.
DATA
w_checkbox.                          " Checkbox
SELECT-OPTIONS:
s_carr FOR spfli-carrid.             " Carrier id range
                      START-OF-SELECTION EVENT                      *
START-OF-SELECTION.
PERFORM selectq.
                      END-OF-SELECTION EVENT                        *
END-OF-SELECTION.
SET PF-STATUS 'YH1314_030502'.
PERFORM display_basic.
AT USER-COMMAND.
PERFORM ucomm.
*&    Form selectq
    This subroutine retreive data from SPFLI table
There are no interface parameters to be passed to this subroutine.
FORM selectq .
SELECT carrid                        " Carrier id
         connid                        " Connection number
         cityfrom                      " City from
         cityto                        " City to
         airpfrom                      " Airport from
         airpto                        " Airport to
         countryfr                     " Country from
         countryto                     " Country to
         INTO CORRESPONDING FIELDS OF TABLE t_spfli
         FROM spfli
         WHERE carrid IN s_carr.
ENDFORM.                               " Selectq
*&      Form display_basic
    This subroutine displays data from internal table
There are no interface parameters to be passed to this subroutine.
FORM display_basic .
LOOP AT t_spfli INTO fs_spfli.
    WRITE:
      / w_checkbox AS CHECKBOX,
        fs_spfli-carrid,
        fs_spfli-connid,
        fs_spfli-cityfrom,
        fs_spfli-cityto,
        fs_spfli-airpfrom,
        fs_spfli-airpto,
        fs_spfli-countryfr,
        fs_spfli-countryto.
ENDLOOP.                             " LOOP AT T-SPFLI INTO...
ENDFORM.                               " Display_basic
*&      Form UCOMM
This subroutine for at user-command event
There are no interface parameters to be passed to this subroutine.
FORM ucomm .
RANGES :
    r_carr FOR spfli-carrid,
    r_conn FOR spfli-connid,
    r_carrid FOR sflight-carrid,
    r_connid FOR sflight-connid,
    r_fldate FOR sflight-fldate.
CASE sy-ucomm.
    WHEN 'DISPLAY'.
      DATA:
        lw_lines TYPE i,
        lw_lineno TYPE i VALUE 3.
      DESCRIBE TABLE t_spfli LINES lw_lines.
      DO lw_lines TIMES.
        READ LINE lw_lineno FIELD
             VALUE w_checkbox   INTO w_checkbox
                   fs_spfli-carrid INTO fs_spfli-carrid
                   fs_spfli-connid INTO fs_spfli-connid.
        IF sy-subrc = 0.
          IF w_checkbox = 'X'.
            r_carr-sign = 'I'.
            r_carr-option = 'EQ'.
            r_carr-low = fs_spfli-carrid.
            APPEND r_carr.
            r_conn-sign = 'I'.
            r_conn-option = 'EQ'.
            r_conn-low = fs_spfli-connid.
            APPEND r_conn.
          ENDIF.                       " IF W_CHECKBOX = 'X'
        ENDIF.                         " IF SY-SUBRC = 0
        ADD 1 TO lw_lineno.
      ENDDO.                           " DO LW_LINES TIMES
      SUBMIT yh1314_030502_call
        WITH s_carr IN r_carr
        WITH s_conn IN r_conn
         AND RETURN.
      IMPORT t_itab FROM MEMORY ID 'YH1314'.
      LOOP AT t_itab INTO fs_itab.
        r_carrid-sign = 'I'.
        r_carrid-option = 'EQ'.
        r_carrid-low = fs_itab-carrid.
        APPEND r_carrid.
        r_connid-sign = 'I'.
        r_connid-option = 'EQ'.
        r_connid-low = fs_itab-connid.
        APPEND r_connid.
        r_fldate-sign = 'I'.
        r_fldate-option = 'EQ'.
        r_fldate-low = fs_itab-fldate.
        APPEND r_fldate.
      ENDLOOP.                         " LOOP AT T_ITAB INTO.....
      SELECT carrid                    " Carriee Id
             connid                    " Connection number
             fldate                    " Flight date
             bookid                    " Booking number
             loccuram                  " Local Currency
             order_date                " Booking date
         INTO CORRESPONDING FIELDS OF TABLE t_sbook
         FROM sbook
         WHERE carrid IN r_carrid AND
               connid IN r_connid AND
               fldate IN r_fldate.
      IF SY-SUBRC NE 0.
        MESSAGE 'NO RECORDS FOUND'(006) TYPE 'S'.
      ENDIF.                           " IF SY-SUBRC NE 0
      LOOP AT t_sbook INTO fs_sbook.
        AT FIRST.
          WRITE: /5 'Carrier Id'(001),
                 20 'Conn Id'(002),
                 35 'Flight date'(003),
                 50 'Book Id'(004),
                 65 'Local Currency'(005).
        ENDAT.                         " AT FIRST
        WRITE: /5 fs_sbook-carrid,
               20 fs_sbook-connid,
               35 fs_sbook-fldate,
               50 fs_sbook-bookid,
               65 fs_sbook-loccuram CURRENCY fs_sbook-loccurkey.
      ENDLOOP.                         " LOOP AT T_SBOOK INTO.....
ENDCASE.                             " CASE SY-UCOMM
ENDFORM.                               " UCOMM
Regards
Kiran

Import Internal Table

Similar Messages

Maybe you are looking for