<?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: SAP Memory in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-memory/m-p/2411280#M537863</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&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;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;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;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;A href="https://forums.sdn.sap.com/click.jspa?searchID=2274783&amp;amp;messageID=2489768" target="test_blank"&gt;https://forums.sdn.sap.com/click.jspa?searchID=2274783&amp;amp;messageID=2489768&lt;/A&gt;&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;&lt;/P&gt;&lt;P&gt;Reward if useful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ashu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 28 Jun 2007 05:26:41 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-06-28T05:26:41Z</dc:date>
    <item>
      <title>SAP Memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-memory/m-p/2411279#M537862</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi gurus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can any one pl. tell me the difference between SAP-Local Memory and SAP-Global Memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;kiran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jun 2007 05:24:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-memory/m-p/2411279#M537862</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-28T05:24:27Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-memory/m-p/2411280#M537863</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&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;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;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;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;A href="https://forums.sdn.sap.com/click.jspa?searchID=2274783&amp;amp;messageID=2489768" target="test_blank"&gt;https://forums.sdn.sap.com/click.jspa?searchID=2274783&amp;amp;messageID=2489768&lt;/A&gt;&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;&lt;/P&gt;&lt;P&gt;Reward if useful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ashu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jun 2007 05:26:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-memory/m-p/2411280#M537863</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-28T05:26:41Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-memory/m-p/2411281#M537864</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Within a main session, when ever you start an application program, it opens up an internal sessions with in the main session. The internal session has a memory area that contains the ABAP program and its associated data.  So when ever you want to  pass data between two internal sessions, then you can use ABAP Memory (i.e import, export). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When comes to SAP memory (also known as &amp;lt;b&amp;gt;global memory&amp;lt;/b&amp;gt;), if the data has to be passed b/w two main sessions, we can use SAP Memory(SPA/GPA Parameters).  SAP Memory can also be used to pass data b/w internal sessions.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jun 2007 05:27:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-memory/m-p/2411281#M537864</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-28T05:27:02Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-memory/m-p/2411282#M537865</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;kiran,&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;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;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;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;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;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;Don't forget to reward if useful.....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jun 2007 05:27:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-memory/m-p/2411282#M537865</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-28T05:27:14Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-memory/m-p/2411283#M537866</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(GLOBAL) - the data here is accessible globally across all users / sessions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP Memory - Session specific memory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Local memory - Program specific memory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Memmory - use to acess memmory area between session&lt;/P&gt;&lt;P&gt;eg:- when u call a transaction or report ( within ur program) want the value of the prticular field should have value define by U.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then u use GET and SET parameter command&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;field u set or get should have parameter ID&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;Regards,&lt;/P&gt;&lt;P&gt;Priyanka.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jun 2007 05:31:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-memory/m-p/2411283#M537866</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-28T05:31:45Z</dc:date>
    </item>
  </channel>
</rss>

