Application Development and Automation 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: 
Read only

Difference between internal and external session

Former Member
0 Likes
2,235

Hi experts,

I tried to read it many times but I am still very confused with it.

1. Each logon through Sap Logon will create a new external session? New Mode created through /o will create another internal session in this external session? Is it OK?

2. When are the data deleted from Sap Memory which are allocated through the command SET PARAMETER?

Thank you very much for your answers,

Radek

1 ACCEPTED SOLUTION
Read only

Maciej_DomagaBa
Contributor
1,668

1. No.

Each logon made through Saplogon creates a terminal session.

Within the terminal session you can have up to 6 external sessions (GUI windows). You can think of each external session as of one GUI window.

Internal sessions are created by the system within an external session, each time a new program is called and its data must be stored somewhere in memory. Each such program lives in its internal session. The first one is loaded when you start some transaction. Then it can in turn call another program if it needs - then the system will create another internal session for the called program (within the same external session = the same GUI window).

So you, as a user, do not observe internal sessions in any visual way (maybe that's why they're called "internal" ).

2. I don't understand what you mean - set/get parameter do not create/delete data but rather set and read the value. The value set this way is valid within the terminal session.

regards

4 REPLIES 4
Read only

Former Member
0 Likes
1,668

Hi

See the bellow examples:

Internal session : report called from any RFC or user exit for a transaction etc things are interrelated to each other for the perticular instance we are using them.

External Session: we are using a report and same time we are using any other object which is not at all related to this report neither it calls that report for perticular instance we are using it.

Regards

Sagar

Read only

former_member434229
Active Participant
0 Likes
1,668

Hi,

1. Check these links below:

ABAP Memory - Internal Session

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/9f/db9df735c111d1829f0000e829fbfe/frameset.htm

SAP Memory - External session

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/9f/db9e0435c111d1829f0000e829fbfe/frameset.htm

2. When You Free Memory ID, it clear the data stored in Internal or external session, else internal session memory remains till you end your current session and external memory till you log out from the system.

Regards,

Ni3

Read only

Maciej_DomagaBa
Contributor
1,669

1. No.

Each logon made through Saplogon creates a terminal session.

Within the terminal session you can have up to 6 external sessions (GUI windows). You can think of each external session as of one GUI window.

Internal sessions are created by the system within an external session, each time a new program is called and its data must be stored somewhere in memory. Each such program lives in its internal session. The first one is loaded when you start some transaction. Then it can in turn call another program if it needs - then the system will create another internal session for the called program (within the same external session = the same GUI window).

So you, as a user, do not observe internal sessions in any visual way (maybe that's why they're called "internal" ).

2. I don't understand what you mean - set/get parameter do not create/delete data but rather set and read the value. The value set this way is valid within the terminal session.

regards

Read only

0 Likes
1,668

Maciej, Thanks for providing the good explanation.