SAP GET_INTERFACE_WSDL Function Module for Create URL for interface WSDL
GET_INTERFACE_WSDL is a standard get interface wsdl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create URL for interface WSDL 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 get interface wsdl FM, simply by entering the name GET_INTERFACE_WSDL into the relevant SAP transaction such as SE37 or SE38.
Function Group: SRT_WSP_CONFIG_API
Program Name: SAPLSRT_WSP_CONFIG_API
Main Program: SAPLSRT_WSP_CONFIG_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GET_INTERFACE_WSDL 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 'GET_INTERFACE_WSDL'"Create URL for interface WSDL.
EXPORTING
IF_DEF_NAME = "WSP Name of Interface Object
IMPORTING
RESULT = "List of WSDL URLs
EXCEPTIONS
OBJECT_NOT_EXISTS_EXCEPTION = 1 TECHNICAL_EXCEPTION = 2
IMPORTING Parameters details for GET_INTERFACE_WSDL
IF_DEF_NAME - WSP Name of Interface Object
Data type: SRT_WSP_DT_OBJ_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GET_INTERFACE_WSDL
RESULT - List of WSDL URLs
Data type: SRT_WSP_WSDL_URL_LISTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_NOT_EXISTS_EXCEPTION - Configuration does not exist
Data type:Optional: No
Call by Reference: Yes
TECHNICAL_EXCEPTION - Technical error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GET_INTERFACE_WSDL 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_result | TYPE SRT_WSP_WSDL_URL_LIST, " | |||
| lv_if_def_name | TYPE SRT_WSP_DT_OBJ_NAME, " | |||
| lv_object_not_exists_exception | TYPE SRT_WSP_DT_OBJ_NAME, " | |||
| lv_technical_exception | TYPE SRT_WSP_DT_OBJ_NAME. " |
|   CALL FUNCTION 'GET_INTERFACE_WSDL' "Create URL for interface WSDL |
| EXPORTING | ||
| IF_DEF_NAME | = lv_if_def_name | |
| IMPORTING | ||
| RESULT | = lv_result | |
| EXCEPTIONS | ||
| OBJECT_NOT_EXISTS_EXCEPTION = 1 | ||
| TECHNICAL_EXCEPTION = 2 | ||
| . " GET_INTERFACE_WSDL | ||
ABAP code using 7.40 inline data declarations to call FM GET_INTERFACE_WSDL
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