ABAP Memory & SAP Memory

The memory area of each main session has an area called ABAP Memory, which the programs in the internal session can access with EXPORT TO MEMORY and IMPORT FROM MEMORY. Data in the ABAP Memory is conserved through a sequence of program calls. To transfer data to a called program, it can be placed in the ABAP Memory with the EXPORT statement before the program is called. The internal session of the called program then replaces the internal session of the calling program and the data can be read from the ABAP Memory with the IMPORT statement. Data can be passed in exactly the same way when the system returns to the calling program.

The SAP Memory is a memory area to which all sessions of a SAP logon have common access. In ABAP programs, the SET PARAMETER and GET PARAMETER commands can be used to access the so-called SPA/GPA parameters stored in the SAP Memory. Input fields on screens can be linked to this type of parameter and default entries thereby established.

If you like this post, you may as well like these too:

1. ABAP Memory Ever thought as to how to exchange the data between programs? well, that’s why we have ABAP Memory for. EXPORT TO MEMORY ID <memory_id_ name> will copy the data to...
2. ABAP Programs: Exporting to the ABAP/4 Memory REPORT ZSOURCE1401. * Work areas TABLES: CUSTOMERS, BOOKINGS. * Internal tables which will be exported DATA: ALL_CUSTOMERS LIKE CUSTOMERS OCCURS 100 WITH HEADER LINE, ALL_BOOKINGS LIKE BOOKINGS OCCURS 10 WITH...
3. ABAP Programs: Importing from the ABAP/4 Memory REPORT ZSOURCE1402. * Internal tables which will be imported DATA: ALL_CUSTOMERS LIKE CUSTOMERS OCCURS 100 WITH HEADER LINE, ALL_BOOKINGS LIKE BOOKINGS OCCURS 10 WITH HEADER LINE, NEW_BOOKINGS LIKE BOOKINGS OCCURS...