SAP RSPO_MAP_SERVERNAME Function Module for Represent Logical Server Name on Physical Server Name
RSPO_MAP_SERVERNAME is a standard rspo map servername SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Represent Logical Server Name on Physical 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 rspo map servername FM, simply by entering the name RSPO_MAP_SERVERNAME into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEXT
Program Name: SAPLSEXT
Main Program: SAPLSEXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSPO_MAP_SERVERNAME 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 'RSPO_MAP_SERVERNAME'"Represent Logical Server Name on Physical Server Name.
EXPORTING
LNAME = "
IMPORTING
PNAME = "
IMPORTING Parameters details for RSPO_MAP_SERVERNAME
LNAME -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSPO_MAP_SERVERNAME
PNAME -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSPO_MAP_SERVERNAME 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_lname | TYPE C, " | |||
| lv_pname | TYPE C. " |
|   CALL FUNCTION 'RSPO_MAP_SERVERNAME' "Represent Logical Server Name on Physical Server Name |
| EXPORTING | ||
| LNAME | = lv_lname | |
| IMPORTING | ||
| PNAME | = lv_pname | |
| . " RSPO_MAP_SERVERNAME | ||
ABAP code using 7.40 inline data declarations to call FM RSPO_MAP_SERVERNAME
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.Search for further information about these or an SAP related objects