Get Example source ABAP code based on a different SAP table
ABAP_RFC - Session Every remote call of a function module using an RFC interface defines an RFC session as a dedicated user session in the target system. The logon data of an RFC session is defined during the definition of an RFC destination in transaction SM59. If no values are defined for the user name, the client, or the logon language in this definition, they are filled implicitly when the session is loaded for the first time with the user name (sy-uname), the client (sy-mandt ), and the text environment language (sy-langu) of the calling session. The function pool of the function module is loaded into an ABAP_ISESS of the RFC session and is persisted there, so that when function modules with the same RFC destination and function pool are called repeatedly, the global data of this function pool can be accessed together. When functions are called in an external system, the RFC Library API simulates this behavior. A connection and its RFC session are persisted until it is explicitly closed, or until the calling program is finished. The function module RFC_CONNECTION_CLOSE or API functions <(>RfcAbort<)> and <(>RfcClose<)> are used to explicitly close a connection.
Latest notes: It should be noted that when the logon language is passed from the current session, the logon language of the session is not used, but the text environment language, which, unlike the logon language, can be affected by the statement SET LOCALE LANGUAGE . This applies particularly to the destination NONE and SELF and therefore also to the asynchronous remote function call without a specified destination. ABAP_HINT_END
ABAP_EXAMPLE_ABEXA Implicit Logon Data in RFC. ABAP_EXAMPLE_END
