Tune sap memory parameter

Hi experts,
How can calculate the value of sap memory parameter if wish u tune.
i have app+db both different servers.
no central instance.
12-12 GB both server.
Please suggest which value set for the sap memory parameter.
REgards,
Vivek

You need to tune SAP and DB parameters for good performance.
830576 Parameter recommendations for Oracle 10g
172747 SAP on HP-UX: OS kernel parameter recommendations
Refer to the document on Memory Management and forums
http://help.sap.com/printdocu/core/print46c/en/data/pdf/BCCSTMM/BCCSTMM.pdf
http://forums.sdn.sap.com/thread.jspa?threadID=1788609
Regards,
Arjun

Similar Messages

SAP Memory, Set and Get parameter

Hi All,
     I am running two programs in background from program1
Eq: Program1 --> Calls 2 programs
                          Program1_01.(First Program)
                          Program2_01(Second Program).
Programs1 schedules Program1_01 and Program1_02 in background. These two programs are interdependent.
Program1_01 extracts data, evaluates and sets the Flag. This Flag is exported to SAP Memory using
Set parameter id 'p_id_flag' field Flag.
Program1_02 checks for Program1_01 is completed in background. If complted gets the Flag value from SAP Memory using "Get paramter id 'p_id_flag' field Flag.
When i checked this is not happning. When saw Flag in Program1_01 is set as Flag = 'X'.
When I came and checked in Program1_02 after Get Parameter statement Falg value is SPACE.
Cn hlp on this?

Hi,
The problem simply lies in fact that pid was provided in lowercase.
Use:
SET PARAMETER ID 'P_ID_FLAG' FIELD flag.
GET PARAMETER ID 'P_ID_FLAG' FIELD flag.
It works fine then.
Note!
Though SAP claims it is mandatory to create pid in TPARA table, in fact this is not required. Each time SET PARAMETER is executed, system checks if data object P_ID_FLAG was defined in SAP memory. If not it will automatically create it for us. But be carefull here. If there is such data object, its value will be overwritten.
As for your last question, your statement (FREE MEMORY ....) is ok.
Regards
Marcin
Edited by: Marcin Pciak on Jan 22, 2009 1:14 PM

Physical Memory Upgrade [SAP, Oracle parameter changes]

Hello Guru,
Good day!
I'm not sure if I'm in the correct forum, please bare with me if I'm not.
We are actually planning to increase our Production [Physical Memory] server from its current size 15360GB including [oracle, SAP & OS] to 44GB memory. Do you have any idea how can we calculate to the most needed SAP / DB parameter should be increase after we allocate the 44GB in preparation for Go-Live. Below are details of my systems [oracle version, kernel, R/3 System, OS version, SAP parameter and DB parameter.
Reason for memory upgrade: will create two client in one system with a different number of users and different plant e.g. America / Canada
======================================================================
SAP R/3 Version: SAP 4.6C
Oracle Version: 10.2.0.4.0
OS Level: AIX 5.3
orapaa> oslevel -g
Fileset                                 Actual Level        Maintenance Level
bos.rte                                 5.3.8.0             5.3.0.0
Physical Memory
Real,MB   15360
======================================================================
kernel release               46D
kernel make variant       46D_EXT
compiled on                  AIX 1 5 0056AA8A4C00
compiled for                  64 BIT
compile time                  Aug 17 2007 10:57:49
update level                  0
patch number                  2337
source id                     0.2337
======================================================================
orapaa> prtconf
System Model: IBM,9117-MMA
Machine Serial Number: 06DDD01
Processor Type: PowerPC_POWER6
Processor Implementation Mode: POWER 6
Processor Version: PV_6_Compat
Number Of Processors: 4
Processor Clock Speed: 4208 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
LPAR Info: 9 SWT_AMR_SADCB335_SAP_HA_PRI
Memory Size: 15360 MB
Good Memory Size: 15360 MB
Platform Firmware level: Not Available
Firmware Version: IBM,EM340_095
Console Login: enable
Auto Restart: true
Full Core: false
======================================================================
Our current used SAP parameter
Profile parameters for SAP buffers     Parameters Name               Value     Unit
Program buffer
                    abap/buffersize               850000     Kb
CUA buffer
                    rsdb/cua/buffersize               10000
Screen buffer
                    zcsa/presentation_buffer_area     20000000 Byte
Generic key table buffer
                    zcsa/table_buffer_area          100000000 Byte
Single record table buffer
                    rtbb/buffer_length               60000
Export/import buffer
                    rsdb/obj/buffersize               40000      kB
Table definition buffer
                    rsdb/ntab/entrycount          30000
Field description buffer
                    rsdb/ntab/ftabsize               60000     kB
Initial record buffer
                    rsdb/ntab/irbdsize               8000     kB
Short nametab (NTAB)
                    rsdb/ntab/sntabsize          3000     kB
Calendar buffer
                    zcsa/calendar_area          500000     Byte
Roll, extended and heap memory     EM/TOTAL_SIZE_MB          6144     MB
                    ztta/roll_area               6500000     Byte
                    ztta/roll_first               1     Byte
                    ztta/short_area               1400000     Byte
                    rdisp/ROLL_SHM               16384     8 kB
                    rdisp/PG_SHM               16384     8 kB
                    rdisp/PG_LOCAL               150     8 kB
                    em/initial_size_MB               4092     MB
                    em/blocksize_KB               4096     kB
                    em/address_space_MB          4092     MB
                    ztta/roll_extension               2000000000     Byte
                    abap/heap_area_dia          2000000000     Byte
                    abap/heap_area_nondia          2000000000     Byte
                    abap/heap_area_total          2000000000     Byte
                    abap/heaplimit               40000000     Byte
                    abap/use_paging               0
======================================================================
Oracle Parameter
Oracle Parameter Name     Value     Unit
SGA_MAX_SIZE          6192     MB
PGA_AGGREGATE_TARGET     400     MB
DB_CACHE_SIZE           0
SHARED_POOL_SIZE     960     MB
LARGE_POOL_SIZE          16     MB
JAVA_POOL_SIZE           32     MB
LOG_BUFFER          14246912
db_block_buffers          655360
Thanks and regards,
Mike

I feel the best way to get the parameters which needs to be adjusted is to go for EarlyWatch Check after increasing the Physical Memory of your SAP system, as we cannot say how and which parameters needs to be checked and changed.. as there is some dependiblity also between the parameters...
All the best !

How to remove a grobal parameter in SAP memory

As known to all, we can use SET/GET PARAMETER to pass parameters among multiple programs.
Now I'm just curious about how to remove a grobal parameter in SAP memory, and how can I get the list of all grobal parameter in SAP memory.
Any idea?

Hi william,
1. how to remove a grobal parameter in SAP memory
Well, i dont think we can REMOVE.
At most, we can RESET it to blank(initial)
2. set parameter id 'BUKRS' FIELD ''.
regards,
amit m.

SAP Memory

hi all,
Please tell me the code for passing a particular flag value to a SAP memory . Then calling the memory at any other location and freeing the memory thereafter.
Also please let me know the code for disabling/enabling a particular screen field .
Thanks ,
Paul

To fill the input fields of a called transaction with data from the calling program, you can use the SPA/GPA technique. SPA/GPA parameters are values that the system stores in the global, user-specific SAP memory. SAP memory allows you to pass values between programs. A user can access the values stored in the SAP memory during one terminal session for all parallel sessions. Each SPA/GPA parameter is identified by a 20-character code. You can maintain them in the Repository Browser in the ABAP Workbench. The values in SPA/GPA parameters are user-specific.
SPA/GPA Parameters as Default Values
The SPA/GPA Parameter Technique is a general procedure for filling the initial screen when a program is called. To use this technique for parameters on selection screens, you must link the parameter to an SPA/GPA parameter from the SAP memory as follows:
PARAMETERS ...... MEMORY ID <pid>......
If you use this addition, the current value of SPA/GPA parameter <pid> from the global user-related SAP memory is assigned to parameter as a default value. Description <pid> can contain a maximum of twenty characters and must not be enclosed in quotation marks.
REPORT DEMO.
PARAMETERS TEST(16) MEMORY ID RID.
ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETER statements.
To fill one, use:
SET PARAMETER ID <pid> FIELD <f>.
This statement saves the contents of field <f> under the ID <pid> in the SAP memory. The code <pid> can be up to 20 characters long. If there was already a value stored under <pid>, this statement overwrites it. If the ID <pid> does not exist, double-click <pid> in the ABAP Editor to create a new parameter object.
To read an SPA/GPA parameter, use:
GET PARAMETER ID <pid> FIELD <f>.
Passing Data Between Programs
There are two ways of passing data to a called program:
Passing Data Using Internal Memory Areas
There are two cross-program memory areas to which ABAP programs have access (refer to the diagram in Memory Structures of an ABAP Program) that you can use to pass data between programs.
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, refer to Data Clusters in ABAP Memory.
Filling Input Fields on an Initial Screen
Most programs that you call from other programs have their own initial screen that the user must fill with values. For an executable program, this is normally the selection screen. The SUBMIT statement has a series of additions that you can use to fill the input fields of the called program:
Filling the Selection Screen of a Called Program
You cannot fill the input fields of a screen using additions in the calling statement. Instead, you can use SPA/GPA parameters. For further information, refer to Filling an Initial Screen Using SPA/GPA Parameters.
regards
vinod

Examples for SAP Memory and ABAP Memory

Hi all,
can u give me one example of sap memory and abap memory.
Ranjith

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 at the time of logon 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 .
example:
ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETERstatements.
To fill one, use:
SET PARAMETER ID pid FIELD f
This statement saves the contents of field f under the ID pid in the SAP memory. The ID pid can be up to 20 characters long. If there was already a value stored under pid, this statement overwrites it. If you double-click pid in the ABAP Editor, parameters that do not exist can be created as a Repository object.
To read an SPA/GPA parameter, use:
GET PARAMETER ID pid FIELD f.
This statement places the value stored under the pid ID into the variable f. If the system does not find any value for pid in the SAP memory, sy-subrc is set to 4. Otherwise, it sets the value to 0.
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 memory area remains throughout a sequence of program calls, with the exception of LEAVE TO TRANSACTION. To pass data to a program that you are calling, the data needs to be placed in ABAP memory before the call is made from the internal calling session using the EXPORT statement. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory using the IMPORT statement. If control is then returned to the program that made the initial call, the same procedure operates in reverse.If a transaction is called using LEAVE TO TRANSACTION, the ABAP memory and the call stack are deleted. They cannot be used for data transfer.
Since objects belonging to ABAP objects can only be accessed within an internal session, it does not make sense and is therefore forbidden (from a syntax point of view) to pass a reference to an object to a calling program through the ABAP memory.
Example:
Export hello to memory id 'Hello_world'.
Import hello from memory id 'Hello_world'
Regards
Sudheer

ABAP / SAP memory

Hi Friends,
Kindly give me sample programs, for ABAP Memory and SAP memory.
TIA.
Regards,
MARK K

Hi,
DATA TEXT1(10) VALUE 'Exporting'.
DATA ITAB LIKE SBOOK OCCURS 10 WITH HEADER LINE.
DO 5 TIMES.
ITAB-BOOKID = 100 + SY-INDEX.
APPEND ITAB.
ENDDO.
EXPORT TEXT1
       TEXT2 FROM 'Literal'
TO MEMORY ID 'text'.
EXPORT ITAB
TO MEMORY ID 'table'.
In this example, the text fields TEXT1 and TEXT2 are stored in the ABAP memory of program SAPMZTS1 under the name "text". The internal table ITAB is stored under the name "table".
DATA TEXT1(10) VALUE 'Exporting'.
DATA ITAB LIKE SBOOK OCCURS 10 WITH HEADER LINE.
DO 5 TIMES.
ITAB-BOOKID = 100 + SY-INDEX.
APPEND ITAB.
ENDDO.
EXPORT TEXT1
       TEXT2 FROM 'Literal'
TO MEMORY ID 'text'.
EXPORT ITAB
TO MEMORY ID 'table'.
SUBMIT SAPMZTS2 AND RETURN.
SUBMIT SAPMZTS3.
The first part of this program is the same as the example in the section Saving Data Objects in Memory. In the example, the programs SAPMZTS1 and SAPMZTS2 are called using SUBMIT. You can create and maintain the programs called using the SUBMIT statement by double-clicking their names in the statement. For further information about the SUBMIT statement, refer to Calling Executable Programs (Reports)
Example for SAPMZTS2:
PROGRAM SAPMZTS2.
DATA: TEXT1(10),
      TEXT3 LIKE TEXT1 VALUE 'Initial'.
IMPORT TEXT3 FROM MEMORY ID 'text'.
WRITE: / SY-SUBRC, TEXT3.
IMPORT TEXT2 TO TEXT1 FROM MEMORY ID 'text'.
WRITE: / SY-SUBRC, TEXT1.
Example for SAPMZTS3:
PROGRAM SAPMZTS3.
DATA JTAB LIKE SBOOK OCCURS 10 WITH HEADER LINE.
IMPORT ITAB TO JTAB FROM MEMORY ID 'table'.
LOOP AT JTAB.
WRITE / JTAB-BOOKID.
ENDLOOP.
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.
TEXT = 'xxxxxxxxxx'.
IMPORT TEXT FROM MEMORY ID IDEN.
WRITE: / SY-SUBRC, TEXT.
The output is
0 0123456789
4 xxxxxxxxxx
The FREE MEMORY statement deletes the data cluster "XYZ". Consequently, SY-SUBRC is 4 after the following IMPORT statement, and the target field remains unchanged.
sap memory
TABLES SBOOK.
START-OF-SELECTION.
WRITE: 'Select a booking',
SKIP.
GET SBOOK.
WRITE: SBOOK-CARRID, SBOOK-CONNID,
         SBOOK-FLDATE, SBOOK-BOOKID.
HIDE: SBOOK-CARRID, SBOOK-CONNID,
         SBOOK-FLDATE, SBOOK-BOOKID.
AT LINE-SELECTION.
SET PARAMETER ID: 'CAR' FIELD SBOOK-CARRID,
                    'CON' FIELD SBOOK-CONNID,
                    'DAY' FIELD SBOOK-FLDATE,
                    'BOK' FIELD SBOOK-BOOKID.
CALL TRANSACTION 'BOOK'.
Thanks,
Das............

In internal sessions sap memory will not use {export to...} statment

SAP memory does not use "Export tou2026" statement for internal sessions

hi,
ABAP memory
Within the same internal session
SAP memory
Across internal sessions
IN SAP MEMORY
SET PARAMETER ID <pid> FIELD <f>.- Writes the contents of the field f to the global SAP memory under the key pid . If the key already contains a value, it is overwritten.
GET PARAMETER ID <pid> FIELD <f>.- Transfers the value stored under the key pid from the global user-related SAP memory to the field f .
IN ABAP memory
EXPORT obj1 ... objn TO MEMORY.
IMPORT f itab FROM MEMORY.
hope it may help you.
Thanks
Sachin

Hi Friends ....Difference between SAP memory and ABAP memory

Hi Friends,
I faced a interview and they ask this question
What is the difference between SAP Memory and ABAP memory..

conti
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 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.
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.
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
Set
http://www.geocities.com/SiliconValley/Campus/6345/set_para.htm
GET
http://www.geocities.com/SiliconValley/Campus/6345/get_para.htm
EXPORT
http://www.geocities.com/SiliconValley/Campus/6345/export01.htm
Other Imp Help
http://www.geocities.com/SiliconValley/Campus/6345/abapindx.htm

Need to clear SAP memory

Hi Experts,
I need to Clear SAP memory set using the 'Parameter ID' keyword in reports. Please advise.
Thanks in advance,
Vivenchandar R

Sure, you can simply set the parameter id to a blank field. For example.
data: vbeln type vbak-vbeln.
vbeln = space.
set parameter id 'AUN' field vbeln.
Regards,
Rich Heilman

Fm to read from SAP memory

Hi,
I need a fm whic will read the sub-equipments currnetly dismanteled for a superior equipment.
I am using tcode ieo2 and enhancement IEQM0003
Plz help

Hi
you can use export and import parameter i.d to read from sap memory
Regards
Divya

SAPNOTE for memory parameter ECC 6.0, Windows?

Hi,
Can anyone please help by suggesting some SAP notes on memeory management parameters for ECC 6.0 (netweaver 2004s) running on Windows and SQL database?
Thanks & Regards,
Sujit.

Juan,
Physical memory: 130.937,0 MB
Current memory: 104.448,0 MB
Data Cache hit ratio (MB): 93,534%
Job is running in BTC.
Roll memory     Dialog session   kB     6.348
                Nondialog sess. kB     6.348
                Available        kB 2.000.000
                in shared memory kB   262.288
                on disk          kB 1.737.712
                Used             kB     4.945
                Maximum used     kB    25.768
Paging memory   Session buffer   kB     1.200
                Available        kB 2.000.000
                in shared memory kB   131.072
                on disk          kB 1.868.928
                Used             kB     3.527
                Maximum used     kB   150.704
Extended memory Dialog session   kB 7.812.500
                Nondialog sess. kB 7.812.500
                Available        kB 8.384.512
                Used             kB   761.856
                Maximum used     kB 4.542.464
Heap memory     Dialog session   kB 2.929.688
                Nondialog sess. kB 2.929.688
                Used             kB         0
                Maximum used     kB 2.929.727
SWAP is zero in central instance where the job is running. Any other memory parameter if want to know?
Let me know your suggestion which memory parameter can be incresed?
And, I will close the prevîous thread.
Thanks & Regards,
Sujit.

Importing to SAP Memory

Hi All,
I have created an implementation for the badi LE_SHP_DELIVERY_PROC. In the method CHANGE_FIELD_ATTRIBUTES i have written a code to export Vendor(LIFNR) to the sap memory. However, i need to import this to an include and use it in the function module CONVERSION_EXIT_ALPHA_INPUT with the LIFNR as the exporting parameter in the function module. how do I import this LIFNR in the include. Please help.

Hi,
Export LIFNR TO MEMORY ID 'AB'. (ID is the name of memory, you don't need to create it ).
Import LIFNR FROM MEMORY ID 'AB'. In Importing program create the same field name.
Hope this is useful to you!
Thanks,
Reetesh

How to read From SAP Memory

hello friends,
can u help me to read the document no. generated at runtime in BDC from
SAp Memory.
Thanks

HI,
See this both the eq u will be get ur requirement.
report ykrish_set_prg1.
data : g_ebeln type ekko-ebeln.
select-options : s_ebeln for g_ebeln obligatory.
data: begin of it_ekko occurs 0,
        ebeln type ekko-ebeln,
        bukrs type ekko-bukrs,
        bstyp type ekko-bstyp,
        bsart type ekko-bsart,
      end of it_ekko.
start-of-selection.
select ebeln bukrs
         bstyp bsart
    into table it_ekko
    from ekko
    where ebeln in s_ebeln.
if sy-subrc = 0.
    sort it_ekko by ebeln.
endif.
end-of-selection.
if not it_ekko[] is initial.
    loop at it_ekko.
      write :/ it_ekko-ebeln hotspot on,
               it_ekko-bukrs,
               it_ekko-bstyp,
               it_ekko-bsart.
      hide it_ekko-ebeln.
    endloop.
endif.
at line-selection.
set parameter id 'BES' field it_ekko-ebeln.
write :/ 'Parameter ID is set for Document Number :', it_ekko-ebeln.
report ykrish_get_prg1.
data : g_ebeln type ekko-ebeln.
get parameter id 'BES' field g_ebeln.
call transaction 'ME23N'.
Regards,
Naresh

What is the diffrence betwen the sap memory &abapmemory.

what is the diffrence betwen the sap memory &abapmemory.

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 (see also Organization of Modularization Units). 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/4 memory.
Hope it helps.
Chang

Tune sap memory parameter

Similar Messages

Maybe you are looking for