SAP FIBKRU_ADD_LOG_ENTRY_BY_SYMSG Function Module for Add log entry by system message









FIBKRU_ADD_LOG_ENTRY_BY_SYMSG is a standard fibkru add log entry by symsg SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Add log entry by system message 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 fibkru add log entry by symsg FM, simply by entering the name FIBKRU_ADD_LOG_ENTRY_BY_SYMSG into the relevant SAP transaction such as SE37 or SE38.

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



Function FIBKRU_ADD_LOG_ENTRY_BY_SYMSG 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 'FIBKRU_ADD_LOG_ENTRY_BY_SYMSG'"Add log entry by system message
  EXPORTING
   IN_MSG_OBJ =  "Application Log: Object Name (Application Code)
*  IN_MSGNO =  "Message Number
*  IN_MSGID_DEFAULT = 'FIBK_RU_MO' "Message Class
*  IN_MSGNO_OWN =  "Message number if test is not from message class
   IN_LOG_HANDLE =  "Application Log: Log Handle
   IN_MSGTY =  "Message Type
*  IN_MSGID =  "Message Class
*  IN_MESSAGE =  "Message text if not from message class
*  IN_MSGV1 =  "Message Variable
*  IN_MSGV2 =  "Message Variable
*  IN_MSGV3 =  "Message Variable
*  IN_MSGV4 =  "Message Variable
.



IMPORTING Parameters details for FIBKRU_ADD_LOG_ENTRY_BY_SYMSG

IN_MSG_OBJ - Application Log: Object Name (Application Code)

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

IN_MSGNO - Message Number

Data type: SYMSGNO
Optional: Yes
Call by Reference: Yes

IN_MSGID_DEFAULT - Message Class

Data type: SYMSGID
Default: 'FIBK_RU_MO'
Optional: Yes
Call by Reference: Yes

IN_MSGNO_OWN - Message number if test is not from message class

Data type: CHAR3
Optional: Yes
Call by Reference: Yes

IN_LOG_HANDLE - Application Log: Log Handle

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

IN_MSGTY - Message Type

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

IN_MSGID - Message Class

Data type: SYMSGID
Optional: Yes
Call by Reference: Yes

IN_MESSAGE - Message text if not from message class

Data type: STRING
Optional: Yes
Call by Reference: Yes

IN_MSGV1 - Message Variable

Data type: SYMSGV
Optional: Yes
Call by Reference: Yes

IN_MSGV2 - Message Variable

Data type: SYMSGV
Optional: Yes
Call by Reference: Yes

IN_MSGV3 - Message Variable

Data type: SYMSGV
Optional: Yes
Call by Reference: Yes

IN_MSGV4 - Message Variable

Data type: SYMSGV
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for FIBKRU_ADD_LOG_ENTRY_BY_SYMSG 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_in_msg_obj  TYPE BALOBJ_D, "   
lv_in_msgno  TYPE SYMSGNO, "   
lv_in_msgid_default  TYPE SYMSGID, "   'FIBK_RU_MO'
lv_in_msgno_own  TYPE CHAR3, "   
lv_in_log_handle  TYPE BALLOGHNDL, "   
lv_in_msgty  TYPE SYMSGTY, "   
lv_in_msgid  TYPE SYMSGID, "   
lv_in_message  TYPE STRING, "   
lv_in_msgv1  TYPE SYMSGV, "   
lv_in_msgv2  TYPE SYMSGV, "   
lv_in_msgv3  TYPE SYMSGV, "   
lv_in_msgv4  TYPE SYMSGV. "   

  CALL FUNCTION 'FIBKRU_ADD_LOG_ENTRY_BY_SYMSG'  "Add log entry by system message
    EXPORTING
         IN_MSG_OBJ = lv_in_msg_obj
         IN_MSGNO = lv_in_msgno
         IN_MSGID_DEFAULT = lv_in_msgid_default
         IN_MSGNO_OWN = lv_in_msgno_own
         IN_LOG_HANDLE = lv_in_log_handle
         IN_MSGTY = lv_in_msgty
         IN_MSGID = lv_in_msgid
         IN_MESSAGE = lv_in_message
         IN_MSGV1 = lv_in_msgv1
         IN_MSGV2 = lv_in_msgv2
         IN_MSGV3 = lv_in_msgv3
         IN_MSGV4 = lv_in_msgv4
. " FIBKRU_ADD_LOG_ENTRY_BY_SYMSG




ABAP code using 7.40 inline data declarations to call FM FIBKRU_ADD_LOG_ENTRY_BY_SYMSG

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.

 
 
DATA(ld_in_msgid_default) = 'FIBK_RU_MO'.
 
 
 
 
 
 
 
 
 
 


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!