SAP CBRC_LIB_MSG_LEV_GET Function Module for NOTRANSL: Lesen der aktuellen Detaillierungslevels für Meldungen
CBRC_LIB_MSG_LEV_GET is a standard cbrc lib msg lev get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Lesen der aktuellen Detaillierungslevels für Meldungen processing and below is the pattern details for this FM, 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 cbrc lib msg lev get FM, simply by entering the name CBRC_LIB_MSG_LEV_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: CBRC_LIB
Program Name: SAPLCBRC_LIB
Main Program: SAPLCBRC_LIB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CBRC_LIB_MSG_LEV_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 'CBRC_LIB_MSG_LEV_GET'"NOTRANSL: Lesen der aktuellen Detaillierungslevels für Meldungen.
EXPORTING
* I_RFCDEST = "RFC Connection
IMPORTING
E_LEV_MSG = "Application Log: Level of Detail
IMPORTING Parameters details for CBRC_LIB_MSG_LEV_GET
I_RFCDEST - RFC Connection
Data type: RFCDESTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CBRC_LIB_MSG_LEV_GET
E_LEV_MSG - Application Log: Level of Detail
Data type: BALMI-DETLEVELOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CBRC_LIB_MSG_LEV_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: | ||||
| lv_e_lev_msg | TYPE BALMI-DETLEVEL, " | |||
| lv_i_rfcdest | TYPE RFCDEST. " |
|   CALL FUNCTION 'CBRC_LIB_MSG_LEV_GET' "NOTRANSL: Lesen der aktuellen Detaillierungslevels für Meldungen |
| EXPORTING | ||
| I_RFCDEST | = lv_i_rfcdest | |
| IMPORTING | ||
| E_LEV_MSG | = lv_e_lev_msg | |
| . " CBRC_LIB_MSG_LEV_GET | ||
ABAP code using 7.40 inline data declarations to call FM CBRC_LIB_MSG_LEV_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.| "SELECT single DETLEVEL FROM BALMI INTO @DATA(ld_e_lev_msg). | ||||
Search for further information about these or an SAP related objects