SAP SWF_BND_GET_USER_OPTIONS Function Module for
SWF_BND_GET_USER_OPTIONS is a standard swf bnd get user options 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 swf bnd get user options FM, simply by entering the name SWF_BND_GET_USER_OPTIONS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWF_BND
Program Name: SAPLSWF_BND
Main Program: SAPLSWF_BND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SWF_BND_GET_USER_OPTIONS 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 'SWF_BND_GET_USER_OPTIONS'".
EXPORTING
* CLIENT = SY-MANDT "R/3 System, Client Number from Logon
* USERNAME = SY-UNAME "SAP System, User Logon Name
IMPORTING
OPTIONS = "Options for Setting Parameters of the Binding Editor
IMPORTING Parameters details for SWF_BND_GET_USER_OPTIONS
CLIENT - R/3 System, Client Number from Logon
Data type: SYMANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: Yes
USERNAME - SAP System, User Logon Name
Data type: SYUNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SWF_BND_GET_USER_OPTIONS
OPTIONS - Options for Setting Parameters of the Binding Editor
Data type: SWFBNDSOPTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SWF_BND_GET_USER_OPTIONS 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_client | TYPE SYMANDT, " SY-MANDT | |||
| lv_options | TYPE SWFBNDSOPT, " | |||
| lv_username | TYPE SYUNAME. " SY-UNAME |
|   CALL FUNCTION 'SWF_BND_GET_USER_OPTIONS' " |
| EXPORTING | ||
| CLIENT | = lv_client | |
| USERNAME | = lv_username | |
| IMPORTING | ||
| OPTIONS | = lv_options | |
| . " SWF_BND_GET_USER_OPTIONS | ||
ABAP code using 7.40 inline data declarations to call FM SWF_BND_GET_USER_OPTIONS
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.| DATA(ld_client) | = SY-MANDT. | |||
| DATA(ld_username) | = SY-UNAME. | |||
Search for further information about these or an SAP related objects