SAP ICLC_LB_CHECK_STATUS_SET Function Module for BRF: Check Whether Status Is Set
ICLC_LB_CHECK_STATUS_SET is a standard iclc lb check status set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BRF: Check Whether Status Is Set 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 iclc lb check status set FM, simply by entering the name ICLC_LB_CHECK_STATUS_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: ICL_BAS_UI
Program Name: SAPLICL_BAS_UI
Main Program: SAPLICL_BAS_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICLC_LB_CHECK_STATUS_SET 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 'ICLC_LB_CHECK_STATUS_SET'"BRF: Check Whether Status Is Set.
EXPORTING
IT_EXPRESSIONS = "BRF: Structure Parameter + Other Fields (Table Category)
IO_EVENT = "BRF: Event
IO_EXPRESSION = "BRF: Expression
IMPORTING
EV_VALUE = "BRF: Result
EV_TYPE = "BRF: Result Type
EV_LENGTH = "BRF: Field Length/Structure Length
EV_CURRENCY = "BRF: Currency Key
EV_OUTPUT_LENGTH = "BRF: Output Length
EV_DECIMALS = "BRF: Decimal Places for Category P
EV_DATA_MISSING = "BRF: Data Missing
IMPORTING Parameters details for ICLC_LB_CHECK_STATUS_SET
IT_EXPRESSIONS - BRF: Structure Parameter + Other Fields (Table Category)
Data type: SBRF260A_TOptional: No
Call by Reference: Yes
IO_EVENT - BRF: Event
Data type: IF_EVENT_BRFOptional: No
Call by Reference: Yes
IO_EXPRESSION - BRF: Expression
Data type: IF_EXPRESSION_BRFOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ICLC_LB_CHECK_STATUS_SET
EV_VALUE - BRF: Result
Data type: BRF_RESULT_VALUEOptional: No
Call by Reference: Yes
EV_TYPE - BRF: Result Type
Data type: BRF_RESULT_TYPEOptional: No
Call by Reference: Yes
EV_LENGTH - BRF: Field Length/Structure Length
Data type: BRF_RESULT_LENGTHOptional: No
Call by Reference: Yes
EV_CURRENCY - BRF: Currency Key
Data type: BRF_CURRENCYOptional: No
Call by Reference: Yes
EV_OUTPUT_LENGTH - BRF: Output Length
Data type: BRF_RESULT_OUTPUT_LENGTHOptional: No
Call by Reference: Yes
EV_DECIMALS - BRF: Decimal Places for Category P
Data type: BRF_RESULT_DECIMALSOptional: No
Call by Reference: Yes
EV_DATA_MISSING - BRF: Data Missing
Data type: BRF_DATA_MISSINGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ICLC_LB_CHECK_STATUS_SET 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_ev_value | TYPE BRF_RESULT_VALUE, " | |||
| lv_it_expressions | TYPE SBRF260A_T, " | |||
| lv_ev_type | TYPE BRF_RESULT_TYPE, " | |||
| lv_io_event | TYPE IF_EVENT_BRF, " | |||
| lv_ev_length | TYPE BRF_RESULT_LENGTH, " | |||
| lv_io_expression | TYPE IF_EXPRESSION_BRF, " | |||
| lv_ev_currency | TYPE BRF_CURRENCY, " | |||
| lv_ev_output_length | TYPE BRF_RESULT_OUTPUT_LENGTH, " | |||
| lv_ev_decimals | TYPE BRF_RESULT_DECIMALS, " | |||
| lv_ev_data_missing | TYPE BRF_DATA_MISSING. " |
|   CALL FUNCTION 'ICLC_LB_CHECK_STATUS_SET' "BRF: Check Whether Status Is Set |
| EXPORTING | ||
| IT_EXPRESSIONS | = lv_it_expressions | |
| IO_EVENT | = lv_io_event | |
| IO_EXPRESSION | = lv_io_expression | |
| IMPORTING | ||
| EV_VALUE | = lv_ev_value | |
| EV_TYPE | = lv_ev_type | |
| EV_LENGTH | = lv_ev_length | |
| EV_CURRENCY | = lv_ev_currency | |
| EV_OUTPUT_LENGTH | = lv_ev_output_length | |
| EV_DECIMALS | = lv_ev_decimals | |
| EV_DATA_MISSING | = lv_ev_data_missing | |
| . " ICLC_LB_CHECK_STATUS_SET | ||
ABAP code using 7.40 inline data declarations to call FM ICLC_LB_CHECK_STATUS_SET
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