topic Re: abap general in Application Development and Automation Discussions

abap general

Former Member — Wed, 11 Jul 2007 08:32:57 GMT

friends

i want to know the difference between abap memmory and sap memmory and where we will use sap memmory.

please give me answer with an example if possible.

thanks

Re: abap general

Former Member — Wed, 11 Jul 2007 08:33:32 GMT

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 & SAP Memory

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

Re: abap general

Former Member — Wed, 11 Jul 2007 08:34:54 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

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 if useful

Regards

Priyanka.

Re: abap general

Former Member — Thu, 12 Jul 2007 04:36:00 GMT

Hi,

SAP and ABAP Memory

There is a difference between the cross-transaction SAP memory and the transaction-specific ABAP memory.

Global SAP memory

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

Input fields on screens can be linked with parameters in the SAP memory, which allows you to preassign values to the input fields on initial screens.

With general screens, the linking takes place during the definition of the screen using the Screen Painter tool. When setting the field attributes of an input field, you can specify the ID of an SPA/GPA parameter in the Parameter-ID attribute. In the checkboxes SET Parameter and GET Parameter you can specify whether the screen field is filled with the value of the SPA/GPA parameter at the time of PBO or whether the SPA/GPA parameter is filled with the user input on the screen at the time of PAI.

With selection screens, the linking is carried out using the MEMORY ID addition to the PARAMETERS or SELECT-OPTIONS statement. If you specify an SPA/GPA parameter ID, when declaring a parameter or selection criterion, the relevant input field is linked with the parameter.

Local SAP memory

The local SAP memory is available to the user throughout a transaction, within which you can also call other program units, for example using SUBMIT or CALL TRANSACTION. With SET PARAMETER you write to both the global and the local SAP memory. If the global SAP memory is changed by an external mode of the same user, the local SAP memory remains unchanged. This ensures that parameters set in the frame of a transaction remain unchanged until the end of this transaction. The local SAP memory is deleted after the transaction is ended.

ABAP memory

The contents of the ABAP 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 if helpful

Regards

Raghavendra.D.S

Re: abap general

Former Member — Thu, 12 Jul 2007 05:29:30 GMT

Difference Between SAP and ABAP Memory

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.

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.

example :

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.

example

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

reward points if it is usefull....

Girish

Re: abap general

Former Member — Thu, 12 Jul 2007 06:00:05 GMT

Hi Savitha,

SAP Memory

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

Regards

Sathish

Re: abap general

Former Member — Thu, 12 Jul 2007 06:01:14 GMT

SAP Memory

ABAP/4 Memory

SAP memory

ABAP/4 memory

What is the code to send internal table to abap memory?

This code is from which program you want to export to the ABAP memory:

export ist_resb to memory id 'ZPPC0122_FD'.

where ist_resb is the internal table name &

ZPPC0122_FD is the include name of my program ZPPC0122.

This code is from which program you want to import from the ABAP memory

import *ist_resb *= ist_resb from memory id 'ZPPC0122_FD'.

where ist_resb This internal table is the importing program internal table.

ist_resb This internal table is the exporting program internal table.

But remember in both the program you have defined the same internal table with same structure

Regards

Sathish

Re: abap general

Former Member — Mon, 16 Jul 2007 10:51:59 GMT

ABAP Memory

Memory area within every main session, which the programs with the statements EXPORT and IMPORT can access. This memory area is maintained via a succession of program calls (call sequence).

SAP Memory

Memory area of application server, which all main sessions of a user session access jointly. ABAP programs have access to SPA/GPA parameters stored in the SAP memory.

do give point if useful

regards

debjani