SAP CBRC_LIB_MSG_WRITE_COMPLETE Function Module for NOTRANSL: EHS: Schreiben der Sperrmeldung ins Application-Log
CBRC_LIB_MSG_WRITE_COMPLETE is a standard cbrc lib msg write complete 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: EHS: Schreiben der Sperrmeldung ins Application-Log 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 write complete FM, simply by entering the name CBRC_LIB_MSG_WRITE_COMPLETE 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_MSG_WRITE_COMPLETE 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_WRITE_COMPLETE'"NOTRANSL: EHS: Schreiben der Sperrmeldung ins Application-Log.
EXPORTING
I_OBJKY = "Object Key
* I_UNAME = "SAP System, User Logon Name
I_TCODE = "ABAP Program, Current Transaction Code
I_REPID = "ABAP Program: Current Main Program
I_OBJECT = "Application Log: Object Name (Application Code)
I_SUBOBJECT = "Application Log: Subobject
TABLES
I_MSG_TAB = "Application Log: APPL_LOG_WRITE_MESSAGES interface
EXCEPTIONS
LOG_WRITE_FAILED = 1
IMPORTING Parameters details for CBRC_LIB_MSG_WRITE_COMPLETE
I_OBJKY - Object Key
Data type: NAST-OBJKYOptional: No
Call by Reference: No ( called with pass by value option)
I_UNAME - SAP System, User Logon Name
Data type: SY-UNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TCODE - ABAP Program, Current Transaction Code
Data type: SY-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
I_REPID - ABAP Program: Current Main Program
Data type: SY-REPIDOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJECT - Application Log: Object Name (Application Code)
Data type: BALHDRI-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
I_SUBOBJECT - Application Log: Subobject
Data type: BALHDRI-SUBOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CBRC_LIB_MSG_WRITE_COMPLETE
I_MSG_TAB - Application Log: APPL_LOG_WRITE_MESSAGES interface
Data type: BALMIOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LOG_WRITE_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CBRC_LIB_MSG_WRITE_COMPLETE 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_objky | TYPE NAST-OBJKY, " | |||
| lt_i_msg_tab | TYPE STANDARD TABLE OF BALMI, " | |||
| lv_log_write_failed | TYPE BALMI, " | |||
| lv_i_uname | TYPE SY-UNAME, " | |||
| lv_i_tcode | TYPE SY-TCODE, " | |||
| lv_i_repid | TYPE SY-REPID, " | |||
| lv_i_object | TYPE BALHDRI-OBJECT, " | |||
| lv_i_subobject | TYPE BALHDRI-SUBOBJECT. " |
|   CALL FUNCTION 'CBRC_LIB_MSG_WRITE_COMPLETE' "NOTRANSL: EHS: Schreiben der Sperrmeldung ins Application-Log |
| EXPORTING | ||
| I_OBJKY | = lv_i_objky | |
| I_UNAME | = lv_i_uname | |
| I_TCODE | = lv_i_tcode | |
| I_REPID | = lv_i_repid | |
| I_OBJECT | = lv_i_object | |
| I_SUBOBJECT | = lv_i_subobject | |
| TABLES | ||
| I_MSG_TAB | = lt_i_msg_tab | |
| EXCEPTIONS | ||
| LOG_WRITE_FAILED = 1 | ||
| . " CBRC_LIB_MSG_WRITE_COMPLETE | ||
ABAP code using 7.40 inline data declarations to call FM CBRC_LIB_MSG_WRITE_COMPLETE
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 OBJKY FROM NAST INTO @DATA(ld_i_objky). | ||||
| "SELECT single UNAME FROM SY INTO @DATA(ld_i_uname). | ||||
| "SELECT single TCODE FROM SY INTO @DATA(ld_i_tcode). | ||||
| "SELECT single REPID FROM SY INTO @DATA(ld_i_repid). | ||||
| "SELECT single OBJECT FROM BALHDRI INTO @DATA(ld_i_object). | ||||
| "SELECT single SUBOBJECT FROM BALHDRI INTO @DATA(ld_i_subobject). | ||||
Search for further information about these or an SAP related objects