SAP Function Modules

comments icon Comments

G_RULE_ELEMENTS_GET SAP Function module







G_RULE_ELEMENTS_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name G_RULE_ELEMENTS_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: GBL6
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM G_RULE_ELEMENTS_GET - G RULE ELEMENTS GET 





CALL FUNCTION 'G_RULE_ELEMENTS_GET' "
  EXPORTING
*   bsubrules = 'X'             " gb01-bexclude  Check the subrules too.                  ('X')
    rule =                      " gb90-boolid   Rule to check
*   client = SY-MANDT           " sy-mandt      Desired client
  IMPORTING
    info_not_complete =         " gb01-bexclude  List not complete.  (User exit used...)
* TABLES
*   all_fields =                " dfies         List of fields found
*   all_rules =                 " gb90          List of rules  found
*   all_sets =                  " gbset_name    List of sets   found
*   all_exits =                 " gb922         List of exits  found
  EXCEPTIONS
    CHECK_FAILED = 1            "               Rule failed the check.
    NOT_FOUND = 2               "               Rule not found.
    .  "  G_RULE_ELEMENTS_GET

ABAP code example for Function Module G_RULE_ELEMENTS_GET





The ABAP code below is a full code listing to execute function module G_RULE_ELEMENTS_GET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_info_not_complete    TYPE GB01-BEXCLUDE
,
it_all_fields    TYPE STANDARD TABLE OF DFIES,"TABLES PARAM
wa_all_fields  LIKE LINE OF it_all_fields
,
it_all_rules    TYPE STANDARD TABLE OF GB90,"TABLES PARAM
wa_all_rules  LIKE LINE OF it_all_rules
,
it_all_sets    TYPE STANDARD TABLE OF GBSET_NAME,"TABLES PARAM
wa_all_sets  LIKE LINE OF it_all_sets
,
it_all_exits    TYPE STANDARD TABLE OF GB922,"TABLES PARAM
wa_all_exits  LIKE LINE OF it_all_exits
.



 

SELECT single BEXCLUDE 
  FROM GB01 
  INTO @DATA(ld_bsubrules).

 

SELECT single BOOLID 
  FROM GB90 
  INTO @DATA(ld_rule).


DATA(ld_client) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_all_fields to it_all_fields.
 

"populate fields of struture and append to itab
append wa_all_rules to it_all_rules.
 

"populate fields of struture and append to itab
append wa_all_sets to it_all_sets.
 

"populate fields of struture and append to itab
append wa_all_exits to it_all_exits.
.

CALL FUNCTION 'G_RULE_ELEMENTS_GET'
  EXPORTING
*   bsubrules =                  ld_bsubrules
    rule =                       ld_rule
*   client =                     ld_client
  IMPORTING
    info_not_complete =          ld_info_not_complete
* TABLES
*   all_fields =                 it_all_fields
*   all_rules =                  it_all_rules
*   all_sets =                   it_all_sets
*   all_exits =                  it_all_exits
  EXCEPTIONS
    CHECK_FAILED =               1
    NOT_FOUND =                  2
    .  "  G_RULE_ELEMENTS_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_info_not_complete  TYPE GB01-BEXCLUDE ,
ld_bsubrules  TYPE GB01-BEXCLUDE ,
it_all_fields  TYPE STANDARD TABLE OF DFIES ,
wa_all_fields  LIKE LINE OF it_all_fields,
ld_rule  TYPE GB90-BOOLID ,
it_all_rules  TYPE STANDARD TABLE OF GB90 ,
wa_all_rules  LIKE LINE OF it_all_rules,
ld_client  TYPE SY-MANDT ,
it_all_sets  TYPE STANDARD TABLE OF GBSET_NAME ,
wa_all_sets  LIKE LINE OF it_all_sets,
it_all_exits  TYPE STANDARD TABLE OF GB922 ,
wa_all_exits  LIKE LINE OF it_all_exits.





SELECT single BEXCLUDE 
  FROM GB01 
  INTO ld_bsubrules.
 

"populate fields of struture and append to itab
append wa_all_fields to it_all_fields.

SELECT single BOOLID 
  FROM GB90 
  INTO ld_rule.
 

"populate fields of struture and append to itab
append wa_all_rules to it_all_rules.
ld_client = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_all_sets to it_all_sets. 

"populate fields of struture and append to itab
append wa_all_exits to it_all_exits.

SAP Documentation for FM G_RULE_ELEMENTS_GET


This function can be used for the F4 help. It is independent of whether or not the new boolean routines are used or not. ...See here for full SAP fm documentation









Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name G_RULE_ELEMENTS_GET or its description.


   
 

G_RULE_ELEMENTS_GET - 
G_RP_RWE_IF_REPORT - 
G_RP_PROCESS_SETS - 
G_RP_PROCESS_LAYOUT - 
G_RP_GR31_SET_COPY_PARAMETERS - 
G_RP_FILTER_VARIABLES -