Get Example source ABAP code based on a different SAP table
VERSION 5 OUT
User Sessions Each execution of an ABAP program takes place in an ABAP_ISESS > in an ABAP session> within an ABAP_ASINSTANCE > user session>. For this, at least one ABAP session is open in each user session. A user session is opened whenever an ABAP user > logs on> to an AS ABAP >. Here, the following fixed properties of the user session are defined:
User name> The user name is assigned a user master record> and authorizations> that affect the behavior of an ABAP program. The current user name is returned by the method GET_USER_NAME> of the class CL_ABAP_SYST>> and is available in the system field> sy-uname>.
Client ID> The client ID determines the current client>. When database content is accessed using AB_SQL >, implicit client handling> is used by default where only the data of the current client is accessed. The current client is returned by the method GET_CLIENT> of the class CL_ABAP_SYST>> and is available in the system field> sy-mandt>.
Logon language> The logon language determines the access to certain text repositories and is also the text environment language > by default. The current logon language is returned by the method GET_LOGON_LANGUAGE> of the class CL_ABAP_SYST>>. The system field> sy-langu>, on the other hand, contains the text environment language of the current ABAP_ISESS > , which can also be set to a different value. There are different types of user sessions in which different rules and restrictions apply when ABAP programs are executed:
Dialog sessions> Dialog sessions are used for dialog processing> with the SAP GUI>. The ABAP programs are controlled by classic dynpros> and their special forms, selection screens > and classic lists>.