Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata
ABAP MEMORY-It uses export and import parameters when an active internal session 
calls another internal session within a single main session .
SAP MEMORY- It uses set and get parameters to pass the data from one main session to another main session. 

 

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

External session: - when user logs on to R/3 system, the system Creates a new terminal session called external session. E.g. System Session.

Internal session: - created by calling a transaction (with CALL TRANSACTION), a dialog module (with CALL DIALOG) or a report (with SUBMIT or RETURN).

In general 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.

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.

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.

 

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.

 

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.

 

******************ABAP MEMORY - with export and import parameters****************
REPORT  YSP_0136.
 
data : name1(10) type c value 'aaaaaaaaaa'. export name1 to memory id 'MEM1'. SUBMIT YSP_0137 AND RETURN. WRITE 'SSSSSSSS'.
********************************************************
REPORT  YSP_0137                                                    .
DATA : NAME2(10) TYPE C. IMPORT NAME1 TO NAME2 FROM MEMORY ID 'MEM1'. WRITE NAME2.
 
***********ABAP MEMORY - with export and import parameters****************
REPORT ZPGM1.
data : text1 type char20 value 'export and import'.

export text1
       text2 from 'ex and im' to memory id 'MEM'.

SUBMIT ZPGM2 AND RETURN.
REPORT ZPGM2.
DATA : T1 TYPE CHAR20.
DATA : T2 TYPE CHAR20.
IMPORT TEXT1 TO T1 FROM MEMORY ID 'MEM'.
IMPORT TEXT2 TO T2 FROM MEMORY ID 'MEM'.
WRITE :/ T1.
WRITE :/ T2.

****************************OUTPUT **************
export and import
ex and im 
 
************ABAP MEMORY - with export and import parameters**************
data : t1 type char15 value  'ex and im'.

export t1 to memory id 'mem'.
t1 = 'xxxxxxxxxx'.
write :/ sy-subrc , t1.
import t1 from memory id 'mem'. " or free memory.
write :/ sy-subrc , t1.
t1 = 'xxxxxxxxxx'.
free memory id 'mem'.
import t1 from memory id 'mem'.
write :/ sy-subrc , t1.

*************output of program ****************

   0  xxxxxxxxxx
   0  ex and im
   4  xxxxxxxxxx
***************ABAP MEMORY - with export and import parameters ****************
data : text(10) value '0123456789',
       iden(3) value 'xyz'.

export text to memory id iden.

text = 'xxxxxxxxxx'.

import text from memory id iden.
write :/ sy-subrc, text.

free memory . " free memory id iden.
text = 'xxxxxxxxxx'.
import text from memory id iden.
write :/ sy-subrc, text.
******************SAP MEMORY - with set and get parameters******************* 
REPORT  YSP_0138                                .

DATA TEXT1(30) TYPE C VALUE 'SET AND GET PARAMETER'.
SET PARAMETER ID 'MEM' FIELD TEXT1.

WRITE : 'SET PARAMETER'.
*************************************************
REPORT  YSP_0139                                .
DATA TEXT2(30) TYPE C .
GET PARAMETER ID 'MEM' FIELD TEXT2.
WRITE : / TEXT2.
WRITE : 'GET PARAMETER'. 
  • No labels