<?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: memory in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/memory/m-p/1760373#M329192</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SAP memory is the global memory which you can share through out the sessions.&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;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;ABAP memory &lt;/P&gt;&lt;P&gt;ABAP memory is a local memory within a session, which is used by a particular program. &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;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;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Dec 2006 08:50:59 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-12-06T08:50:59Z</dc:date>
    <item>
      <title>memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/memory/m-p/1760372#M329191</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hai guru,&lt;/P&gt;&lt;P&gt;wat is diff bet.sapmemory n abap memory&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Dec 2006 08:50:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/memory/m-p/1760372#M329191</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-06T08:50:18Z</dc:date>
    </item>
    <item>
      <title>Re: memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/memory/m-p/1760373#M329192</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SAP memory is the global memory which you can share through out the sessions.&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;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;ABAP memory &lt;/P&gt;&lt;P&gt;ABAP memory is a local memory within a session, which is used by a particular program. &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;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;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Dec 2006 08:50:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/memory/m-p/1760373#M329192</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-06T08:50:59Z</dc:date>
    </item>
    <item>
      <title>Re: memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/memory/m-p/1760374#M329193</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;Welcome to SDN...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check these links&lt;/P&gt;&lt;P&gt;&lt;A href="https://forums.sdn.sap.com/click.jspa?searchID=304698&amp;amp;messageID=2489768" target="test_blank"&gt;https://forums.sdn.sap.com/click.jspa?searchID=304698&amp;amp;messageID=2489768&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://forums.sdn.sap.com/click.jspa?searchID=304698&amp;amp;messageID=2441465" target="test_blank"&gt;https://forums.sdn.sap.com/click.jspa?searchID=304698&amp;amp;messageID=2441465&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://forums.sdn.sap.com/click.jspa?searchID=304698&amp;amp;messageID=2055214" target="test_blank"&gt;https://forums.sdn.sap.com/click.jspa?searchID=304698&amp;amp;messageID=2055214&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://forums.sdn.sap.com/click.jspa?searchID=304698&amp;amp;messageID=1536548" target="test_blank"&gt;https://forums.sdn.sap.com/click.jspa?searchID=304698&amp;amp;messageID=1536548&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Dec 2006 08:52:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/memory/m-p/1760374#M329193</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-06T08:52:47Z</dc:date>
    </item>
  </channel>
</rss>

