topic Re: hi in Application Development and Automation Discussions

hi

Former Member — Fri, 03 Aug 2007 07:30:20 GMT

what is diffrence between the sap memory and abap memory.

Re: hi

Former Member — Fri, 03 Aug 2007 07:33:28 GMT

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.

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

Anji

Re: hi

former_member196299 — Fri, 03 Aug 2007 07:34:06 GMT

hi Murali ,

The answer of the question you could have got from a simple search of the forum ..

Here is the difference I got from a document :

1. SAP memory is for cross-transaction Applications and ABAP/4 memory is transaction-specific.

2. 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 contents of the ABAP/4 memory are retained only during the lifetime of an external session. You can retain or pass data across internal sessions.

3. The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory. The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory.

Hope this helps !

Regards,

Ranjita

Re: hi

Former Member — Fri, 03 Aug 2007 07:34:23 GMT

hai,

Check this explanation.

SAP Memory

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.

reward points if useful.

bye

Re: hi

Former Member — Fri, 03 Aug 2007 07:35:28 GMT

Hi,

In the Overview of the R/3 Basis System you have seen that 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.

reward if it helps..

regards,

Omkar.

Re: hi

former_member150733 — Fri, 03 Aug 2007 07:35:45 GMT

SAP memory :

http://help.sap.com/saphelp_47x200/helpdata/en/9f/db9df735c111d1829f0000e829fbfe/frameset.htm

ABAP Memory:

http://help.sap.com/saphelp_47x200/helpdata/en/fc/eb3bc4358411d1829f0000e829fbfe/frameset.htm

Re: hi

Former Member — Fri, 03 Aug 2007 07:35:56 GMT

1. SAP Memory is a global memory area which all sessions within a

SAPgui have access to. This allows for passing data between

sessions. The SET PARAMETER ID and GET PARAMETER ID statements are

used to manipulate the SAP Memory.

SET PARAMETER ID 'MAT' field p_matnr.

GET PARAMETER ID 'MAT' field p_matnr.

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

ABAP Memmory & SAP Memmory

http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm

regards,

Message was edited by:

Kiran Sure(skk)

Re: hi

Former Member — Fri, 03 Aug 2007 07:36:53 GMT

Hi,

SAP Memory

ABAP/4 Memory

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

Sudheer