SAP CK_F_MSGPROTOCOL_LINE_APPEND Function Module for









CK_F_MSGPROTOCOL_LINE_APPEND is a standard ck f msgprotocol line append SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ck f msgprotocol line append FM, simply by entering the name CK_F_MSGPROTOCOL_LINE_APPEND into the relevant SAP transaction such as SE37 or SE38.

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



Function CK_F_MSGPROTOCOL_LINE_APPEND 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 'CK_F_MSGPROTOCOL_LINE_APPEND'"
  EXPORTING
   P_MSGID =  "
   P_MSGTY =  "
   P_MSGNO =  "
*  P_MSGV1 = ' ' "
*  P_MSGV2 = ' ' "
*  P_MSGV3 = ' ' "
*  P_MSGV4 = ' ' "
*  P_DEF_SERIOUS_ERROR = 'E' "
   P_NAME_OF_PROGRAM =  "

CHANGING
*  P_SERIOUS_ERROR_OCCURED =  "

TABLES
   P_MSGPROTOKOLL =  "
.



IMPORTING Parameters details for CK_F_MSGPROTOCOL_LINE_APPEND

P_MSGID -

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

P_MSGTY -

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

P_MSGNO -

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

P_MSGV1 -

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

P_MSGV2 -

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

P_MSGV3 -

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

P_MSGV4 -

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

P_DEF_SERIOUS_ERROR -

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

P_NAME_OF_PROGRAM -

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

CHANGING Parameters details for CK_F_MSGPROTOCOL_LINE_APPEND

P_SERIOUS_ERROR_OCCURED -

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

TABLES Parameters details for CK_F_MSGPROTOCOL_LINE_APPEND

P_MSGPROTOKOLL -

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

Copy and paste ABAP code example for CK_F_MSGPROTOCOL_LINE_APPEND 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_p_msgid  TYPE SYMSGID, "   
lt_p_msgprotokoll  TYPE STANDARD TABLE OF CMFMSG, "   
lv_p_serious_error_occured  TYPE C, "   
lv_p_msgty  TYPE SYMSGTY, "   
lv_p_msgno  TYPE SYMSGNO, "   
lv_p_msgv1  TYPE SYMSGV, "   SPACE
lv_p_msgv2  TYPE SYMSGV, "   SPACE
lv_p_msgv3  TYPE SYMSGV, "   SPACE
lv_p_msgv4  TYPE SYMSGV, "   SPACE
lv_p_def_serious_error  TYPE C, "   'E'
lv_p_name_of_program  TYPE SYREPID. "   

  CALL FUNCTION 'CK_F_MSGPROTOCOL_LINE_APPEND'  "
    EXPORTING
         P_MSGID = lv_p_msgid
         P_MSGTY = lv_p_msgty
         P_MSGNO = lv_p_msgno
         P_MSGV1 = lv_p_msgv1
         P_MSGV2 = lv_p_msgv2
         P_MSGV3 = lv_p_msgv3
         P_MSGV4 = lv_p_msgv4
         P_DEF_SERIOUS_ERROR = lv_p_def_serious_error
         P_NAME_OF_PROGRAM = lv_p_name_of_program
    CHANGING
         P_SERIOUS_ERROR_OCCURED = lv_p_serious_error_occured
    TABLES
         P_MSGPROTOKOLL = lt_p_msgprotokoll
. " CK_F_MSGPROTOCOL_LINE_APPEND




ABAP code using 7.40 inline data declarations to call FM CK_F_MSGPROTOCOL_LINE_APPEND

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_p_msgv1) = ' '.
 
DATA(ld_p_msgv2) = ' '.
 
DATA(ld_p_msgv3) = ' '.
 
DATA(ld_p_msgv4) = ' '.
 
DATA(ld_p_def_serious_error) = 'E'.
 
 


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!