SAP FIBKRU_START_LOG Function Module for Strat logging messages
FIBKRU_START_LOG is a standard fibkru start log SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Strat logging messages 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 start log FM, simply by entering the name FIBKRU_START_LOG 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_START_LOG 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_START_LOG'"Strat logging messages.
EXPORTING
IN_MSG_OBJ = "Application Log: Object Name (Application Code)
IMPORTING
OUT_BEGDATE = "Current Date of Application Server
OUT_BEGTIME = "Current Time of Application Server
CHANGING
C_LOG_HANDLE = "Application Log: Log Handle
IMPORTING Parameters details for FIBKRU_START_LOG
IN_MSG_OBJ - Application Log: Object Name (Application Code)
Data type: BALOBJ_DOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FIBKRU_START_LOG
OUT_BEGDATE - Current Date of Application Server
Data type: SYDATUMOptional: No
Call by Reference: Yes
OUT_BEGTIME - Current Time of Application Server
Data type: SYUZEITOptional: No
Call by Reference: Yes
CHANGING Parameters details for FIBKRU_START_LOG
C_LOG_HANDLE - Application Log: Log Handle
Data type: BALLOGHNDLOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FIBKRU_START_LOG 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_out_begdate | TYPE SYDATUM, " | |||
| lv_c_log_handle | TYPE BALLOGHNDL, " | |||
| lv_out_begtime | TYPE SYUZEIT. " |
|   CALL FUNCTION 'FIBKRU_START_LOG' "Strat logging messages |
| EXPORTING | ||
| IN_MSG_OBJ | = lv_in_msg_obj | |
| IMPORTING | ||
| OUT_BEGDATE | = lv_out_begdate | |
| OUT_BEGTIME | = lv_out_begtime | |
| CHANGING | ||
| C_LOG_HANDLE | = lv_c_log_handle | |
| . " FIBKRU_START_LOG | ||
ABAP code using 7.40 inline data declarations to call FM FIBKRU_START_LOG
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