SAP BRF_MESSAGE_GET Function Module for









BRF_MESSAGE_GET is a standard brf message 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 brf message get FM, simply by entering the name BRF_MESSAGE_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: BRF_MAINTENANCE
Program Name: SAPLBRF_MAINTENANCE
Main Program: SAPLBRF_MAINTENANCE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BRF_MESSAGE_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 'BRF_MESSAGE_GET'"
IMPORTING
EV_MAX_SEVERITY = "Return Value, Return Value After ABAP Statements

TABLES
ET_MESSAGE = "BRF: Message
.



EXPORTING Parameters details for BRF_MESSAGE_GET

EV_MAX_SEVERITY - Return Value, Return Value After ABAP Statements

Data type: SYSUBRC
Optional: No
Call by Reference: Yes

TABLES Parameters details for BRF_MESSAGE_GET

ET_MESSAGE - BRF: Message

Data type: BRF_MESSAGE
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BRF_MESSAGE_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:
lt_et_message  TYPE STANDARD TABLE OF BRF_MESSAGE, "   
lv_ev_max_severity  TYPE SYSUBRC. "   

  CALL FUNCTION 'BRF_MESSAGE_GET'  "
    IMPORTING
         EV_MAX_SEVERITY = lv_ev_max_severity
    TABLES
         ET_MESSAGE = lt_et_message
. " BRF_MESSAGE_GET




ABAP code using 7.40 inline data declarations to call FM BRF_MESSAGE_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.

 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!