topic Re: sap memory and abap memory in Application Development and Automation Discussions

sap memory and abap memory

Former Member — Sat, 29 Dec 2007 09:19:44 GMT

hi any body tell me where sap memory stores data and where abap memory stores data.i know sap memory is global ...i want 2 know where the global data stores..

Re: sap memory and abap memory

Former Member — Sat, 29 Dec 2007 09:47:59 GMT

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.

These two are memories

these are @ repository.- part of DB

its a matter of session nt in the matter of database.

reward if its useful.

Re: sap memory and abap memory

Former Member — Sat, 29 Dec 2007 10:00:22 GMT

pls tell me ...diff between internal session and main session...

Re: sap memory and abap memory

Former Member — Sat, 29 Dec 2007 10:04:19 GMT

Hi,

if u give tcode /nse38 in command field then it opens a session which is internal one and if u type /ose38 in commnad field in same command field then another session opens which is external to first one.

hope u got some idea

Regards

Re: sap memory and abap memory

Former Member — Sat, 29 Dec 2007 10:08:49 GMT

ya..thanx

Re: sap memory and abap memory

Former Member — Wed, 05 Mar 2008 05:28:15 GMT

Hai,

Memory Structures of an ABAP Program

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.

The following diagram shows how an application program accesses the different areas within shared memory:

In the diagram, an ABAP program is active in the second internal session of the first main session. It can access the memory of its own internal session, ABAP memory and SAP memory. The program in the first internal session has called the program which is currently active, and its own data is currently inactive on the stack. If the program currently active calls another program but will itself carry on once that program has finished running, the new program will be activated in a third internal session.

Re: sap memory and abap memory

Former Member — Wed, 05 Mar 2008 05:29:52 GMT

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

Re: sap memory and abap memory

Former Member — Wed, 05 Mar 2008 05:33:46 GMT

Hi,

Storage Media for Data Clusters

Data clusters are stored in a storage medium with the help of the statement EXPORT ( see: Statements for Data Clusters) . This is achieved using the different variations of the addition medium. These are as follows:

· DATA BUFFER xstr for storage in a byte string xstr

· INTERNAL TABLE itab for storage in an internal table itab (Standard table)

· MEMORY ID id for storage under the name id in the ABAP Memory

· DATABASE dbtab ... ID id for storage under the name id in a database table in the ABAP Dictionary

· SHARED MEMORY dbtab ... ID id and SHARED BUFFER dbtab ... ID id for storage under the name id in the cross-transaction application buffer of the applications server's shared memory.

In the following you will learn more about the temporary storage of data clusters in ABAP memory and shared memory, as well as permanent storage in databanks. You can find detailed information about the different storage media in the keyword documentation.

ABAP Memory

ABAP memory is a memory area within the internal session (roll area) of an ABAP program and any other program called from it using CALL TRANSACTION or SUBMIT.

ABAP memory is independent of the ABAP program or program module from which it was generated. In other words, an object saved in ABAP memory can be read from any other ABAP program in the same call chain. ABAP memory is not the same as the cross-transaction global SAP memory. For further information, refer to Passing Data Between Programs.

This allows you to pass data from one module to another over several levels of the program hierarchy. For example, you can pass data

· from executable programs that have been called using SUBMIT

· From a transaction to an executable program.

· Between dialog modules.

· From a program to a function module.

and so on.

The contents of the memory are released when you leave the transaction.

Database Tables

You can store data clusters in databases in the ABAP Dictionary. In order to do so, you must create databank tables with a special structure. SAP provides a template databank table called INDX, which you can copy and modify. This is why we also make reference to INDX type tables (see the keyword documentation).

This method allows you to store complex data objects with deep structures in a single step, without having to adjust them to conform to the flat structure of a relational database. Your data objects are then available system-wide to every user. To read these objects from the database successfully, you must know their data types.

You can use INDX-type database tables to store the results of analyses of data from the relational database. For example, if you want to create a list of your customers with the highest revenue, or an address list from the personnel data of all of your branches, you can write ABAP programs to generate the list and store it as a data cluster. To update the data cluster, you can schedule the program to run periodically as a background job. You can then write other programs that read from the data cluster and work with the results. This method can considerably reduce the response time of your system, since it means that you do not have to access the distributed data in the relational database tables each time you want to look at your list.

Although INDX type tables are normal databank tables from the ABAP Dictionary, you should only use them in conjunction with the special statements for data clusters. Only in exceptional cases, for example in order to delete many data clusters from one area with a single statement, can you use Open SQL statements. In order to do this you must have a good working knowledge of the structure of INDX type tables and it is recommended that the table and its contents first be checked for different application cases using the data browser of the ABAP Workbench (transaction SE16).Although it is possible to access an INDX-type database using SQL statements, it is only possible to interpret the structure of the data cluster using ABAP statements.

Cross Transaction Application Buffer

The cross transaction application buffer is a storage area on an application server which all ABAP programs of the SAP system running on the same applications server can access. Data clusters in the cross transaction application buffer are exactly the same as data clusters that are organized in databank tables. Here we will refer to the databank table dbtab. The data are not stored in the databank table itself but in a table with a corresponding set up. Therefore the databank table dbtab must also be an INDX type (see keyword documentation). The structure of this table is then copied for the storage of the cluster in the buffer. This gives you the possibility to store your own administrative information in every cluster in the buffer and import it again as necessary.

The difference between the application buffers SHARED MEMORY and SHARED BUFFER lies in how the system reacts when the storage limit is reached (see Keyword documentation).

with regards,

sowjanyagosala.

Re: sap memory and abap memory

Former Member — Wed, 05 Mar 2008 05:33:50 GMT

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

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.

Re: sap memory and abap memory

Former Member — Wed, 05 Mar 2008 07:35:52 GMT

thanku very help ful