SAP G_SUBRULE_GET Function Module for
G_SUBRULE_GET is a standard g subrule get 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 subrule get FM, simply by entering the name G_SUBRULE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: GBLO
Program Name: SAPLGBLO
Main Program: SAPLGBLO
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function G_SUBRULE_GET 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_SUBRULE_GET'".
EXPORTING
* BOOLID_SUGGESTED = ' ' "Last choice for the rule name
* SUBRULE_EVENT = ' ' "Event
SUBRULE_USER = "Rule user
* VIEW_ONLY = ' ' "Only display ('X')
IMPORTING
BOOLID_SELECTED = "New choice for the rule name
EXCEPTIONS
NONE_SELECTED = 1 NO_CHANGE = 2
IMPORTING Parameters details for G_SUBRULE_GET
BOOLID_SUGGESTED - Last choice for the rule name
Data type: GB90-BOOLIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SUBRULE_EVENT - Event
Data type: GB31-VALEVENTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SUBRULE_USER - Rule user
Data type: GB03-VALUSEROptional: No
Call by Reference: No ( called with pass by value option)
VIEW_ONLY - Only display ('X')
Data type: GB01-BEXCLUDEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for G_SUBRULE_GET
BOOLID_SELECTED - New choice for the rule name
Data type: GB90-BOOLIDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NONE_SELECTED - None selected
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_CHANGE - No change
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for G_SUBRULE_GET 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_none_selected | TYPE STRING, " | |||
| lv_boolid_selected | TYPE GB90-BOOLID, " | |||
| lv_boolid_suggested | TYPE GB90-BOOLID, " SPACE | |||
| lv_no_change | TYPE GB90, " | |||
| lv_subrule_event | TYPE GB31-VALEVENT, " SPACE | |||
| lv_subrule_user | TYPE GB03-VALUSER, " | |||
| lv_view_only | TYPE GB01-BEXCLUDE. " SPACE |
|   CALL FUNCTION 'G_SUBRULE_GET' " |
| EXPORTING | ||
| BOOLID_SUGGESTED | = lv_boolid_suggested | |
| SUBRULE_EVENT | = lv_subrule_event | |
| SUBRULE_USER | = lv_subrule_user | |
| VIEW_ONLY | = lv_view_only | |
| IMPORTING | ||
| BOOLID_SELECTED | = lv_boolid_selected | |
| EXCEPTIONS | ||
| NONE_SELECTED = 1 | ||
| NO_CHANGE = 2 | ||
| . " G_SUBRULE_GET | ||
ABAP code using 7.40 inline data declarations to call FM G_SUBRULE_GET
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 BOOLID FROM GB90 INTO @DATA(ld_boolid_selected). | ||||
| "SELECT single BOOLID FROM GB90 INTO @DATA(ld_boolid_suggested). | ||||
| DATA(ld_boolid_suggested) | = ' '. | |||
| "SELECT single VALEVENT FROM GB31 INTO @DATA(ld_subrule_event). | ||||
| DATA(ld_subrule_event) | = ' '. | |||
| "SELECT single VALUSER FROM GB03 INTO @DATA(ld_subrule_user). | ||||
| "SELECT single BEXCLUDE FROM GB01 INTO @DATA(ld_view_only). | ||||
| DATA(ld_view_only) | = ' '. | |||
Search for further information about these or an SAP related objects