Parameter Id

[Former Member]

Hi,

What is the difference between parameter id and memeory id?

How do i use it in the program?

Will I run into performance issue when i use paramter id's?

Regards,

Arvindh

[Former Member]

Hi,

The SAP Memory is a user-specific memory area of the application server, which is accessed by all main sessions of a user session at once. ABAP programs have access to SPA/GPA parameters stored in the SAP Memory (also called SET/GET parameters).

e.g.

Using Set parameter

you can give value of variable (dobj) to parameter ID 'pid'. This will store value in SAP memory

SET PARAMETER ID pid FIELD dobj.

When you want to use that value stored in SAP memory

you can use GET parameter.

GET PARAMETER ID pid FIELD dobj.

The above cannot be used for internal table. Supported data types are (data type C, N, D or T).

Memory-ID is used to save and retrieve the last entered data in the field.

Eg: PARAMETERS p_vbeln for vbak-vbeln memory-id pid

Shared memory is the area that can be used to share data between different processes.

Regards,

Vinodh

[Former Member]

Hi,

Hi

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

for more information please go through this link

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

*******please reward points if the information is helpful to you*************

[Former Member]

Hi

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

Reward points for useful Answers

Regards

Jay

[Former Member]

Hi

ABAP memory -

---

> Memory related to that particular session

ABAP Memory is a memory area which all programs in the call stack within the same internal session can access. The EXPORT and IMPORT

statements are used here.

export p_matnr = p_matnr to memory id 'ZTESTMAT'.

import p_matnr = p_matnr from memory id 'ZTESTMAT'.

SAP memory -

---

> memory related to all sessions

SAP Memory is a global memory area which is common to a user. This allows for passing data between sessions. The SET PARAMETER ID and GET PARAMETER ID statements are used here

SET PARAMETER ID 'MAT' field p_matnr.

GET PARAMETER ID 'MAT' field p_matnr.

Regards,

Aparna

[Former Member]

Hi Arvindh,

As far as performance is concerned, its not advisable to use parameter id's. But even if they are used, care should be taken to initialize the parameter after its been consumed.

Regards,

Vinodh.