topic Re: diff between internal session and external session in Application Development and Automation Discussions

diff between internal session and external session

Former Member — Tue, 26 Dec 2006 05:19:29 GMT

Hi,

i would like to know the difference between internal and external session and

how these session technically handle.

Re: diff between internal session and external session

Former Member — Tue, 26 Dec 2006 05:23:59 GMT

u mean to say BDC...Internal Session is Call Transaction Method whereas External session is Session method.....Means call transaction executes data and posts into SAP. Session method needs to be run from SM35 and then gets posted into SAP.

Re: diff between internal session and external session

Former Member — Tue, 26 Dec 2006 05:33:22 GMT

1. return code - for session No , for call transaction yes

2. database update - for session synchronous,for call transaction asynchronous/synchronous

3. processing - for session -time-dalayed , for call transaction - immediately

4. transactions - for session - more than one,for call transaction only one

5. error log - for session -will be created,for call transaction- will not be created

hope this will help you in understanding the differences between the sessions

Re: diff between internal session and external session

Former Member — Tue, 26 Dec 2006 05:34:16 GMT

Hi,

May be you are asking about SAP memory and ABAP Memory,

SAP Memory - Available over the sessions

Use Memory ID's

ABAP Memory - Available in current session only Example : funcntion modules.

Re: diff between internal session and external session

Former Member — Tue, 26 Dec 2006 05:41:02 GMT

let me know about which sessions you want to know. reward points if the above details that i provided are helpful

Re: diff between internal session and external session

Former Member — Tue, 26 Dec 2006 05:42:49 GMT

Hi Rao,

exactly i wanted to know about that only so please let me know that

a user can have up to six session. so i am getting confuse for that only whether

one session or all six abap session are internal session .so which one called external session .

thanks

Rao

Re: diff between internal session and external session

Former Member — Tue, 26 Dec 2006 05:44:12 GMT

hi,,

internal session means from sap screen you have option called create session.

external session means you have to go for login to the system again whcih is related external session

Re: diff between internal session and external session

Former Member — Tue, 26 Dec 2006 05:52:09 GMT

Hi Reddy,

I want to know about that only so please let me know in detail because

we can have upto six session ,so does all these six sessions are called internal

session . how can we pass data to internal session ( import and export).So what

about Set and Get parameters.

Thanks

Reddy

Re: diff between internal session and external session

Former Member — Tue, 26 Dec 2006 06:02:56 GMT

HI Kumar,

Exactly i want to know about ABAP Session so because we can have upto

six session so which called internal session and which one external and how data

can be pass to them.

Thanks

Re: diff between internal session and external session

Former Member — Tue, 26 Dec 2006 15:30:36 GMT

hi,,

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 .

regard

deepak

Re: diff between internal session and external session

Former Member — Tue, 26 Dec 2006 16:05:48 GMT

Hi,

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.

Check the below links for more information...

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

I hope this answers yor question

Regards,

Vara

I hope this solves your quesiton....