SAP GENERAL_GET_APP_SERVER_NAME Function Module for Get long app server name
GENERAL_GET_APP_SERVER_NAME is a standard general get app server name SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get long app server name processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for general get app server name FM, simply by entering the name GENERAL_GET_APP_SERVER_NAME into the relevant SAP transaction such as SE37 or SE38.
Function Group: GENERAL_DB2
Program Name: SAPLGENERAL_DB2
Main Program: SAPLGENERAL_DB2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled + BasXML supported
Update:

Function GENERAL_GET_APP_SERVER_NAME pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'GENERAL_GET_APP_SERVER_NAME'"Get long app server name.
IMPORTING
SERVER_NAME = "Local app server name
EXCEPTIONS
ERROR_READING_NAME = 1
EXPORTING Parameters details for GENERAL_GET_APP_SERVER_NAME
SERVER_NAME - Local app server name
Data type: MSXXLIST-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_READING_NAME -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GENERAL_GET_APP_SERVER_NAME Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_server_name | TYPE MSXXLIST-NAME, " | |||
| lv_error_reading_name | TYPE MSXXLIST. " |
|   CALL FUNCTION 'GENERAL_GET_APP_SERVER_NAME' "Get long app server name |
| IMPORTING | ||
| SERVER_NAME | = lv_server_name | |
| EXCEPTIONS | ||
| ERROR_READING_NAME = 1 | ||
| . " GENERAL_GET_APP_SERVER_NAME | ||
ABAP code using 7.40 inline data declarations to call FM GENERAL_GET_APP_SERVER_NAME
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single NAME FROM MSXXLIST INTO @DATA(ld_server_name). | ||||
Search for further information about these or an SAP related objects