BRF_WHERE_USED SAP Function module

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

Associated Function Group: BRF_WHERE_USED
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM BRF_WHERE_USED - BRF WHERE USED

CALL FUNCTION 'BRF_WHERE_USED' "
  EXPORTING
    iv_brf_objid =              " brf_objid     BRF: Expression
    iv_brf_class_cat =          " brf_class_category  BRF: Category of Implementation Class
    iv_applclass =              " brf_applclass  BRF: Import Status
    iv_import_status = 'A'      " brf_import_status  BRF: Import Status
    iv_version = 0              " brf_version   BRF: Version
*   iv_wb_mode = '~'            " brf_boole_d   Called from Workbench Mode
*   iv_popup_mode = SPACE       " brf_boole_d   BRF: Space = False, 'X' = True
*   iv_confirm_use = SPACE      " brf_boole_d   BRF: Space = False, 'X' = True
* CHANGING
*   cv_confirm_use =            " brf_boole_d   BRF: Space = False, 'X' = True
    .  "  BRF_WHERE_USED

ABAP code example for Function Module BRF_WHERE_USED

The ABAP code below is a full code listing to execute function module BRF_WHERE_USED 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_cv_confirm_use) = 'Check type of data required'.

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

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

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

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

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

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

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

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

CALL FUNCTION 'BRF_WHERE_USED'
  EXPORTING
    iv_brf_objid =               ld_iv_brf_objid
    iv_brf_class_cat =           ld_iv_brf_class_cat
    iv_applclass =               ld_iv_applclass
    iv_import_status =           ld_iv_import_status
    iv_version =                 ld_iv_version
*   iv_wb_mode =                 ld_iv_wb_mode
*   iv_popup_mode =              ld_iv_popup_mode
*   iv_confirm_use =             ld_iv_confirm_use
* CHANGING
*   cv_confirm_use =             ld_cv_confirm_use
    .  "  BRF_WHERE_USED

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_cv_confirm_use
 
 TYPE BRF_BOOLE_D ,
ld_iv_brf_objid
 
 TYPE BRF_OBJID ,
ld_iv_brf_class_cat
 
 TYPE BRF_CLASS_CATEGORY ,
ld_iv_applclass
 
 TYPE BRF_APPLCLASS ,
ld_iv_import_status
 
 TYPE BRF_IMPORT_STATUS ,
ld_iv_version
 
 TYPE BRF_VERSION ,
ld_iv_wb_mode
 
 TYPE BRF_BOOLE_D ,
ld_iv_popup_mode
 
 TYPE BRF_BOOLE_D ,
ld_iv_confirm_use
 
 TYPE BRF_BOOLE_D .


ld_cv_confirm_use = 'Check type of data required'.
ld_iv_brf_objid = 'Check type of data required'.
ld_iv_brf_class_cat = 'Check type of data required'.
ld_iv_applclass = 'Check type of data required'.
ld_iv_import_status = 'Check type of data required'.
ld_iv_version = 'Check type of data required'.
ld_iv_wb_mode = 'Check type of data required'.
ld_iv_popup_mode = 'Check type of data required'.
ld_iv_confirm_use = 'Check type of data required'.