SAP SWD_EDIT_BLOCK_BINDING Function Module for

Search SAP Function Modules

SWD_EDIT_BLOCK_BINDING is a standard swd edit block binding 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 edit block binding FM, simply by entering the name SWD_EDIT_BLOCK_BINDING into the relevant SAP transaction such as SE37 or SE38.

Function Group: SWDI
Program Name: SAPLSWDI
Main Program: SAPLSWDI
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SWD_EDIT_BLOCK_BINDING 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_EDIT_BLOCK_BINDING'"
  EXPORTING
*  IM_DISPLAY = ' ' "
*  IM_PARFOROBJ = ' ' "
*  IM_STEP_DESCRIPT =  "
   IM_BLOCK_CONTAINER =  "
   IM_CONTAINER =  "
*  IM_BINDTYPE =  "

 IMPORTING
   EX_CHANGED =  "

TABLES
   CH_BINDING =  "

EXCEPTIONS
   ERROR = 1 

.

IMPORTING Parameters details for SWD_EDIT_BLOCK_BINDING

IM_DISPLAY -

Data type: SWD_DATA-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_PARFOROBJ -

Data type: SWD_ASTEP-PARFOROBJ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_STEP_DESCRIPT -

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

IM_BLOCK_CONTAINER -

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

IM_CONTAINER -

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

IM_BINDTYPE -

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

EXPORTING Parameters details for SWD_EDIT_BLOCK_BINDING

EX_CHANGED -

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

TABLES Parameters details for SWD_EDIT_BLOCK_BINDING

CH_BINDING -

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

EXCEPTIONS details

ERROR -

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

Copy and paste ABAP code example for SWD_EDIT_BLOCK_BINDING 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 SWD_EDIT_BLOCK_BINDING

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