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

Function ICLE_BUS_MESSAGE_STATUS_GET 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 'ICLE_BUS_MESSAGE_STATUS_GET'"Determine Message Status (0 = No Message).
IMPORTING
MAX_MSG = "Return Value from ABAP Statement
EXPORTING Parameters details for ICLE_BUS_MESSAGE_STATUS_GET
MAX_MSG - Return Value from ABAP Statement
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ICLE_BUS_MESSAGE_STATUS_GET 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_max_msg | TYPE SY-SUBRC. " |
|   CALL FUNCTION 'ICLE_BUS_MESSAGE_STATUS_GET' "Determine Message Status (0 = No Message) |
| IMPORTING | ||
| MAX_MSG | = lv_max_msg | |
| . " ICLE_BUS_MESSAGE_STATUS_GET | ||
ABAP code using 7.40 inline data declarations to call FM ICLE_BUS_MESSAGE_STATUS_GET
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.| "SELECT single SUBRC FROM SY INTO @DATA(ld_max_msg). | ||||
Search for further information about these or an SAP related objects