FMCA_BRF_MSG_SELECT SAP Function module

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

Associated Function Group: FMCA_BRF_MSG
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM FMCA_BRF_MSG_SELECT - FMCA BRF MSG SELECT

CALL FUNCTION 'FMCA_BRF_MSG_SELECT' "
* EXPORTING
*   i_return_id =               " scmg_case_guid  Technical Key of Case (Case GUID)
*   i_form_id =                 " scmg_case_guid  Technical Key of Case (Case GUID)
*   i_rt_msgty =                " bal_r_msty    Application Log: MSGTY Range Table
*   i_rt_status =               " fmca_rt_msgstatus
*   iv_bypass_buffer = 'X'      " xfeld         Checkbox
  IMPORTING
    et_fmca_brf_msg =           " fmca_brf_msg_t  Tax Calculation and Validation: Table Error Messages
    .  "  FMCA_BRF_MSG_SELECT

ABAP code example for Function Module FMCA_BRF_MSG_SELECT

The ABAP code below is a full code listing to execute function module FMCA_BRF_MSG_SELECT 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_et_fmca_brf_msg  
 
 TYPE FMCA_BRF_MSG_T
.


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

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

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

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

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

CALL FUNCTION 'FMCA_BRF_MSG_SELECT'
* EXPORTING
*   i_return_id =                ld_i_return_id
*   i_form_id =                  ld_i_form_id
*   i_rt_msgty =                 ld_i_rt_msgty
*   i_rt_status =                ld_i_rt_status
*   iv_bypass_buffer =           ld_iv_bypass_buffer
  IMPORTING
    et_fmca_brf_msg =            ld_et_fmca_brf_msg
    .  "  FMCA_BRF_MSG_SELECT

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_et_fmca_brf_msg
 
 TYPE FMCA_BRF_MSG_T ,
ld_i_return_id
 
 TYPE SCMG_CASE_GUID ,
ld_i_form_id
 
 TYPE SCMG_CASE_GUID ,
ld_i_rt_msgty
 
 TYPE BAL_R_MSTY ,
ld_i_rt_status
 
 TYPE FMCA_RT_MSGSTATUS ,
ld_iv_bypass_buffer
 
 TYPE XFELD .


ld_i_return_id = 'Check type of data required'.
ld_i_form_id = 'Check type of data required'.
ld_i_rt_msgty = 'Check type of data required'.
ld_i_rt_status = 'Check type of data required'.
ld_iv_bypass_buffer = 'Check type of data required'.