SAP G_BOOL_EXIST_SUBRULE Function Module for









G_BOOL_EXIST_SUBRULE is a standard g bool exist subrule 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 exist subrule FM, simply by entering the name G_BOOL_EXIST_SUBRULE 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_EXIST_SUBRULE 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_EXIST_SUBRULE'"
EXPORTING
RULE_NAME = "Rule name
* VALEVENT = ' ' "
* VALUSER = ' ' "
* CLIENT = SY-MANDT "

IMPORTING
VALEVENT_FND = "
VALUSER_FND = "
RULE_AUTHGR = "
RULE_BCLASS = "

EXCEPTIONS
NOT_FOUND = 1 NULL_RULE = 2 WRONG_CLASS = 3
.



IMPORTING Parameters details for G_BOOL_EXIST_SUBRULE

RULE_NAME - Rule name

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

VALEVENT -

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

VALUSER -

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

CLIENT -

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

EXPORTING Parameters details for G_BOOL_EXIST_SUBRULE

VALEVENT_FND -

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

VALUSER_FND -

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

RULE_AUTHGR -

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

RULE_BCLASS -

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

EXCEPTIONS details

NOT_FOUND - Rule does not exist.

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

NULL_RULE - Rule name is blank.

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

WRONG_CLASS -

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

Copy and paste ABAP code example for G_BOOL_EXIST_SUBRULE 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_not_found  TYPE STRING, "   
lv_rule_name  TYPE STRING, "   
lv_valevent_fnd  TYPE GB31-VALEVENT, "   
lv_valevent  TYPE GB31-VALEVENT, "   ' '
lv_null_rule  TYPE GB31, "   
lv_valuser_fnd  TYPE GB31-VALUSER, "   
lv_valuser  TYPE GB31-VALUSER, "   ' '
lv_rule_authgr  TYPE GB90-AUTHGR, "   
lv_wrong_class  TYPE GB90, "   
lv_client  TYPE SY-MANDT, "   SY-MANDT
lv_rule_bclass  TYPE GB90-CLASSID. "   

  CALL FUNCTION 'G_BOOL_EXIST_SUBRULE'  "
    EXPORTING
         RULE_NAME = lv_rule_name
         VALEVENT = lv_valevent
         VALUSER = lv_valuser
         CLIENT = lv_client
    IMPORTING
         VALEVENT_FND = lv_valevent_fnd
         VALUSER_FND = lv_valuser_fnd
         RULE_AUTHGR = lv_rule_authgr
         RULE_BCLASS = lv_rule_bclass
    EXCEPTIONS
        NOT_FOUND = 1
        NULL_RULE = 2
        WRONG_CLASS = 3
. " G_BOOL_EXIST_SUBRULE




ABAP code using 7.40 inline data declarations to call FM G_BOOL_EXIST_SUBRULE

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 VALEVENT FROM GB31 INTO @DATA(ld_valevent_fnd).
 
"SELECT single VALEVENT FROM GB31 INTO @DATA(ld_valevent).
DATA(ld_valevent) = ' '.
 
 
"SELECT single VALUSER FROM GB31 INTO @DATA(ld_valuser_fnd).
 
"SELECT single VALUSER FROM GB31 INTO @DATA(ld_valuser).
DATA(ld_valuser) = ' '.
 
"SELECT single AUTHGR FROM GB90 INTO @DATA(ld_rule_authgr).
 
 
"SELECT single MANDT FROM SY INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
"SELECT single CLASSID FROM GB90 INTO @DATA(ld_rule_bclass).
 


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!