Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

internal & external session ?

Former Member
0 Kudos

for each main session we can get 6 internal session.then what is this meaning ?

what is internal session & external session ?plzzzzzzzz explain with examples .

1 ACCEPTED SOLUTION

Former Member
0 Kudos

internal session ( means ABAP/4 memory ) when u r using call transaction or u can write t code in command field in that case internal session can genrate means from sap screen you have option called create session.

external session (means sap memory) whenever u login to sap in that case external session genrate or xternal session means you have to go for login to the system again whcih is related external session .

Check the below links for more information...

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

In general 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.

<b>Reward points if this helps you.</b>

siva

Message was edited by:

SivaKumar

3 REPLIES 3

Former Member
0 Kudos

internal session ( means ABAP/4 memory ) when u r using call transaction or u can write t code in command field in that case internal session can genrate means from sap screen you have option called create session.

external session (means sap memory) whenever u login to sap in that case external session genrate or xternal session means you have to go for login to the system again whcih is related external session .

Check the below links for more information...

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

In general 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.

<b>Reward points if this helps you.</b>

siva

Message was edited by:

SivaKumar

ferry_lianto
Active Contributor
0 Kudos

Hi,

External Session is per main window and uses SAP memory to share data between External sessions. An external session is started when you start a program and whenever you use CALL TRANSACTION. Data stored in SAP memory is there till you logoff.

Internal Session is a session with in the External session there can be many internal sessions in an External Session, You can use ABAP memory to share data between Internal session. SUBMIT statement creates an internal session and replaces calling programs internal session if you don't want that use SUBMIT with RETURN.

Regards,

Ferry Lianto

varma_narayana
Active Contributor
0 Kudos

Hi..

Internal Session: It is the memory allocated for a program during execution. When we call a program using SUBMIT or Call Transaction then it will be loaded in a new internal Session. To exchange the data between internal sessions we can use ABAP MEMORY.

External Session: It is nothing but a window. Which we can create using SYSTEM -> CREATE SESSION.

We can open up to 6 external sessions (this is set by Basis of course).

We can use SAP Memory to exchange the data between External sessions in a Login.

<b>Reward if Helpful.</b>