SAP K41C_RUN_ID_PROTOCOL_DISPLAY Function Module for Display Message Log









K41C_RUN_ID_PROTOCOL_DISPLAY is a standard k41c run id protocol display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Message 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 k41c run id protocol display FM, simply by entering the name K41C_RUN_ID_PROTOCOL_DISPLAY into the relevant SAP transaction such as SE37 or SE38.

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



Function K41C_RUN_ID_PROTOCOL_DISPLAY 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 'K41C_RUN_ID_PROTOCOL_DISPLAY'"Display Message Log
EXPORTING
* ID_RUN_ID = "
* ID_LOGHANDLE = "Application Log: Log Handle
ID_CALLBACK_PROG = "
* ID_CALLBACK_FORM = 'POST_AFTER_TEST_RUN' "Application Log: Callback: Routine Name
* ID_CALLBACK_TYPE = ' ' "Application Log: Callback: Type (Ext. Perform, FM, etc.)
* ID_AMODAL = 'X' "
* ID_TEST = ' ' "
* ID_STOP = 'X' "

EXCEPTIONS
ERROR_IN_LOGFILE = 1 NO_PROTOCOL_FOUND = 2
.



IMPORTING Parameters details for K41C_RUN_ID_PROTOCOL_DISPLAY

ID_RUN_ID -

Data type: GUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_LOGHANDLE - Application Log: Log Handle

Data type: BALLOGHNDL
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_CALLBACK_PROG -

Data type: SYREPID
Optional: No
Call by Reference: No ( called with pass by value option)

ID_CALLBACK_FORM - Application Log: Callback: Routine Name

Data type: BALUEF
Default: 'POST_AFTER_TEST_RUN'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_CALLBACK_TYPE - Application Log: Callback: Type (Ext. Perform, FM, etc.)

Data type: BALUET
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_AMODAL -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_TEST -

Data type: BOOLE_D
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ID_STOP -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR_IN_LOGFILE -

Data type:
Optional: No
Call by Reference: Yes

NO_PROTOCOL_FOUND - No Error Log Exists

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for K41C_RUN_ID_PROTOCOL_DISPLAY 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_id_run_id  TYPE GUID, "   
lv_error_in_logfile  TYPE GUID, "   
lv_id_loghandle  TYPE BALLOGHNDL, "   
lv_no_protocol_found  TYPE BALLOGHNDL, "   
lv_id_callback_prog  TYPE SYREPID, "   
lv_id_callback_form  TYPE BALUEF, "   'POST_AFTER_TEST_RUN'
lv_id_callback_type  TYPE BALUET, "   SPACE
lv_id_amodal  TYPE BOOLE_D, "   'X'
lv_id_test  TYPE BOOLE_D, "   SPACE
lv_id_stop  TYPE BOOLE_D. "   'X'

  CALL FUNCTION 'K41C_RUN_ID_PROTOCOL_DISPLAY'  "Display Message Log
    EXPORTING
         ID_RUN_ID = lv_id_run_id
         ID_LOGHANDLE = lv_id_loghandle
         ID_CALLBACK_PROG = lv_id_callback_prog
         ID_CALLBACK_FORM = lv_id_callback_form
         ID_CALLBACK_TYPE = lv_id_callback_type
         ID_AMODAL = lv_id_amodal
         ID_TEST = lv_id_test
         ID_STOP = lv_id_stop
    EXCEPTIONS
        ERROR_IN_LOGFILE = 1
        NO_PROTOCOL_FOUND = 2
. " K41C_RUN_ID_PROTOCOL_DISPLAY




ABAP code using 7.40 inline data declarations to call FM K41C_RUN_ID_PROTOCOL_DISPLAY

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_id_callback_form) = 'POST_AFTER_TEST_RUN'.
 
DATA(ld_id_callback_type) = ' '.
 
DATA(ld_id_amodal) = 'X'.
 
DATA(ld_id_test) = ' '.
 
DATA(ld_id_stop) = 'X'.
 


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!