<?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 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap/m-p/3240986#M773461</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;Check the below link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/9f/db994235c111d1829f0000e829fbfe/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/9f/db994235c111d1829f0000e829fbfe/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Vadi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 03 Jan 2008 05:54:22 GMT</pubDate>
    <dc:creator>i048168</dc:creator>
    <dc:date>2008-01-03T05:54:22Z</dc:date>
    <item>
      <title>abap</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap/m-p/3240983#M773458</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi friends&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) what are the Different types of ABAP memory?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2008 05:50:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap/m-p/3240983#M773458</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-03T05:50:17Z</dc:date>
    </item>
    <item>
      <title>Re: abap</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap/m-p/3240984#M773459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&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;ABAP memory is temporary and values are retained in same LUW.&lt;/P&gt;&lt;P&gt;&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 length.&lt;/P&gt;&lt;P&gt;&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;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;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="4653876"&gt;&lt;/A&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;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;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;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;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;&lt;/P&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 global memory), 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;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;Reward if usful.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Arpit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2008 05:53:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap/m-p/3240984#M773459</guid>
      <dc:creator>arpit_shah</dc:creator>
      <dc:date>2008-01-03T05:53:33Z</dc:date>
    </item>
    <item>
      <title>Re: abap</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap/m-p/3240985#M773460</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;SAP MEMORY is a Global Memory , it can be used across the logons where as the ABAP memory can be used within one logon but diff sections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We use Set/get Paramter ids for SAP Memory where as We use Import &amp;amp; Export for ABAP Memory. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Drawback of SAP memory is that we cant send Internal Table data where as in ABAP memory it is possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Selvapandian Arunachalam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2008 05:54:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap/m-p/3240985#M773460</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-03T05:54:18Z</dc:date>
    </item>
    <item>
      <title>Re: abap</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap/m-p/3240986#M773461</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;Check the below link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/9f/db994235c111d1829f0000e829fbfe/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/9f/db994235c111d1829f0000e829fbfe/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Vadi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2008 05:54:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap/m-p/3240986#M773461</guid>
      <dc:creator>i048168</dc:creator>
      <dc:date>2008-01-03T05:54:22Z</dc:date>
    </item>
    <item>
      <title>Re: abap</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap/m-p/3240987#M773462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SAP memory is simply global memory that can be used from any logon whereas ABAP memory is local memory presented in Application layer for local use.It can used from same logon .&lt;/P&gt;&lt;P&gt;SAP memory accessed by SET and GET parameter whereas IMPORT and EXPORT been used by ABAP Memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Of luck&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 10:30:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap/m-p/3240987#M773462</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-06-12T10:30:07Z</dc:date>
    </item>
  </channel>
</rss>

