SAP SWU_GET_USER_FLAG Function Module for









SWU_GET_USER_FLAG is a standard swu get user flag 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 swu get user flag FM, simply by entering the name SWU_GET_USER_FLAG into the relevant SAP transaction such as SE37 or SE38.

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



Function SWU_GET_USER_FLAG 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 'SWU_GET_USER_FLAG'"
EXPORTING
* GPASPA = 'SWA' "
INDEX = "
* BIT_INDEX = '0' "

IMPORTING
FLAG = "
.



IMPORTING Parameters details for SWU_GET_USER_FLAG

GPASPA -

Data type: USR05-PARID
Default: 'SWA'
Optional: Yes
Call by Reference: No ( called with pass by value option)

INDEX -

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

BIT_INDEX -

Data type: SY-FDAYW
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SWU_GET_USER_FLAG

FLAG -

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

Copy and paste ABAP code example for SWU_GET_USER_FLAG 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_flag  TYPE SY-INPUT, "   
lv_gpaspa  TYPE USR05-PARID, "   'SWA'
lv_index  TYPE SY-TABIX, "   
lv_bit_index  TYPE SY-FDAYW. "   '0'

  CALL FUNCTION 'SWU_GET_USER_FLAG'  "
    EXPORTING
         GPASPA = lv_gpaspa
         INDEX = lv_index
         BIT_INDEX = lv_bit_index
    IMPORTING
         FLAG = lv_flag
. " SWU_GET_USER_FLAG




ABAP code using 7.40 inline data declarations to call FM SWU_GET_USER_FLAG

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 INPUT FROM SY INTO @DATA(ld_flag).
 
"SELECT single PARID FROM USR05 INTO @DATA(ld_gpaspa).
DATA(ld_gpaspa) = 'SWA'.
 
"SELECT single TABIX FROM SY INTO @DATA(ld_index).
 
"SELECT single FDAYW FROM SY INTO @DATA(ld_bit_index).
DATA(ld_bit_index) = '0'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!