Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

ABAP

Former Member
0 Kudos

Hi,

What is the difference between SAP memory & ABAP memory?

1 ACCEPTED SOLUTION

Former Member

Hi

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).

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.

SAP Memory

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

ABAP/4 Memory

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.

SAP memory

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.

ABAP/4 memory

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.

ABAP MEMORY:To transfer the Data between the Programs Running in the Same Session We can use.

Eg:

Calling Report.

REPORT ZREP1.

DATA : ITAB TYPE TABLE OF MARA.

SELECT * FROM MARA INTO TABLE ITAB.

EXPORT TEMPTAB FROM ITAB TO MEMORY ID 'M1'.

SUBMIT ZREP2 AND RETURN.

Called report

REPORT ZREP2.

DATA: IT_MARA TYPE TABLE OF MARA.

DATA WA TYPE MARA.

IMPORT TEMPTAB TO IT_MARA FROM MEMORY ID 'M1'

LOOP AT IT_MARA INTO WA.

WRITE:/ WA-MATNR.

ENDLOOP.

SAP Menory:

It is used to pass the Data to Screen fields or Read data from Screen Fields.

It can be used to Transfer data from one Session(window) to another within the Login.

DATA : V_KUNNR TYPE KNA1-KUNNR VALUE 1000.

SET PARAMETER ID 'KUN' FIELD V_KUNNR.

CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.

Regards

Ravish

Reward if useful

7 REPLIES 7

Former Member

Hi

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).

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.

SAP Memory

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

ABAP/4 Memory

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.

SAP memory

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.

ABAP/4 memory

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.

ABAP MEMORY:To transfer the Data between the Programs Running in the Same Session We can use.

Eg:

Calling Report.

REPORT ZREP1.

DATA : ITAB TYPE TABLE OF MARA.

SELECT * FROM MARA INTO TABLE ITAB.

EXPORT TEMPTAB FROM ITAB TO MEMORY ID 'M1'.

SUBMIT ZREP2 AND RETURN.

Called report

REPORT ZREP2.

DATA: IT_MARA TYPE TABLE OF MARA.

DATA WA TYPE MARA.

IMPORT TEMPTAB TO IT_MARA FROM MEMORY ID 'M1'

LOOP AT IT_MARA INTO WA.

WRITE:/ WA-MATNR.

ENDLOOP.

SAP Menory:

It is used to pass the Data to Screen fields or Read data from Screen Fields.

It can be used to Transfer data from one Session(window) to another within the Login.

DATA : V_KUNNR TYPE KNA1-KUNNR VALUE 1000.

SET PARAMETER ID 'KUN' FIELD V_KUNNR.

CALL TRANSACTION 'XD03' AND SKIP FIRST SCREEN.

Regards

Ravish

Reward if useful

0 Kudos

Hi,

SAP Memory is to share the data between External Sessions.

ABAP memory is to share data between Internal Sessions.

Data saved in SAP Memory stays till the user log-off.

Data saved in ABAP memory is lost when the transaction is closed, that is with the end of all the internal sessions involved in transaction.

Regards,

Sesh

Former Member
0 Kudos

hi,

SAP Memory

SAP memory is the memory area where all main sessions with in the SAP GUI have the access. We can use SAP memory either

to pass data from one program to other within the session, or to pass data from one session to other. 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

ABAP/4 Memory

ABAP memory is the 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.

SAP memory

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.

ABAP/4 memory

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.

Former Member
0 Kudos

<b>SAP Memory</b>

SAP memory is the memory area where all main sessions within the SAP GUI have the access. We can use SAP memory either to pass data from one program to other within the session, or to pass data from one session to other. 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.

<b>ABAP/4 Memory</b>

ABAP memory is the 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 that 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 that made the initial call, the same process operates in reverse.

<b>SAP memory </b>

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.

<b>ABAP/4 memory </b>

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.

regards,

srinivas

<b>*reward for useful answers*</b>

Former Member
0 Kudos

<b>SAP Memory</b>

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).

<b>ABAP Memory</b>

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, refer to Data Clusters in ABAP Memory,

Also please check this links for more information.

<b>SAP Memory</b>

http://help.sap.com/saphelp_47x200/helpdata/en/fc/eb3bf8358411d1829f0000e829fbfe/content.htm

<b>ABAP Memory</b>

http://help.sap.com/saphelp_47x200/helpdata/en/fc/eb3bc4358411d1829f0000e829fbfe/content.htm

Regards

Gokul

former_member673201
Discoverer
0 Kudos

SAP memory is user specific. The data store in SAP memory have access any session fro terminal. ABAP Memory is user and Transaction specific. the data store in ABAP memory have access only one session. If we are creating another session so you can not use ABAP memory.

0 Kudos

SAP memory and ABAP memory

SAP memory is global memory where we can pass the values or data across main sessions i.e SAP memory is accessible not only by programs that are running under the same main session but also across different main sessions.

where as ABAP memory is local memory in which data can be pass across local or internal sessions i.e ABAP memory is kind of limited and can only be accessed within one main internal session, Other programs which are running outside the particular session will not be able to read or write to the memory.

GET PARAMETER and SET PARAMETER statements are used in SAP memory where as IMPORT from memory and EXPORT to memory statements are used n ABAP memory.

Regards,

Varun