SAP G_MESS_PRINT_PROTOCOL Function Module for









G_MESS_PRINT_PROTOCOL is a standard g mess print protocol 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 g mess print protocol FM, simply by entering the name G_MESS_PRINT_PROTOCOL into the relevant SAP transaction such as SE37 or SE38.

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



Function G_MESS_PRINT_PROTOCOL 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 'G_MESS_PRINT_PROTOCOL'"
  EXPORTING
*  I_ERROR_LIST = 'X' "
*  I_ERROR_TAB_TO_MEMORY = ' ' "
*  I_LEDGER =  "
*  I_POST_MESS_LIST = 'X' "
*  I_POST_OK_LIST = 'X' "
*  I_BATCH_PROTOCOL = 'X' "
*  I_TEST = ' ' "
*  I_PRECHECK = ' ' "
*  I_MM_SD_HR = ' ' "
*  I_PROTOCOL_TEXT =  "
*  I_SEND_SUCCESS_MESSAGES = 'X' "

TABLES
*  I_GLEDGER =  "
.



IMPORTING Parameters details for G_MESS_PRINT_PROTOCOL

I_ERROR_LIST -

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

I_ERROR_TAB_TO_MEMORY -

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

I_LEDGER -

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

I_POST_MESS_LIST -

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

I_POST_OK_LIST -

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

I_BATCH_PROTOCOL -

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

I_TEST -

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

I_PRECHECK -

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

I_MM_SD_HR -

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

I_PROTOCOL_TEXT -

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

I_SEND_SUCCESS_MESSAGES -

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

TABLES Parameters details for G_MESS_PRINT_PROTOCOL

I_GLEDGER -

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

Copy and paste ABAP code example for G_MESS_PRINT_PROTOCOL 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:
lt_i_gledger  TYPE STANDARD TABLE OF GLEDGER, "   
lv_i_error_list  TYPE CHAR1, "   'X'
lv_i_error_tab_to_memory  TYPE BOOLE_D, "   SPACE
lv_i_ledger  TYPE RLDNR, "   
lv_i_post_mess_list  TYPE CHAR1, "   'X'
lv_i_post_ok_list  TYPE CHAR1, "   'X'
lv_i_batch_protocol  TYPE CHAR1, "   'X'
lv_i_test  TYPE CHAR1, "   ' '
lv_i_precheck  TYPE CHAR1, "   ' '
lv_i_mm_sd_hr  TYPE CHAR1, "   ' '
lv_i_protocol_text  TYPE STRING, "   
lv_i_send_success_messages  TYPE CHAR1. "   'X'

  CALL FUNCTION 'G_MESS_PRINT_PROTOCOL'  "
    EXPORTING
         I_ERROR_LIST = lv_i_error_list
         I_ERROR_TAB_TO_MEMORY = lv_i_error_tab_to_memory
         I_LEDGER = lv_i_ledger
         I_POST_MESS_LIST = lv_i_post_mess_list
         I_POST_OK_LIST = lv_i_post_ok_list
         I_BATCH_PROTOCOL = lv_i_batch_protocol
         I_TEST = lv_i_test
         I_PRECHECK = lv_i_precheck
         I_MM_SD_HR = lv_i_mm_sd_hr
         I_PROTOCOL_TEXT = lv_i_protocol_text
         I_SEND_SUCCESS_MESSAGES = lv_i_send_success_messages
    TABLES
         I_GLEDGER = lt_i_gledger
. " G_MESS_PRINT_PROTOCOL




ABAP code using 7.40 inline data declarations to call FM G_MESS_PRINT_PROTOCOL

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_i_error_list) = 'X'.
 
DATA(ld_i_error_tab_to_memory) = ' '.
 
 
DATA(ld_i_post_mess_list) = 'X'.
 
DATA(ld_i_post_ok_list) = 'X'.
 
DATA(ld_i_batch_protocol) = 'X'.
 
DATA(ld_i_test) = ' '.
 
DATA(ld_i_precheck) = ' '.
 
DATA(ld_i_mm_sd_hr) = ' '.
 
 
DATA(ld_i_send_success_messages) = '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!