SAP CBRC_LIB_TRANS_CHECK Function Module for NOTRANSL: Prüfung von Transaktion Filter Bedingungen
CBRC_LIB_TRANS_CHECK is a standard cbrc lib trans check 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: Prüfung von Transaktion Filter Bedingungen 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 trans check FM, simply by entering the name CBRC_LIB_TRANS_CHECK 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): Normal Function Module
Update:

Function CBRC_LIB_TRANS_CHECK 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_TRANS_CHECK'"NOTRANSL: Prüfung von Transaktion Filter Bedingungen.
EXPORTING
I_REG = "Regulatory List
I_SCEN = "Scenario
IMPORTING
E_FLG_RELEVANT = "Truth Value
IMPORTING Parameters details for CBRC_LIB_TRANS_CHECK
I_REG - Regulatory List
Data type: ESESLSTIDOptional: No
Call by Reference: Yes
I_SCEN - Scenario
Data type: CCRCE_SCENOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CBRC_LIB_TRANS_CHECK
E_FLG_RELEVANT - Truth Value
Data type: ESEBOOLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CBRC_LIB_TRANS_CHECK 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_i_reg | TYPE ESESLSTID, " | |||
| lv_e_flg_relevant | TYPE ESEBOOLE, " | |||
| lv_i_scen | TYPE CCRCE_SCEN. " |
|   CALL FUNCTION 'CBRC_LIB_TRANS_CHECK' "NOTRANSL: Prüfung von Transaktion Filter Bedingungen |
| EXPORTING | ||
| I_REG | = lv_i_reg | |
| I_SCEN | = lv_i_scen | |
| IMPORTING | ||
| E_FLG_RELEVANT | = lv_e_flg_relevant | |
| . " CBRC_LIB_TRANS_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM CBRC_LIB_TRANS_CHECK
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