SAP ICLX_GET_MESSAGE_PROTOCOL Function Module for Set Message Table
ICLX_GET_MESSAGE_PROTOCOL is a standard iclx get message protocol SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Message Table 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 iclx get message protocol FM, simply by entering the name ICLX_GET_MESSAGE_PROTOCOL into the relevant SAP transaction such as SE37 or SE38.
Function Group: ICLX_TOOLS_APP
Program Name: SAPLICLX_TOOLS_APP
Main Program: SAPLICLX_TOOLS_APP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICLX_GET_MESSAGE_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 'ICLX_GET_MESSAGE_PROTOCOL'"Set Message Table.
IMPORTING
ET_RETURN = "Table for Error Structure BAPIRET2
ET_MESSAGE_PROTOCOL = "Message Log: Error, Warning, Information, Success Messages
EXPORTING Parameters details for ICLX_GET_MESSAGE_PROTOCOL
ET_RETURN - Table for Error Structure BAPIRET2
Data type: ICL_BAPIRET2_TABOptional: No
Call by Reference: Yes
ET_MESSAGE_PROTOCOL - Message Log: Error, Warning, Information, Success Messages
Data type: ICLX_MESSAGE_PROTOCOL_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ICLX_GET_MESSAGE_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: | ||||
| lv_et_return | TYPE ICL_BAPIRET2_TAB, " | |||
| lv_et_message_protocol | TYPE ICLX_MESSAGE_PROTOCOL_T. " |
|   CALL FUNCTION 'ICLX_GET_MESSAGE_PROTOCOL' "Set Message Table |
| IMPORTING | ||
| ET_RETURN | = lv_et_return | |
| ET_MESSAGE_PROTOCOL | = lv_et_message_protocol | |
| . " ICLX_GET_MESSAGE_PROTOCOL | ||
ABAP code using 7.40 inline data declarations to call FM ICLX_GET_MESSAGE_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.Search for further information about these or an SAP related objects