set get parameters

[Former Member]

Hi,

what is the use of set ,get parameters and what is ABAP memory and SAP Memory difference?

[former_member156446]

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.

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.

[Former Member]

Functionality is same.

SAP Memory is global memory so it can be useful in any module in the SAP.

ABAP memory is local memory, that means it can be useful in the ABAP module only.

By using set we can store one value, by using get we can get the values

[Former Member]

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.

[Former Member]

Hi....

ABAP memory: The data in the ABAP memory can be used with in session by using following staements.

export <f1> [from<g1>] <f2> [from<g2>]... <fn> [from<gn>] to

memory id <name of memory location>.

import <f1> [to <g1>] <f2> [to <g2>]... <fn> [to<gn>] from memory id <name>

SAP memory:it is used to share the data across the session or in different transactions.

SET PARAMETER:

syntax:

SET PARAMETER ID <pid> FIELD <f>.

it is used to store a value of the field in sap memory and it is identified by parameter id(pid).

GET PARAMETER:

syntax:

GET PARAMETER ID<pid> FIELD <f>.

it is used to get data from memory location pid into the given field f.

[Former Member]

hi,

set angd get parameters:

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.

ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETER statements

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

pls reward if its useful

[Former Member]

Hi,

here is the simple answer for your Q.

these set/get parameter id's are basically for retriving the earlier data in your screen. suppose u r created an initial screen 100 where u need to enter some value QMNUM (QMEL-QMNUM) by executing the transaction code etc. first time you need to enter the value qmnum. next time if you execute the same transaction code, by default it will show the previous value. if you want to find the parameter id of qmnum go to table qmel. then double click on field type 'QMNUM' there you can find the parameter id.

DATA: gv_fx_qmnum TYPE qmnum.

GET PARAMETER ID 'IQM' FIELD gv_fx_qmnum.

reward if helpful.

Regards

Venkat

[Former Member]

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

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.

[Former Member]

Hi

SET and get parameters

http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9e0435c111d1829f0000e829fbfe/content.htm

SAP AND ABAP MEMORY

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.

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.

*************

SAP global memomy 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 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.

progaram A

export itab to memory id 'TeST'.

program B

import itab from memory Id 'TEST'.

value of itab is not retained in program b since

they are not in same LUW.

program A

export itab to memory id 'TeST'.

SUBMIT rep and return

program B

import itab from memory Id 'TEST'.

value of itab are retained in program b since

they are in same LUW.

[Former Member]

Hi,

SAP Memory is global memory so it can be useful in any module in the SAP.

ABAP memory is local memory, that means it can be useful in the ABAP module only.

SET PARAMETER:

syntax: SET PARAMETER ID <pid> FIELD <f>.

It is used to store the value of the field <f> under the id <pid>.

GET PARAMETER:

syntax: GET PARAMETER ID<pid> FIELD <f>.

It is used to get data of the field <f> stored under the id< pid>.

REgards,

kavitha.k

[Former Member]

Hi,

SAP Memory is global memory so it can be useful in any module in the SAP.

ABAP memory is local memory, that means it can be useful in the ABAP module only.

SET PARAMETER:

syntax: SET PARAMETER ID <pid> FIELD <f>.

It is used to store the value of the field <f> under the id <pid>.

GET PARAMETER:

syntax: GET PARAMETER ID<pid> FIELD <f>.

It is used to get data of the field <f> stored under the id< pid>.

REgards,

kavitha.k