08-18-2007 12:35 PM
08-18-2007 1:03 PM
Hi mala,
Before reading this just as friend i want to tell one thing ,
dont mind, before posting any question plz plz plz check whether it is there in forum r not if not then post r y u r wasting ur time for anwers,
sorry if spell anything wrong
A simple example of ABAP memory is using the EXPORT/IMPORT statements.
Here in this program, I get the data, export it to memory,
clear out the internal table in my progam, then reimport the data into it and write out the data.
You probably wounldn't do this in a normal program,
but this is how you can pass data from program a to program b when A Submits program B.
report zxy_0002 .
data: it001 type table of t001 with header line.
select * into table it001 from t001.
export it001 = it001 to memory id 'ZXY_TEST'.
clear it001. refresh it001.
import it001 = it001 from memory id 'ZXY_TEST'.
loop at it001.
write:/ it001-bukrs, it001-butxt.
endloop.
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.
REWARD POINTS IS USEFUL.
THANKS
NAveen khan
08-19-2007 11:23 AM
Hi
Welcome to SDN forum.
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
SAP global memory retains field value through out session.
set parameter id 'MAT' field v_matnr.
get parameter id 'MAT' field v_matnr.
They are stored in table TPARA.
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.
ABAP memory is temporary and values are retained in same LUW.
export itab to memory id 'TEST'.
import itab from memory Id 'TEST'.
Here itab should be declared of same type and length.
http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
ABAP Memmory & SAP Memmory
http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
<b>Reward points for useful Answers</b>
Regards
Anji
08-20-2007 4:22 AM
"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.
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.
reward points if it is usefull ....
Girish
08-20-2007 4:48 AM
Hi,
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 (see below).
ABAP 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. For further information
Regards,
Priyanka.
08-20-2007 5:16 AM
Hi..
ABAP MEMORY:
To transfer the Data between the Programs Running in the Same Session We can use.
Eg:
<b>Calling Report.</b>
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.
<b>
Called report</b>
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.
<b>Reward if Helpful</b>
08-20-2007 8:04 AM
Hi
As the number of sessions opened in SAP is 6 (external sessions).
These sessions can access the SAP memory but not ABAP memory. ABAP memory is the memory where in programme can access the internal sessions of the transaction( One stable state to other).
For the same SET/GET parameters are used to access .(SAP memory)
For accessing ABAP memory EXPORT/IMPORT parameters are used .
Internal sessions can access SAP memory but the vice -versa isnt true Please go through the following links.Advisable is to use ABAP memory.
http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb2d40358411d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/dba6eb35c111d1829f0000e829fbfe/content.htm
Thanks
08-20-2007 11:20 AM
SAP Memory
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.
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 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.
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.
regards,
srinivas
<b>*reward for useful answers*</b>