SAP GET_BINDING_WSDL Function Module for Create URL for binding WSDL

Search SAP Function Modules

GET_BINDING_WSDL is a standard get binding 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 binding 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 binding wsdl FM, simply by entering the name GET_BINDING_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_BINDING_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_BINDING_WSDL'"Create URL for binding WSDL
  EXPORTING
*  RT_CONFIG_TYPE = 'SR' "WSP Configuration Type
   RT_CONFIG_NAME =  "WSP Name of RT Configuration
   IF_DEF_NAME =  "WSP Name of Interface Object
   BINDING_QNAME =  "Qualified Name

 IMPORTING
   RESULT =  "List of WSDL URLs

EXCEPTIONS
   OBJECT_NOT_EXISTS_EXCEPTION = 1    TECHNICAL_EXCEPTION = 2 

.

IMPORTING Parameters details for GET_BINDING_WSDL

RT_CONFIG_TYPE - WSP Configuration Type

Data type: SRT_WSP_CONFIG_TYPE
Default: 'SR'
Optional: Yes
Call by Reference: No ( called with pass by value option)

RT_CONFIG_NAME - WSP Name of RT Configuration

Data type: SRT_WSP_RT_CONFIG_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

IF_DEF_NAME - WSP Name of Interface Object

Data type: SRT_WSP_DT_OBJ_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

BINDING_QNAME - Qualified Name

Data type: QNAME
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for GET_BINDING_WSDL

RESULT - List of WSDL URLs

Data type: SRT_WSP_WSDL_URL_LIST
Optional: 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_BINDING_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.

ABAP code using 7.40 inline data declarations to call FM GET_BINDING_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