<?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: general in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355090#M520258</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;&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 (see below).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;ABAP Memory&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&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. For further information&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Padmam.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Jun 2007 09:48:49 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-06-04T09:48:49Z</dc:date>
    <item>
      <title>general</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355087#M520255</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is sap memory and abap memory&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Jun 2007 09:28:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355087#M520255</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-04T09:28:34Z</dc:date>
    </item>
    <item>
      <title>Re: general</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355088#M520256</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;Memory Structures of an ABAP Program &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the Overview of the R/3 Basis System you have seen that each user can open up to six R/3 windows in a single SAPgui session. Each of these windows corresponds to a session on the application server with its own area of shared memory. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The first application program that you start in a session opens an internal session within the main session. The internal session has a memory area that contains the ABAP program and its associated data. When the program calls external routines (methods, subroutines or function modules) their main program and working data are also loaded into the memory area of the internal session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Only one internal session is ever active. If the active application program calls a further application program, the system opens another internal session. Here, there are two possible cases: If the second program does not return control to the calling program when it has finished running, the called program replaces the calling program in the internal session. The contents of the memory of the calling program are deleted. If the second program does return control to the calling program when it has finished running, the session of the called program is not deleted. Instead, it becomes inactive, and its memory contents are placed on a stack. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The memory area of each session contains an area called ABAP memory. ABAP memory is available to all internal sessions. ABAP programs can use the EXPORT and IMPORT statements to access it. 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;All ABAP programs can also access the SAP memory. This is a memory area to which all 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 are often used to preassign values to input fields. You can set them individually for users, or globally according to the flow of an application program. SAP memory is the only connection between the different sessions within a SAPgui.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Omkar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Jun 2007 09:34:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355088#M520256</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-04T09:34:03Z</dc:date>
    </item>
    <item>
      <title>Re: general</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355089#M520257</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: is a global memory ,it mean its is USER logon specific and Transaction specific.&lt;/P&gt;&lt;P&gt;Parameters for SAP memory are Set parameter id , get parameter id, SPA, GPA .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP memory: is local memory, &lt;/P&gt;&lt;P&gt;paremeters for abap memory are import &amp;amp; export.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Revert back if any issues.&lt;/P&gt;&lt;P&gt;Reward with points if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naveen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Jun 2007 09:36:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355089#M520257</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-04T09:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: general</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355090#M520258</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;&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 (see below).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;ABAP Memory&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&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. For further information&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Padmam.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Jun 2007 09:48:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355090#M520258</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-04T09:48:49Z</dc:date>
    </item>
    <item>
      <title>Re: general</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355091#M520259</link>
      <description>&lt;P&gt;Hi Manjula,&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 &lt;/P&gt;&lt;P&gt;within a SAPgui have access. You can use SAP memory either &lt;/P&gt;&lt;P&gt;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.  Application &lt;/P&gt;&lt;P&gt;programs that use SAP memory must do so using SPA/GPA &lt;/P&gt;&lt;P&gt;parameters (also known as SET/GET parameters). These &lt;/P&gt;&lt;P&gt;parameters can be set either for a particular user or for a &lt;/P&gt;&lt;P&gt;particular program using the SET PARAMETER statement. Other &lt;/P&gt;&lt;P&gt;ABAP programs can then retrieve the set parameters using &lt;/P&gt;&lt;P&gt;the GET PARAMETER statement. The most frequent use of &lt;/P&gt;&lt;P&gt;SPA/GPA parameters is to fill input fields on screens &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;ABAP memory is a memory area that all ABAP programs within &lt;/P&gt;&lt;P&gt;the same internal session can access using the EXPORT and &lt;/P&gt;&lt;P&gt;IMPORT statements. Data within this area remains intact &lt;/P&gt;&lt;P&gt;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 &lt;/P&gt;&lt;P&gt;placed in ABAP memory before the call is made. The internal &lt;/P&gt;&lt;P&gt;session of the called program then replaces that of the &lt;/P&gt;&lt;P&gt;calling program. The program called can then read from the &lt;/P&gt;&lt;P&gt;ABAP memory. If control is then returned to the program &lt;/P&gt;&lt;P&gt;which made the initial call, the same process operates in &lt;/P&gt;&lt;P&gt;reverse. &lt;/P&gt;&lt;P&gt;Difference between SAP memory and ABAP memory.&lt;/P&gt;&lt;P&gt;[Removed by the moderator.]&lt;/P&gt;&lt;P&gt;Hope it helps you.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Regards,&lt;/P&gt;&lt;P&gt;Jackie..&amp;lt;/b&amp;gt;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jun 2007 10:33:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355091#M520259</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-04T10:33:12Z</dc:date>
    </item>
    <item>
      <title>Re: general</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355092#M520260</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;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&lt;/P&gt;&lt;P&gt;access using the EXPORT and IMPORT statements. Data within this area remains intact during&lt;/P&gt;&lt;P&gt;a whole sequence of program calls. To pass data to a program which you are calling, the data&lt;/P&gt;&lt;P&gt;needs to be placed in ABAP memory before the call is made. The internal session of the called&lt;/P&gt;&lt;P&gt;program then replaces that of the calling program. The program called can then read from the&lt;/P&gt;&lt;P&gt;ABAP memory. If control is then returned to the program which made the initial call, the same&lt;/P&gt;&lt;P&gt;process operates in reverse. For further information, refer to Data Clusters in ABAP Memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP Memory is a memory area in the internal session (roll area) of an ABAP program. Data&lt;/P&gt;&lt;P&gt;within this area is retained within a sequence of program calls, allowing you to pass data&lt;/P&gt;&lt;P&gt;between programs that call one another. It is also possible to pass data between sessions&lt;/P&gt;&lt;P&gt;using SAP Memory.&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&lt;/P&gt;&lt;P&gt;can use SAP memory either to pass data from one program to another within a session, or to&lt;/P&gt;&lt;P&gt;pass data from one session to another. Application programs that use SAP memory must do so&lt;/P&gt;&lt;P&gt;using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a memory area to which all sessions within a SAPgui have access. You can use SAP&lt;/P&gt;&lt;P&gt;memory either to pass data from one program to another within a session (as with ABAP&lt;/P&gt;&lt;P&gt;memory) or to pass data from one session to another.&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, 04 Jun 2007 10:47:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/general/m-p/2355092#M520260</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-04T10:47:58Z</dc:date>
    </item>
  </channel>
</rss>

