<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ABAP memory SAP memory in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844002#M666185</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP MEMORY:To transfer the Data between the Programs Running in the Same Session We can use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eg:&lt;/P&gt;&lt;P&gt;Calling Report.&lt;/P&gt;&lt;P&gt;REPORT ZREP1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA : ITAB TYPE TABLE OF MARA.&lt;/P&gt;&lt;P&gt;SELECT * FROM MARA INTO TABLE ITAB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXPORT TEMPTAB FROM ITAB TO MEMORY ID 'M1'.&lt;/P&gt;&lt;P&gt;SUBMIT ZREP2 AND RETURN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Called report&lt;/P&gt;&lt;P&gt;REPORT ZREP2. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: IT_MARA TYPE TABLE OF MARA.&lt;/P&gt;&lt;P&gt;DATA WA TYPE MARA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMPORT TEMPTAB TO IT_MARA FROM MEMORY ID 'M1'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT IT_MARA INTO WA.&lt;/P&gt;&lt;P&gt;WRITE:/ WA-MATNR.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Memory:&lt;/P&gt;&lt;P&gt;It is used to pass the Data to Screen fields or Read data from Screen Fields.&lt;/P&gt;&lt;P&gt;It can be used to Transfer data from one Session(window) to another within the Login.&lt;/P&gt;&lt;P&gt;DATA : V_KUNNR TYPE KNA1-KUNNR VALUE 1000. &lt;/P&gt;&lt;P&gt;SET PARAMETER ID 'KUN' FIELD V_KUNNR.&lt;/P&gt;&lt;P&gt;CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;REWARD IF HELPFUL.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Oct 2007 11:19:18 GMT</pubDate>
    <dc:creator>varma_narayana</dc:creator>
    <dc:date>2007-10-01T11:19:18Z</dc:date>
    <item>
      <title>ABAP memory SAP memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844000#M666183</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is ABAP memory and explain me the total procedure &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is SAP memory and explain me the total procedure &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what is the diff b/w these two&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2007 11:15:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844000#M666183</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-01T11:15:57Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP memory SAP memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844001#M666184</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Memory &lt;/P&gt;&lt;P&gt;SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another.  Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP/4 Memory &lt;/P&gt;&lt;P&gt;ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data &lt;/P&gt;&lt;P&gt;to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP memory  &lt;/P&gt;&lt;P&gt;The SAP memory, otherwise known as the global memory, is available to a user during the entire duration of a terminal session. Its contents are retained across transaction boundaries as well as external and internal sessions. The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP/4 memory  &lt;/P&gt;&lt;P&gt;The contents of the ABAP/4 memory are retained only during the lifetime of an external session (see also Organization of Modularization Units). You can retain or pass data across internal sessions. The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt; Sudheer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2007 11:18:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844001#M666184</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-01T11:18:13Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP memory SAP memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844002#M666185</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP MEMORY:To transfer the Data between the Programs Running in the Same Session We can use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eg:&lt;/P&gt;&lt;P&gt;Calling Report.&lt;/P&gt;&lt;P&gt;REPORT ZREP1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA : ITAB TYPE TABLE OF MARA.&lt;/P&gt;&lt;P&gt;SELECT * FROM MARA INTO TABLE ITAB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXPORT TEMPTAB FROM ITAB TO MEMORY ID 'M1'.&lt;/P&gt;&lt;P&gt;SUBMIT ZREP2 AND RETURN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Called report&lt;/P&gt;&lt;P&gt;REPORT ZREP2. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: IT_MARA TYPE TABLE OF MARA.&lt;/P&gt;&lt;P&gt;DATA WA TYPE MARA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMPORT TEMPTAB TO IT_MARA FROM MEMORY ID 'M1'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT IT_MARA INTO WA.&lt;/P&gt;&lt;P&gt;WRITE:/ WA-MATNR.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Memory:&lt;/P&gt;&lt;P&gt;It is used to pass the Data to Screen fields or Read data from Screen Fields.&lt;/P&gt;&lt;P&gt;It can be used to Transfer data from one Session(window) to another within the Login.&lt;/P&gt;&lt;P&gt;DATA : V_KUNNR TYPE KNA1-KUNNR VALUE 1000. &lt;/P&gt;&lt;P&gt;SET PARAMETER ID 'KUN' FIELD V_KUNNR.&lt;/P&gt;&lt;P&gt;CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;REWARD IF HELPFUL.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2007 11:19:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844002#M666185</guid>
      <dc:creator>varma_narayana</dc:creator>
      <dc:date>2007-10-01T11:19:18Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP memory SAP memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844003#M666186</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A simple example of ABAP memory is using the EXPORT/IMPORT statements.&lt;/P&gt;&lt;P&gt;Here in this program, I get the data, export it to memory,&lt;/P&gt;&lt;P&gt;clear out the internal table in my progam, then reimport the data into it and write out the data. &lt;/P&gt;&lt;P&gt;You probably wounldn't do this in a normal program,&lt;/P&gt;&lt;P&gt;but this is how you can pass data from program a to program b when A Submits program B.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;report zxy_0002 .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data: it001 type table of t001 with header line.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;select * into table it001 from t001.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;export it001 = it001 to memory id 'ZXY_TEST'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;clear it001. refresh it001.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;import it001 = it001 from memory id 'ZXY_TEST'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;loop at it001.&lt;/P&gt;&lt;P&gt;write:/ it001-bukrs, it001-butxt.&lt;/P&gt;&lt;P&gt;endloop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Memory &lt;/P&gt;&lt;P&gt;SAP memory is a memory area to which all main sessions within a SAPgui have access. &lt;/P&gt;&lt;P&gt;You can use SAP memory either to pass data from one program to another within a session, &lt;/P&gt;&lt;P&gt;or to pass data from one session to another. &lt;/P&gt;&lt;P&gt;Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters).&lt;/P&gt;&lt;P&gt;These parameters can be set either for a particular user &lt;/P&gt;&lt;P&gt;or for a particular program using the SET PARAMETER statement. &lt;/P&gt;&lt;P&gt;Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. &lt;/P&gt;&lt;P&gt;The most frequent use of SPA/GPA parameters is to fill input fields on screens &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP/4 Memory &lt;/P&gt;&lt;P&gt;ABAP memory is a memory area that all ABAP programs within the same internal session can access &lt;/P&gt;&lt;P&gt;using the EXPORT and IMPORT statements.&lt;/P&gt;&lt;P&gt;Data within this area remains intact during a whole sequence of program calls. To pass data &lt;/P&gt;&lt;P&gt;to a program which you are calling,&lt;/P&gt;&lt;P&gt;the data needs to be placed in ABAP memory before the call is made.&lt;/P&gt;&lt;P&gt;The internal session of the called program then replaces that of the calling program. &lt;/P&gt;&lt;P&gt;The program called can then read from the ABAP memory. &lt;/P&gt;&lt;P&gt;If control is then returned to the program which made the initial call, the same process operates in reverse. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP memory &lt;/P&gt;&lt;P&gt;The SAP memory, otherwise known as the global memory, &lt;/P&gt;&lt;P&gt;is available to a user during the entire duration of a terminal session. &lt;/P&gt;&lt;P&gt;Its contents are retained across transaction boundaries as well as external and internal sessions. &lt;/P&gt;&lt;P&gt;The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP/4 memory &lt;/P&gt;&lt;P&gt;The contents of the ABAP/4 memory are retained only during the lifetime of an external session &lt;/P&gt;&lt;P&gt;(see also Organization of Modularization Units).&lt;/P&gt;&lt;P&gt;You can retain or pass data across internal sessions.&lt;/P&gt;&lt;P&gt;The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory. &lt;/P&gt;&lt;P&gt;*************&lt;/P&gt;&lt;P&gt;SAP global memomy retains field value through out &lt;/P&gt;&lt;P&gt;session. &lt;/P&gt;&lt;P&gt;set parameter id 'MAT' field v_matnr.&lt;/P&gt;&lt;P&gt;get parameter id 'MAT' field v_matnr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;they are stored in table TPARA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP memory is temporary and values are retained&lt;/P&gt;&lt;P&gt;in same LUW.&lt;/P&gt;&lt;P&gt;export itab to memory id 'TeST'.&lt;/P&gt;&lt;P&gt;import itab from memory Id 'TEST'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here itab should be declared of same type and &lt;/P&gt;&lt;P&gt;length. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;progaram A&lt;/P&gt;&lt;P&gt;export itab to memory id 'TeST'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;program B&lt;/P&gt;&lt;P&gt;import itab from memory Id 'TEST'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;value of itab is not retained in program b since&lt;/P&gt;&lt;P&gt;they are not in same LUW.&lt;/P&gt;&lt;P&gt;program A&lt;/P&gt;&lt;P&gt;export itab to memory id 'TeST'.&lt;/P&gt;&lt;P&gt;SUBMIT rep and return &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;program B&lt;/P&gt;&lt;P&gt;import itab from memory Id 'TEST'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;value of itab are retained in program b since&lt;/P&gt;&lt;P&gt;they are in same LUW.&lt;/P&gt;&lt;P&gt;**********&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;vasu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2007 11:19:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844003#M666186</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-01T11:19:21Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP memory SAP memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844004#M666187</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naresh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Memory:&lt;/P&gt;&lt;P&gt;SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another.  Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP/4 Memory:&lt;/P&gt;&lt;P&gt;ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data &lt;/P&gt;&lt;P&gt;to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Archana&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2007 11:20:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844004#M666187</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-01T11:20:51Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP memory SAP memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844005#M666188</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;b&amp;gt;SAP Memory&amp;lt;/b&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement.&lt;/P&gt;&lt;P&gt;Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;b&amp;gt;ABAP Memory&amp;lt;/b&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bhaskar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2007 11:21:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844005#M666188</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-01T11:21:35Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP memory SAP memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844006#M666189</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A simple example of ABAP memory is using the EXPORT/IMPORT statements.&lt;/P&gt;&lt;P&gt;Here in this program, I get the data, export it to memory,&lt;/P&gt;&lt;P&gt;clear out the internal table in my progam, then reimport the data into it and write out the data.&lt;/P&gt;&lt;P&gt;You probably wounldn't do this in a normal program,&lt;/P&gt;&lt;P&gt;but this is how you can pass data from program a to program b when A Submits program B.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;report zxy_0002 .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data: it001 type table of t001 with header line.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;select * into table it001 from t001.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;export it001 = it001 to memory id 'ZXY_TEST'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;clear it001. refresh it001.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;import it001 = it001 from memory id 'ZXY_TEST'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;loop at it001.&lt;/P&gt;&lt;P&gt;write:/ it001-bukrs, it001-butxt.&lt;/P&gt;&lt;P&gt;endloop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Memory&lt;/P&gt;&lt;P&gt;SAP memory is a memory area to which all main sessions within a SAPgui have access.&lt;/P&gt;&lt;P&gt;You can use SAP memory either to pass data from one program to another within a session,&lt;/P&gt;&lt;P&gt;or to pass data from one session to another.&lt;/P&gt;&lt;P&gt;Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters).&lt;/P&gt;&lt;P&gt;These parameters can be set either for a particular user&lt;/P&gt;&lt;P&gt;or for a particular program using the SET PARAMETER statement.&lt;/P&gt;&lt;P&gt;Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement.&lt;/P&gt;&lt;P&gt;The most frequent use of SPA/GPA parameters is to fill input fields on screens&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP/4 Memory&lt;/P&gt;&lt;P&gt;ABAP memory is a memory area that all ABAP programs within the same internal session can access&lt;/P&gt;&lt;P&gt;using the EXPORT and IMPORT statements.&lt;/P&gt;&lt;P&gt;Data within this area remains intact during a whole sequence of program calls. To pass data&lt;/P&gt;&lt;P&gt;to a program which you are calling,&lt;/P&gt;&lt;P&gt;the data needs to be placed in ABAP memory before the call is made.&lt;/P&gt;&lt;P&gt;The internal session of the called program then replaces that of the calling program.&lt;/P&gt;&lt;P&gt;The program called can then read from the ABAP memory.&lt;/P&gt;&lt;P&gt;If control is then returned to the program which made the initial call, the same process operates in reverse.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP memory&lt;/P&gt;&lt;P&gt;The SAP memory, otherwise known as the global memory,&lt;/P&gt;&lt;P&gt;is available to a user during the entire duration of a terminal session.&lt;/P&gt;&lt;P&gt;Its contents are retained across transaction boundaries as well as external and internal sessions.&lt;/P&gt;&lt;P&gt;The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP/4 memory&lt;/P&gt;&lt;P&gt;The contents of the ABAP/4 memory are retained only during the lifetime of an external session&lt;/P&gt;&lt;P&gt;(see also Organization of Modularization Units).&lt;/P&gt;&lt;P&gt;You can retain or pass data across internal sessions.&lt;/P&gt;&lt;P&gt;The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP Memmory &amp;amp; SAP Memmory&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm" target="test_blank"&gt;http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm" target="test_blank"&gt;http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.geocities.com/SiliconValley/Campus/6345/set_para.htm" target="test_blank"&gt;http://www.geocities.com/SiliconValley/Campus/6345/set_para.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GET&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.geocities.com/SiliconValley/Campus/6345/get_para.htm" target="test_blank"&gt;http://www.geocities.com/SiliconValley/Campus/6345/get_para.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXPORT&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.geocities.com/SiliconValley/Campus/6345/export01.htm" target="test_blank"&gt;http://www.geocities.com/SiliconValley/Campus/6345/export01.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other Imp Help&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.geocities.com/SiliconValley/Campus/6345/abapindx.htm" target="test_blank"&gt;http://www.geocities.com/SiliconValley/Campus/6345/abapindx.htm&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Siva&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;note :this is taken from SDN.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2007 11:21:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844006#M666189</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-01T11:21:39Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP memory SAP memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844007#M666190</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;SAP Memory&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another.  Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&lt;/P&gt;&lt;P&gt;ABAP/4 Memory&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data&lt;/P&gt;&lt;P&gt;to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;SAP memory &amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;The SAP memory, otherwise known as the global memory, is available to a user during the entire duration of a terminal session. Its contents are retained across transaction boundaries as well as external and internal sessions. The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;ABAP/4 memory &amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;The contents of the ABAP/4 memory are retained only during the lifetime of an external session (see also Organization of Modularization Units). You can retain or pass data across internal sessions. The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This code is from which program you want to export to the ABAP memory:          &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   export ist_resb to memory id 'ZPPC0122_FD'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;             where ist_resb is the internal table name &amp;amp;&lt;/P&gt;&lt;P&gt;                   ZPPC0122_FD is the include name of my program ZPPC0122.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This code is from which program you want to import from the ABAP memory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        import *ist_resb *= ist_resb from memory id 'ZPPC0122_FD'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;              where  &lt;STRONG&gt;ist_resb This internal table is the importing program internal table.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;                    ist_resb This internal table is the exporting program internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But remember in both the program you have defined the same internal table with same structure &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2007 11:23:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844007#M666190</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-01T11:23:38Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP memory SAP memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844008#M666191</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi N Naresh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The programs in the internal session can access with EXPORT TO MEMORY and IMPORT FROM MEMORY. To transfer datato a called program, it can be placed in the ABAP MEMORY with the EXPORT statement before the program is called. The internal session of the called program then replaces the internal session of the calling program and the data can be read from the ABAP MEMORY with the IMPORT statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The SAP MEMORY is a memory area to which all sessions of a SAP logon have common access. In ABAP programs, the SET PARAMETER and GET PARAMETER commands can be used to access the SPA/GPA paramters stored in the SAP MEMORY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rayden&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2007 11:24:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-memory-sap-memory/m-p/2844008#M666191</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-01T11:24:35Z</dc:date>
    </item>
  </channel>
</rss>

