BM_CHECK_OBJECT SAP Function module - Check object attributes

BM_CHECK_OBJECT 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 BM_CHECK_OBJECT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SF22
Released Date: 04.12.1996
Processing type: Normal fucntion module

Pattern for FM BM_CHECK_OBJECT - BM CHECK OBJECT

CALL FUNCTION 'BM_CHECK_OBJECT' "Check object attributes
* EXPORTING
*   events =                    " bmt_events
*   functions =                 " bmt_functions
*   function_ranges =           " bmt_function_ranges
*   scenarios =                 " bmt_scenarios
*   entorgtyps =                " bmt_entorgtyps
*   groups =                    " bmt_groups
  TABLES
    errors =                    " rpygser
  CHANGING
    error_occured =             " rpygsgf-err_exist
    .  "  BM_CHECK_OBJECT

ABAP code example for Function Module BM_CHECK_OBJECT

The ABAP code below is a full code listing to execute function module BM_CHECK_OBJECT 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:
it_errors  
 
 TYPE STANDARD TABLE OF RPYGSER,"TABLES PARAM
wa_errors
 
 LIKE LINE OF it_errors
.



DATA(ld_error_occured) = some text here

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

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

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

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

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

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

"populate fields of struture and append to itab
append wa_errors to it_errors.
.

CALL FUNCTION 'BM_CHECK_OBJECT'
* EXPORTING
*   events =                     ld_events
*   functions =                  ld_functions
*   function_ranges =            ld_function_ranges
*   scenarios =                  ld_scenarios
*   entorgtyps =                 ld_entorgtyps
*   groups =                     ld_groups
  TABLES
    errors =                     it_errors
  CHANGING
    error_occured =              ld_error_occured
    .  "  BM_CHECK_OBJECT

IF SY-SUBRC EQ 0.
  "All OK
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_error_occured
 
 TYPE RPYGSGF-ERR_EXIST ,
ld_events
 
 TYPE BMT_EVENTS ,
it_errors
 
 TYPE STANDARD TABLE OF RPYGSER ,
wa_errors
 
 LIKE LINE OF it_errors,
ld_functions
 
 TYPE BMT_FUNCTIONS ,
ld_function_ranges
 
 TYPE BMT_FUNCTION_RANGES ,
ld_scenarios
 
 TYPE BMT_SCENARIOS ,
ld_entorgtyps
 
 TYPE BMT_ENTORGTYPS ,
ld_groups
 
 TYPE BMT_GROUPS .



ld_error_occured = some text here
ld_events = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_errors to it_errors.
ld_functions = 'Check type of data required'.
ld_function_ranges = 'Check type of data required'.
ld_scenarios = 'Check type of data required'.
ld_entorgtyps = 'Check type of data required'.
ld_groups = 'Check type of data required'.