<?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: difference between sap memory and abap memory in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-sap-memory-and-abap-memory/m-p/3640640#M876735</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;THat's an extract from SAP standard documentation&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;ABAP Memory and SAP Memory&lt;/P&gt;&lt;P&gt;It is often necessary to transfer data between two different programs. However, it&lt;/P&gt;&lt;P&gt;is not always possible to specify this data as an addition in the program call. In&lt;/P&gt;&lt;P&gt;such cases, you can use the SAP memory and the ABAP memory to transfer&lt;/P&gt;&lt;P&gt;data between programs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;#149; SAP memory is a user-specific memory area for storing field values. It is&lt;/P&gt;&lt;P&gt;therefore not that useful for passing data between internal sessions.&lt;/P&gt;&lt;P&gt;Values in SAP memory are retained for the duration of the user session. SAP&lt;/P&gt;&lt;P&gt;memory can be used between external sessions in the same user session. All&lt;/P&gt;&lt;P&gt;external sessions of a user session can access SAP memory.&lt;/P&gt;&lt;P&gt;You can use the contents of SAP memory as default values for screen fields.&lt;/P&gt;&lt;P&gt;&amp;amp;#149; ABAP memory is also user-specific. There is a local ABAP memory for&lt;/P&gt;&lt;P&gt;each external session. You can use it to exchange any ABAP data objects&lt;/P&gt;&lt;P&gt;(fields, structures, internal tables, complex objects) between the internal&lt;/P&gt;&lt;P&gt;sessions in the same external session.&lt;/P&gt;&lt;P&gt;When the user exits an external session (/i in the command field), the&lt;/P&gt;&lt;P&gt;corresponding ABAP memory is automatically initialized or released.&lt;/P&gt;&lt;P&gt;ABAP Memory&lt;/P&gt;&lt;P&gt;The EXPORT ... TO MEMORY statement copies any number of ABAP data&lt;/P&gt;&lt;P&gt;objects with their current values to a data cluster in the ABAP memory. The ID&lt;/P&gt;&lt;P&gt;addition (maximum 60 characters long) enables you to identify different clusters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use a newEXPORT TO MEMORY statement for an existing data cluster, the&lt;/P&gt;&lt;P&gt;new one overwrites the old one. The IMPORT ... FROM MEMORY ID ...&lt;/P&gt;&lt;P&gt;statement allows you to copy data from ABAP memory into the corresponding&lt;/P&gt;&lt;P&gt;fields of your ABAP program.&lt;/P&gt;&lt;P&gt;You can also restrict the selection to a part of the data cluster in the IMPORT&lt;/P&gt;&lt;P&gt;statement. The variables into which you want to read data from the cluster in&lt;/P&gt;&lt;P&gt;ABAP memory must have the same types in both the exporting and the importing&lt;/P&gt;&lt;P&gt;programs.&lt;/P&gt;&lt;P&gt;You use the FREE MEMORY ID ... statement to release a data cluster&lt;/P&gt;&lt;P&gt;explicitly.&lt;/P&gt;&lt;P&gt;Caution: When you call programs using transaction codes, you can only&lt;/P&gt;&lt;P&gt;use the ABAP memory to pass data to the transaction in the insert case&lt;/P&gt;&lt;P&gt;(CALL TRANSACTION) .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Memory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can define memory areas (parameters) in SAP memory in various ways:&lt;/P&gt;&lt;P&gt;&amp;amp;#149; By creating input/output fields with reference to the ABAP Dictionary. These&lt;/P&gt;&lt;P&gt;take the parameter names from the data elements to which they refer.&lt;/P&gt;&lt;P&gt;Alternatively, you can enter a name in the attributes of the input/output&lt;/P&gt;&lt;P&gt;fields. Then, you can also choose whether the entries from the field should&lt;/P&gt;&lt;P&gt;be transferred to the parameter (SET), or whether the input field should be&lt;/P&gt;&lt;P&gt;filled with the value from the parameter (GET).&lt;/P&gt;&lt;P&gt;To find out about the names of the parameters assigned to input fields, display&lt;/P&gt;&lt;P&gt;the field help for the field with the (F1) key and choose Technical info.&lt;/P&gt;&lt;P&gt;&amp;amp;#149; You can also fill the memory areas directly with the SET PARAMETER ID&lt;/P&gt;&lt;P&gt;&amp;#146;PAR_ID&amp;#146; FIELD var. statement and read from them with the GET&lt;/P&gt;&lt;P&gt;PARAMETER ID &amp;#146;PAR_ID&amp;#146; FIELD var. statement.&lt;/P&gt;&lt;P&gt;&amp;amp;#149; Finally, you can define parameters in the Object Navigator and the user can&lt;/P&gt;&lt;P&gt;specify user specific default values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 12 Apr 2008 05:19:01 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-04-12T05:19:01Z</dc:date>
    <item>
      <title>difference between sap memory and abap memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-sap-memory-and-abap-memory/m-p/3640636#M876731</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is the difference between sap memory and abap memory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Apr 2008 02:56:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-sap-memory-and-abap-memory/m-p/3640636#M876731</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-12T02:56:41Z</dc:date>
    </item>
    <item>
      <title>Re: difference between sap memory and abap memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-sap-memory-and-abap-memory/m-p/3640637#M876732</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;STRONG&gt;SAP Memory&lt;/STRONG&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;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ABAP/4 Memory&lt;/STRONG&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;&lt;STRONG&gt;SAP memory&lt;/STRONG&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;&lt;STRONG&gt;ABAP/4 memory&lt;/STRONG&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;STRONG&gt;Reward points if useful....&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Apr 2008 02:59:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-sap-memory-and-abap-memory/m-p/3640637#M876732</guid>
      <dc:creator>ak_upadhyay</dc:creator>
      <dc:date>2008-04-12T02:59:05Z</dc:date>
    </item>
    <item>
      <title>Re: difference between sap memory and abap memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-sap-memory-and-abap-memory/m-p/3640638#M876733</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check out this link&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;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Apr 2008 03:37:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-sap-memory-and-abap-memory/m-p/3640638#M876733</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-12T03:37:36Z</dc:date>
    </item>
    <item>
      <title>Re: difference between sap memory and abap memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-sap-memory-and-abap-memory/m-p/3640639#M876734</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;STRONG&gt;SAP Memory&lt;/STRONG&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 &lt;STRONG&gt;SET PARAMETER&lt;/STRONG&gt; statement. Other ABAP programs can then retrieve the set parameters using the &lt;STRONG&gt;GET PARAMETER&lt;/STRONG&gt; 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;&lt;STRONG&gt;ABAP/4 Memory&lt;/STRONG&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 &lt;STRONG&gt;EXPORT and IMPORT statements&lt;/STRONG&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, 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;With Rgds,&lt;/P&gt;&lt;P&gt;S.Barani&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Apr 2008 04:51:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-sap-memory-and-abap-memory/m-p/3640639#M876734</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-12T04:51:12Z</dc:date>
    </item>
    <item>
      <title>Re: difference between sap memory and abap memory</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-sap-memory-and-abap-memory/m-p/3640640#M876735</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;THat's an extract from SAP standard documentation&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;ABAP Memory and SAP Memory&lt;/P&gt;&lt;P&gt;It is often necessary to transfer data between two different programs. However, it&lt;/P&gt;&lt;P&gt;is not always possible to specify this data as an addition in the program call. In&lt;/P&gt;&lt;P&gt;such cases, you can use the SAP memory and the ABAP memory to transfer&lt;/P&gt;&lt;P&gt;data between programs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;#149; SAP memory is a user-specific memory area for storing field values. It is&lt;/P&gt;&lt;P&gt;therefore not that useful for passing data between internal sessions.&lt;/P&gt;&lt;P&gt;Values in SAP memory are retained for the duration of the user session. SAP&lt;/P&gt;&lt;P&gt;memory can be used between external sessions in the same user session. All&lt;/P&gt;&lt;P&gt;external sessions of a user session can access SAP memory.&lt;/P&gt;&lt;P&gt;You can use the contents of SAP memory as default values for screen fields.&lt;/P&gt;&lt;P&gt;&amp;amp;#149; ABAP memory is also user-specific. There is a local ABAP memory for&lt;/P&gt;&lt;P&gt;each external session. You can use it to exchange any ABAP data objects&lt;/P&gt;&lt;P&gt;(fields, structures, internal tables, complex objects) between the internal&lt;/P&gt;&lt;P&gt;sessions in the same external session.&lt;/P&gt;&lt;P&gt;When the user exits an external session (/i in the command field), the&lt;/P&gt;&lt;P&gt;corresponding ABAP memory is automatically initialized or released.&lt;/P&gt;&lt;P&gt;ABAP Memory&lt;/P&gt;&lt;P&gt;The EXPORT ... TO MEMORY statement copies any number of ABAP data&lt;/P&gt;&lt;P&gt;objects with their current values to a data cluster in the ABAP memory. The ID&lt;/P&gt;&lt;P&gt;addition (maximum 60 characters long) enables you to identify different clusters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use a newEXPORT TO MEMORY statement for an existing data cluster, the&lt;/P&gt;&lt;P&gt;new one overwrites the old one. The IMPORT ... FROM MEMORY ID ...&lt;/P&gt;&lt;P&gt;statement allows you to copy data from ABAP memory into the corresponding&lt;/P&gt;&lt;P&gt;fields of your ABAP program.&lt;/P&gt;&lt;P&gt;You can also restrict the selection to a part of the data cluster in the IMPORT&lt;/P&gt;&lt;P&gt;statement. The variables into which you want to read data from the cluster in&lt;/P&gt;&lt;P&gt;ABAP memory must have the same types in both the exporting and the importing&lt;/P&gt;&lt;P&gt;programs.&lt;/P&gt;&lt;P&gt;You use the FREE MEMORY ID ... statement to release a data cluster&lt;/P&gt;&lt;P&gt;explicitly.&lt;/P&gt;&lt;P&gt;Caution: When you call programs using transaction codes, you can only&lt;/P&gt;&lt;P&gt;use the ABAP memory to pass data to the transaction in the insert case&lt;/P&gt;&lt;P&gt;(CALL TRANSACTION) .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP Memory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can define memory areas (parameters) in SAP memory in various ways:&lt;/P&gt;&lt;P&gt;&amp;amp;#149; By creating input/output fields with reference to the ABAP Dictionary. These&lt;/P&gt;&lt;P&gt;take the parameter names from the data elements to which they refer.&lt;/P&gt;&lt;P&gt;Alternatively, you can enter a name in the attributes of the input/output&lt;/P&gt;&lt;P&gt;fields. Then, you can also choose whether the entries from the field should&lt;/P&gt;&lt;P&gt;be transferred to the parameter (SET), or whether the input field should be&lt;/P&gt;&lt;P&gt;filled with the value from the parameter (GET).&lt;/P&gt;&lt;P&gt;To find out about the names of the parameters assigned to input fields, display&lt;/P&gt;&lt;P&gt;the field help for the field with the (F1) key and choose Technical info.&lt;/P&gt;&lt;P&gt;&amp;amp;#149; You can also fill the memory areas directly with the SET PARAMETER ID&lt;/P&gt;&lt;P&gt;&amp;#146;PAR_ID&amp;#146; FIELD var. statement and read from them with the GET&lt;/P&gt;&lt;P&gt;PARAMETER ID &amp;#146;PAR_ID&amp;#146; FIELD var. statement.&lt;/P&gt;&lt;P&gt;&amp;amp;#149; Finally, you can define parameters in the Object Navigator and the user can&lt;/P&gt;&lt;P&gt;specify user specific default values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Apr 2008 05:19:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-sap-memory-and-abap-memory/m-p/3640640#M876735</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-12T05:19:01Z</dc:date>
    </item>
  </channel>
</rss>

