Exporting an internal table to memory

Hi
I want to call an program from another program and want the values stored in an internal table used in the called program.
how can i export an internal table to memory id an then import it.
Regards
Arun

So to be clear, for your requirement it would be:
* Towards the end of the called program
EXPORT it_itab TO MEMORY ID 'ZZ_MEM_ID'.
* And then from calling program after the submit zzzz and return statement
IMPORT it_itab FROM MEMORY ID 'ZZ_MEM_ID'.
Hope that helps.
Brad
Message was edited by: Brad Williams (put back intro text)
Message was edited by: Brad Williams

Similar Messages

Export internal table to memory in User Exit FM

Hi all,
My scenario here is to export an internal table in one user exit FM and import it back in another user exit FM.
I was trying to use
Export lt_table to memory id 'LABEL'.
then
Import lt_table from memory id 'LABEL'.
But then i hit error in the import statement. How can I rectify this?
Thanks. Answer will be rewarded.

Refer to the below related threads
Export an internal table to memory and import from memory into an internal
http://help.sap.com/saphelp_erp2005/helpdata/en/fc/eb3bf8358411d1829f0000e829fbfe/frameset.htm
Regards,
Santosh

Import & Export of Internal table

Hello All,
In my requirement I need to call the MB5B program RM07MLBD. I used the code like this.
SUBMIT rm07mlbd AND RETURN
            WITH matnr   IN so_matnr
            WITH werks   IN so_werks
            WITH datum   IN so_budat.
Now from the RM07MLBD program I need the get the values of the table * g_t_totals_flat * to my zprogram.
Is it possible to import & export the Internal table from one program to other.
Regards,
Anil.

Hi,
You can export the internal table ot memory id and can access the (Import) in the called program.
Consider this small code from ABAPDOCU.
DATA text1(10) TYPE c VALUE 'Exporting'.
DATA: itab TYPE TABLE OF sbook,
      wa_itab LIKE LINE OF itab.
DO 5 TIMES.
wa_itab-bookid = 100 + sy-index.
APPEND wa_itab TO itab.
ENDDO.
EXPORT text1
       text2 = 'Literal'
TO MEMORY ID 'text'.
EXPORT itab
TO MEMORY ID 'table'.
Regards
Bikas

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.

Exporting internal table to memory variable

I need to extract some data within a program into an internal table. Then I need to export the internal table into a memory variable
Then in another program i need to import this memory variable into another internal table
How to do the import export into a memory variable

See the simple example :
REPORT ZTEST_AMEM1.
tables : lfa1.
data : begin of i_lfa1 occurs 0 ,
       lifnr like lfa1-lifnr,
       name1 like lfa1-name1,
       land1 like lfa1-land1,
       end of i_lfa1.
start-of-selection.
select lifnr
       name1
       land1 from lfa1
       into table i_lfa1 up to 100 rows.
Export
export i_lfa1 to memory id 'SAP'.
submit ztest_amem2 and return.
write:/ 'hello'.
*& Report ZTEST_AMEM2
REPORT ZTEST_AMEM2.
data : begin of j_lfa1 occurs 0,
       lifnr like lfa1-lifnr,
       name1 like lfa1-name1,
       land1 like lfa1-land1,
       end of j_lfa1.
start-of-selection.
import i_lfa1 to j_lfa1 from memory id 'SAP'.
loop at j_lfa1.
write:/ j_lfa1-lifnr,j_lfa1-name1,j_lfa1-land1.
endloop.

Problem in exporting internal table to memory

Hi,
I have to export two internal tables (thead and titem) from a report (RFTBCF00) to memory which i will import in my function module can anyone letme know hw it cud b done .
Points will b assigned
Thnx,

You can take the help of this example:
report z_82235_test1                           .
types: begin of tab1,
         a(1),
         b(1),
       end of tab1.
types: begin of tab2,
         c(1),
         d(1),
       end of tab2.
data: itab1 type table of tab1,
      wa1 like line of itab1,
      itab2 type table of tab2,
      wa2 like line of itab2.
wa1-a = '1'.
wa1-b = '2'.
append wa1 to itab1.
clear wa1.
wa1-a = '3'.
wa1-b = '4'.
append wa1 to itab1.
clear wa1.
export itab1 to memory id '001'.
export itab2 to memory id '002'.
submit z_82235_test2 and return exporting list to memory .

Export internal table to memory.

How can I export and import an internal table to memory?
This:
export messtab to memory id 'TAB'. (in program 1)
import messtab=messtab from memory id 'TAB'. (in program 2)
does not work.

Even without the brackets it doesn't work.
In program 1 I have:
    WRITE text-e21 TO messtab-message.
    messtab-type = c_tipo_error.
    APPEND messtab. CLEAR messtab.
    DELETE messtab WHERE message = space.
    EXPORT messtab[] TO MEMORY ID para.
    EXIT.
The EXIT leads to program 2, from where I made a submit to program 1, and where I have:
import messtab[] from memory id para.
Where:
        DATA: para TYPE tpara-paramid VALUE 'MES',
        messtab TYPE TABLE OF bapireturn WITH HEADER LINE.
What's wrong?
Thanks in advance.
Oh, and I've checked the table in program 1 does have an entry.

Save Internal table to memory - problem

Hi everybody ,
I need to extract one Internal table to memory , every 1st in the Month .
Then every day I will be reading this table for my report ( in order to avoid running every day same and same database selections) .
My originall idea wos with EXPORT TO MEMORY ID , AND IMPORT
but it does'nt work next day ... With Export data is cept only untill tthe end of the transaction ...
Is there any way except of storing data in one Z_ database table ???
Thanks in advance

Hi,
You can use the following code to export to memory
*data variable required for background processing
data: wa_indx type indx.
*EXPORT Internal Table TO MEMORY ID 'XYZ'.
*part for background processing
export tab = <your table> to database indx(xy) from wa_indx client
sy-mandt id 'XYZ'.
the following code will import from Memory and clear memory
*data variable required for background processing
data: wa_indx type indx.
imports from database the list sent by the calling program
IMPORT tab = <your table> FROM DATABASE indx(xy) TO wa_indx CLIENT sy-mandt
ID 'XYZ'.
deletes the data to save wastage of memory
DELETE FROM DATABASE indx(xy)
CLIENT sy-mandt
ID 'XYZ'.
Regards,
Samson Rodrigues.

Pass Internal Table to Memory

Dear Experts.
I have the following problem.
I am using a User-Exit for Travel that is called from a program standard with use the T.Code TRIP. The program standard use a structure that when entry in the user exit not is. I need use this structure in the user exit. (p_t_req_head).
I had read abour SAP and ABAP Memory but from the program standar How can Pass Internal Table to Memory SAP or ABAP from the program standard to user-exit?
When I am doing debugging in the program Standard and this call to the user exit, I use ()namestructure for example ()p_t_req_head and I get the datas of the structure, But In the Source Code ABAP, How can do this with instructions?
Regards

Hi,
You try with Import & Export Statements as follows ---
DATA : t_itab LIKE TABLE OF spfli.
EXPORT t_itab TO MEMORY ID 'ABCD'.
After sending the internal table to ABAP memory you need to get that by IMPORT in the called session.
IMPORT t_itab FROM MEMORY ID 'ABCD'.

Passing Dynamic Internal Tables to Memory

I have a bit of a conundrum right now that I can't seem to correct. I am working on adding an ALV report to an existing report program. I was able to write a simple helper program that builds a custom object that I defined that translates my raw data into two seperate dynamic tables, and then builds an ALV grid and outputs it. The reason I wrote this in a simple helper program was so that I could use SUBMIT ... EXPORTING LIST TO MEMORY from my primary report program and capture the input so I can later write it out under our company's standard ABAP list format as if I were using WRITE statements.
The output of the report itself is working beautifully. We have included functionality to automatically take the output, produce an HTML file from it, and then FTP it directly to a webserver so our clients can get easy access to it. What I want to be able to do though is give the clients two tab-delimited files that contain the raw data that was used to build the report. We have an interface in place to do that, but I somehow need to be able to pass these two dynamic internal tables which I have field-symbols to reference back to my calling program.
Here is what I am trying to do:
CALL METHOD OBJ_ALV_MR_EST_REASONS->PRODUCE_ESTIMATION_REPORT
    IMPORTING
      RPT_DATA_BY_REASON   = ref_it_estreason
      RPT_DATA_BY_DISTRICT = ref_it_district.
*   Assign the field symbols
ASSIGN ref_it_estreason->* TO <it_estreason>.
ASSIGN ref_it_district->* TO <it_district>.
* Export the two internal tables to memory so they can be
* retrieved by the calling program
EXPORT reason = <it_estreason>[]
         district = <it_district>[]
TO MEMORY ID 'ZCR_ESTIMATION_REASON_RPT'.
As you can see, my method returns two references to dynamic internal tables. I have used the memory debugger to see that these tables are being correctly written to the ABAP memory.
However, back in my parent program when I try to do the following,
CREATE DATA ref_it_estreason TYPE REF TO DATA.
      CREATE DATA ref_it_district TYPE REF TO DATA.
      ASSIGN ref_it_estreason->* TO <it_estreason>.
      ASSIGN ref_it_district->* TO <it_district>.
      IMPORT reason = <it_estreason>
             district = <it_district>
      FROM MEMORY ID 'ZCR_ESTIMATION_REASON_RPT'.
I get the REFS_NOT_SUPPORTED_YET exception which says that "For the statement Export/Import ..." object references, interface references, and data references are currently not supported".
I have tried multiple other ways of defining my field-symbols or my reference pointers but they all result in exceptions of some sort. Is there any way for me to get this data passed back? It seems like there must be a way to get the data from memory since I know it's being correctly stored there.
Thanks in advance.

Shortly after posting this, I had an idea which I was able to implement to actually get this to work.
I decided that I would simply pass the FIELDCAT tables for each of my dynamic tables into the same memory ID as the tables themselves.
EXPORT reason_fcat = it_estreason_fcat
         district_fcat = it_district_fcat
         reason = <it_estreason>[]
         district = <it_district>[]
TO MEMORY ID 'ZCR_ESTIMATION_REASON_RPT'.
Then, back in my calling program I execute the following code. This retrieves the FIELDCAT tables, builds two empty dynamic table type reference variables and then lets me create field-symbols to reference those components.
*     Retrieve the fieldcat internal tables first
      IMPORT reason_fcat = it_estreason_fcat
             district_fcat = it_district_fcat
      FROM MEMORY ID 'ZCR_ESTIMATION_REASON_RPT'.
*     Generate an internal table type assigned to each
*     reference variable based on the fieldcat listings we
*     retrieve
      CALL METHOD cl_alv_table_create=>create_dynamic_table
        EXPORTING
          it_fieldcatalog = it_estreason_fcat
        IMPORTING
          ep_table        = ref_it_estreason.
      CALL METHOD cl_alv_table_create=>create_dynamic_table
        EXPORTING
          it_fieldcatalog = it_district_fcat
        IMPORTING
          ep_table        = ref_it_district.
*     Assign the field symbols
      ASSIGN ref_it_estreason->* TO <it_estreason>.
      ASSIGN ref_it_district->* TO <it_district>.
      CREATE DATA ref_wa_estreason LIKE LINE OF <it_estreason>.
      CREATE DATA ref_wa_district LIKE LINE OF <it_district>.
      ASSIGN ref_wa_estreason->* TO <wa_estreason>.
      ASSIGN ref_wa_district->* TO <wa_district>.
*     Finally, we can retrieve the data from memory and assign
*     to the internal tables referenced by our field-symbols
      IMPORT reason = <it_estreason>[]
             district = <it_district>[]
      FROM MEMORY ID 'ZCR_ESTIMATION_REASON_RPT'.
This worked beautifully and saved me from having to do a major redesign. I don't know how helpful it would be for ABAP Objects to be passed to memory (I believe some type of serialization would need to be in order there), but for dynamically typed internal tables it worked like a dream with little overhead.

It cannot reference the dynamic internal table in memory as an object.

Hi,
I am getting the syntax error in the second select. I guest it cannot reference the dynamic internal table in memory as an object.
The internal table contains different fields from multiple tables and it gets created OK. Then the first select within the loop executes OK allowing me to read the multiple tables in ITABLES.
* Create dynamic internal table and assign to FS
call method cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog = ifc
    IMPORTING
      ep_table        = dy_table.
***OK, the dynamic tables is created here
assign dy_table->* to <dyn_table>.
* Create dynamic work area and assign to FS
create data dy_line like line of <dyn_table>.
assign dy_line->* to <dyn_wa>.
loop at ITABLES.
***OK, no syntax errors in this select here
select * appending corresponding fields of table <dyn_table>
             from (ITABLES-TABNAME).
endloop.
data: ikonp like konp occurs 0 with header line.
***NOT OK, there is syntax errors
select * into table ikonp
from KONP for all entries in <dyn_table>
where knumh = <dyn_table>-knumh.
Some of the tables in ITABLES are pooled tables which does not allow me to use INNER JOINS. Therefore I need a second select in order to read the pricing table KONP.
Thanks in advance for any hint.

Hi Abel,
You must be getting the syntax error that <dyn_table> does not contain the field knumh.
try putiing the entire where clause in a char type variable say wa_char and then use in ur query as
where (wa_char) .. it may work..
concatenate 'knumh' '=' '<dyn_table>-knumh' INTO wa_char SEPARATED BY SPACES.
SELECT ... from konp...
where (wa_char).
Revert if it doesnt work.

Problem while exporting internal table to memory id using EXPORT

Hi friends,
Iam facing a following problem.
I have 4 line items in my va01 tcode.
now when i give material number and quantity and hit enter the processing for that line item starts.
iam moving that current line item to a internal table lt_vbap in userexit_check_vbap.
now for the 2nd line item also i have to move to internal table lt_vbap.
but my problem is that in internal table lt_vbap iam not getting all the line items.
every time the current line item is being processed the the previous line items are being refreshed.
from lt_vbap internal table.
how can i export internal table.
code
move vbap to lt_vbap.
append lt_vbap.
export lt_vbap to memory id 'ZXYZ'.

>
Prakash Pandey wrote:
> Hi Priyanka,
>
> The internal table lt_vbap will always be empty unless you import it from the Memory ID (in your case ZXYX).
>
> Use the code this way:
>
> IMPORT lt_vbap FROM MEMORY ID 'ZXYX'.
>
> move vbap to lt_vbap.
>
> append lt_vbap.
>
> export lt_vbap to memory id 'ZXYZ'.
>
> Regards,
> Prakash Pandey
The memory id shud be same in both cases

Export to internal table

Hi experts:
    I got problems when I'm using 'export/import to internal table'.When 'import to internal table' exected, an ABAP occured, text 'Format error with IMPORT: No further container found.'
    Part of my codes is below:
    Export:
    data: gi_info type standard table of ZBPS_PASSINFO,
               itab type standard table of ZBPS_PASSINFO,
               gs_info type ZBPS_PASSINFO.
    loop at layout->mt_html_cell assigning <ld_cell> where row = row_id and chanm = 'ZBPS_ZNU'.
              gs_info-num = <ld_cell>-value.
            endloop.
            loop at layout->mt_html_cell assigning <ld_cell> where row = row_id and chanm = 'ZBPS_ZNAM'.
              v_xmmc = <ld_cell>-value.
            endloop.
            loop at layout->mt_html_cell assigning <ld_cell> where row = row_id and chanm = 'ZBPS_ZTZ'.      "
              v_ZTZ = <ld_cell>-value.
            endloop.
            loop at layout->mt_html_cell assigning <ld_cell> where row = row_id and chanm = 'ZBPS_DEP'.      "
              v_DEP = <ld_cell>-value.
            endloop.
            loop at layout->mt_html_cell assigning <ld_cell> where row = row_id and chanm = 'ZBPS_SHRY'.      "
              v_SHRY = <ld_cell>-value.
            endloop.
            gs_info-xmmc = v_xmmc.
            gs_info-ZTZ = v_ZTZ.
            gs_info-DEP = v_DEP.
            gs_info-SHRY = v_SHRY.
            append gs_info to gi_info.
    EXPORT ZPASSINFO FROM gi_info TO INTERNAL TABLE itab.
    Import:
    data: GI_PASSINFO type standard table of ZBPS_PASSINFO,
      itab type standard table of ZBPS_PASSINFO,
      GS_PASSINFO type ZBPS_PASSINFO.
import ZPASSINFO to GI_PASSINFO from INTERNAL TABLE itab.

EXPORT - Export data
Variants
1. EXPORT obj1 ... objn TO MEMORY.
2. EXPORT obj1 ... objn TO DATABASE dbtab(ar) ID key.
3. EXPORT obj1 ... objn TO DATASET dsn(ar) ID key.
Variant 1
EXPORT obj1 ... objn TO MEMORY.
Additions
1. ... FROM g (for each field to be exported)
2. ... ID key
Effect
Exports the objects obj1 ... objn (fields, structures or tables) as a data cluster to ABAP/4 memory .
If you call a transaction, report or dialog module (with CALL TRANSACTION , SUBMIT or CALL DIALOG ), the contents of ABAP/4 memory are retained, even across several levels. The called transaction can then retrieve the data from there using IMPORT ... FROM MEMORY . Each new EXPORT ... TO MEMORY statement overwrites any old data, so no data is appended.
If the processing leaves the deepest level of the call chain, the ABAP/4 memory is released.
Note
The header lines of internal tables cannot be exported, because specifying the name of an internal table with a header line always exports the actual table data.
Addition 1
... FROM g (for each object to be exported)
Effect
Exports the contents of the data object g and stores them under the name specified before FROM .
Addition 2
... ID key
Effect
Stores the exported data under the ID key in ABAP/4 memory . You can then use the ID to read it in again (with IMPORT ). The ID can be up to 32 characters long.
Note
If you store data both with and without an ID , the data stored without an ID remains separate and you can re-import it (using IMPORT without ID ).
Note
Runtime errors
EXPORT_NO_CONTAINER : SAP paging exhausted
Variant 2
EXPORT obj1 ... objn TO DATABASE dbtab(ar) ID key.
Additions
1. ... FROM g (for each field to be exported)
2. ... CLIENT h (after dbtab(ar) )
3. ... USING form
Effect
Exports the objects obj1 ... objn (fields, structures or tables) as a data cluster to the database table dbtab .
The database table dbtab must have a standardized structure .
The database table dbtab is divided into different logically related areas ( ar , 2-character name).
You can export collections of data objects (known as data clusters ) under a freely definable key (field key ) to an area of this database.
IMPORT allows you to import individual data objects from this cluster.
Notes
The table dbtab specified after DATABASE must be declared under TABLES .
The header lines of internal tables cannot be exported because specifying the name of an internal table with a header line always exports the actual table data.
Example
Export two fields and an internal table to the database table INDX :
TABLES INDX.
DATA: INDXKEY LIKE INDX-SRTFD VALUE 'KEYVALUE',
      F1(4), F2 TYPE P,
      BEGIN OF ITAB3 OCCURS 2,
        CONT(4),
      END OF ITAB3.
Before the export, the data fields in
front of CLUSTR are filled.
INDX-AEDAT = SY-DATUM.
INDX-USERA = SY-UNAME.
Export der Daten.
EXPORT F1 F2 ITAB3 TO
       DATABASE INDX(ST) ID INDXKEY.
Addition 1
... FROM g (for each object to be exported)
Effect
Exports the contents of the field g and stores them under the specified name in the database.
Addition 2
... CLIENT h (after dbtab(ar) )
Effect
Stores the data objects in the client h (if the import/export database table dbtab is client-specific).
Addition 3
... USING form
Effect
Does not export the data to the database table. Instead, calls the FORM routine form for every record written to the database without this addition. This routine can take the data from the database table work area and therefore has no parameters.
Note
Runtime errors
Errors in the structure of the EXPORT / IMPORT database can cause runtime errors .
Variant 3
EXPORT obj1 ... objn TO DATASET dsn(ar) ID key.
Note
This variant is not to be used at present.

How to export an internal table to another report while submitting ..

Hi ,
I have 2 reports ZR1 and ZR2 . Both contains an Internal table with same structure IT_DATA. After the output of ZR1 comes,I am submitting ZR2 at a click event. The requirement is to pass the data from IT_DATA from ZR1 to IT_DATA of ZR2 while submitting ZR2.
Hope that the requirement is clear.
Thanks & regards,
Shankar

Hi
You have to use IMPORT/EXPORT statament
REPORT ZREPORT1.
DATA: ITAB LIKE .....
EXPORT ITAB TO MEMORY ID 'ZZZ'.
SUBMIT ZREPORT2.
REPORT ZREPORT2.
DATA ITAB LIKE
INITIALIZATION.
IMPORT ITAB FROM MEMORY ID 'ZZZ'.
Max
Message was edited by: max bianchi

Exceptions passing internal tables to memory...!

code in program 1
DATA :IT_FINAL2 LIKE WA_FINAL OCCURS 10 WITH HEADER LINE.
DATA : I_SORT TYPE SLIS_T_SORTINFO_ALV WITH HEADER LINE.
DATA : I_FCAT   TYPE TABLE OF SLIS_FIELDCAT_ALV WITH NON-UNIQUE
                DEFAULT KEY WITH HEADER LINE INITIAL SIZE 0,
EXPORT (IT_FINAL2[]) TO MEMORY ID 'main'.
EXPORT (I_FCAT[]) TO MEMORY ID 'i_fcat'.
EXPORT (I_SORT) to MEMORY ID 'sort'.
SY-SUBRC IS O FOR THE FIRST EXPORT.
while exporting the other 2 tables the system is throwing exception whose analysis is as follows.
Error analysis
    The table "(itab)" has an illegal row type at position "comp. 1" in statement
     "EXPORT (itab) TO ...".
    The following types are allowed:
    "C, CSTRING"
    However, the field "(itab)" has the type:
    8
    ( Meanings in type description:
      - Values in brackets: Type length in bytes
      - 'DEC'            : Number of decimal places at type P
      At the type description, there is partly only a technical type
      description displayed.)
code in program 2 with same table declaration.
import (I_FCAT_S) FROM MEMORY id 'i_fcat'.
import (CH_ITAB) FROM MEMORY id 'main'.
import (I_SORT_S) FROM MEMORY id 'sort'.
Hey experts plz help me resolve this query .
or suggest a alternative to pass the internal table from one program to another...
Edited by: Anup Deshmukh on Jun 16, 2009 7:22 PM

Hey Anup...just try as Rich had said...firstly remove the brackets....
I tried your codes and it is working fine for me!
DATA :IT_FINAL2 LIKE WA_FINAL OCCURS 10 WITH HEADER LINE.
DATA : I_SORT TYPE SLIS_T_SORTINFO_ALV WITH HEADER LINE.
DATA : I_FCAT   TYPE TABLE OF SLIS_FIELDCAT_ALV WITH NON-UNIQUE
                DEFAULT KEY WITH HEADER LINE INITIAL SIZE 0.
EXPORT it_final2[] TO MEMORY ID 'main'.
EXPORT i_fcat[] TO MEMORY ID 'i_fcat'.
EXPORT i_sort TO MEMORY ID 'sort'.
And while importing use like below:
IMPORT i_fcat[] = i_fcat[]   FROM MEMORY ID 'i_fcat'.
IMPORT it_final2[] = it_final2[]   FROM MEMORY ID 'main'.
IMPORT i_sort = i_sort FROM MEMORY ID 'sort'.
And also remember to FREE the memory ID after importing..

Exporting an internal table to memory

Similar Messages

Maybe you are looking for