SAP SWD_GET_WORKFLOW_BINDINGS Function Module for
SWD_GET_WORKFLOW_BINDINGS is a standard swd get workflow bindings SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 swd get workflow bindings FM, simply by entering the name SWD_GET_WORKFLOW_BINDINGS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWDB_RUNTIME
Program Name: SAPLSWDB_RUNTIME
Main Program: SAPLSWDB_RUNTIME
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SWD_GET_WORKFLOW_BINDINGS 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 'SWD_GET_WORKFLOW_BINDINGS'".
EXPORTING
ACT_TASK = "
ACT_WFDKEY = "
* ACT_SOURCE_CLIENT = SY-MANDT "
* BUFFERED_ACCESS_FORCED = ' ' "
TABLES
BINDING_DATA = "
EXCEPTIONS
INTERNAL_NOT_FOUND = 1 INVALID_OBJECT_TYPE = 2
IMPORTING Parameters details for SWD_GET_WORKFLOW_BINDINGS
ACT_TASK -
Data type: SWD_AHEAD-TASKOptional: No
Call by Reference: No ( called with pass by value option)
ACT_WFDKEY -
Data type: SWD_WFDKEYOptional: No
Call by Reference: No ( called with pass by value option)
ACT_SOURCE_CLIENT -
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
BUFFERED_ACCESS_FORCED -
Data type: SY-INPUTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SWD_GET_WORKFLOW_BINDINGS
BINDING_DATA -
Data type: SWD_BINDEFOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INTERNAL_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_OBJECT_TYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SWD_GET_WORKFLOW_BINDINGS 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_act_task | TYPE SWD_AHEAD-TASK, " | |||
| lt_binding_data | TYPE STANDARD TABLE OF SWD_BINDEF, " | |||
| lv_internal_not_found | TYPE SWD_BINDEF, " | |||
| lv_act_wfdkey | TYPE SWD_WFDKEY, " | |||
| lv_invalid_object_type | TYPE SWD_WFDKEY, " | |||
| lv_act_source_client | TYPE SY-MANDT, " SY-MANDT | |||
| lv_buffered_access_forced | TYPE SY-INPUT. " SPACE |
|   CALL FUNCTION 'SWD_GET_WORKFLOW_BINDINGS' " |
| EXPORTING | ||
| ACT_TASK | = lv_act_task | |
| ACT_WFDKEY | = lv_act_wfdkey | |
| ACT_SOURCE_CLIENT | = lv_act_source_client | |
| BUFFERED_ACCESS_FORCED | = lv_buffered_access_forced | |
| TABLES | ||
| BINDING_DATA | = lt_binding_data | |
| EXCEPTIONS | ||
| INTERNAL_NOT_FOUND = 1 | ||
| INVALID_OBJECT_TYPE = 2 | ||
| . " SWD_GET_WORKFLOW_BINDINGS | ||
ABAP code using 7.40 inline data declarations to call FM SWD_GET_WORKFLOW_BINDINGS
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 TASK FROM SWD_AHEAD INTO @DATA(ld_act_task). | ||||
| "SELECT single MANDT FROM SY INTO @DATA(ld_act_source_client). | ||||
| DATA(ld_act_source_client) | = SY-MANDT. | |||
| "SELECT single INPUT FROM SY INTO @DATA(ld_buffered_access_forced). | ||||
| DATA(ld_buffered_access_forced) | = ' '. | |||
Search for further information about these or an SAP related objects