SAP G_BOOL_F4_USERS Function Module for









G_BOOL_F4_USERS is a standard g bool f4 users 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 g bool f4 users FM, simply by entering the name G_BOOL_F4_USERS into the relevant SAP transaction such as SE37 or SE38.

Function Group: GBL1
Program Name: SAPLGBL1
Main Program: SAPLGBL1
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function G_BOOL_F4_USERS 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 'G_BOOL_F4_USERS'"
EXPORTING
* DYNP_NR = ' ' "
* E_VALUSER = ' ' "
* PROG_NAME = ' ' "
* SUBSTITUTIONS = 'X' "
* VALIDATIONS = 'X' "
* VALUSERTXT_FLD = ' ' "
* VALUSER_FLD = ' ' "

IMPORTING
I_VALUSER = "
I_VALUSERTXT = "
.



IMPORTING Parameters details for G_BOOL_F4_USERS

DYNP_NR -

Data type: D020S-DNUM
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_VALUSER -

Data type: GB31-VALUSER
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

PROG_NAME -

Data type: D020S-PROG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

SUBSTITUTIONS -

Data type: GB01-BEXCLUDE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

VALIDATIONS -

Data type: GB01-BEXCLUDE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

VALUSERTXT_FLD -

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

VALUSER_FLD -

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

EXPORTING Parameters details for G_BOOL_F4_USERS

I_VALUSER -

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

I_VALUSERTXT -

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

Copy and paste ABAP code example for G_BOOL_F4_USERS 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_dynp_nr  TYPE D020S-DNUM, "   ' '
lv_i_valuser  TYPE GB31-VALUSER, "   
lv_e_valuser  TYPE GB31-VALUSER, "   ' '
lv_i_valusertxt  TYPE GB03T-VALUSERTXT, "   
lv_prog_name  TYPE D020S-PROG, "   ' '
lv_substitutions  TYPE GB01-BEXCLUDE, "   'X'
lv_validations  TYPE GB01-BEXCLUDE, "   'X'
lv_valusertxt_fld  TYPE GB01, "   ' '
lv_valuser_fld  TYPE GB01. "   ' '

  CALL FUNCTION 'G_BOOL_F4_USERS'  "
    EXPORTING
         DYNP_NR = lv_dynp_nr
         E_VALUSER = lv_e_valuser
         PROG_NAME = lv_prog_name
         SUBSTITUTIONS = lv_substitutions
         VALIDATIONS = lv_validations
         VALUSERTXT_FLD = lv_valusertxt_fld
         VALUSER_FLD = lv_valuser_fld
    IMPORTING
         I_VALUSER = lv_i_valuser
         I_VALUSERTXT = lv_i_valusertxt
. " G_BOOL_F4_USERS




ABAP code using 7.40 inline data declarations to call FM G_BOOL_F4_USERS

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 DNUM FROM D020S INTO @DATA(ld_dynp_nr).
DATA(ld_dynp_nr) = ' '.
 
"SELECT single VALUSER FROM GB31 INTO @DATA(ld_i_valuser).
 
"SELECT single VALUSER FROM GB31 INTO @DATA(ld_e_valuser).
DATA(ld_e_valuser) = ' '.
 
"SELECT single VALUSERTXT FROM GB03T INTO @DATA(ld_i_valusertxt).
 
"SELECT single PROG FROM D020S INTO @DATA(ld_prog_name).
DATA(ld_prog_name) = ' '.
 
"SELECT single BEXCLUDE FROM GB01 INTO @DATA(ld_substitutions).
DATA(ld_substitutions) = 'X'.
 
"SELECT single BEXCLUDE FROM GB01 INTO @DATA(ld_validations).
DATA(ld_validations) = 'X'.
 
DATA(ld_valusertxt_fld) = ' '.
 
DATA(ld_valuser_fld) = ' '.
 


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!