SAP ICL_IF_EVALUATE_EXPRESSION Function Module for Determines Result of Expression
ICL_IF_EVALUATE_EXPRESSION is a standard icl if evaluate expression SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines Result of Expression 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 icl if evaluate expression FM, simply by entering the name ICL_IF_EVALUATE_EXPRESSION into the relevant SAP transaction such as SE37 or SE38.
Function Group: ICL_IF2
Program Name: SAPLICL_IF2
Main Program: SAPLICL_IF2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICL_IF_EVALUATE_EXPRESSION 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 'ICL_IF_EVALUATE_EXPRESSION'"Determines Result of Expression.
EXPORTING
IV_EXPRESSION = "BRF: Expression
* IV_RESULT_REQUEST = "
* IS_ACTUAL = "Values for Description of Current Claim Data
IMPORTING
EV_RESULT = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
EV_RESULT_VALUE = "BRF: Result
EV_RESULT_DATA_MISSING = "BRF: Data Missing
EV_RESULT_TYPE = "BRF: Result Type
EV_RESULT_LENGTH = "BRF: Field Length/Structure Length
EV_RESULT_DECIMALS = "BRF: Decimal Places for Category P
EV_RESULT_OUTPUT_LENGTH = "BRF: Output Length
EO_BRF_PLUS_RESULT = "
EXCEPTIONS
ERROR_IN_FUNCTION = 1 OTHER_ERROR = 2
IMPORTING Parameters details for ICL_IF_EVALUATE_EXPRESSION
IV_EXPRESSION - BRF: Expression
Data type: BRF_EXPRESSIONOptional: No
Call by Reference: No ( called with pass by value option)
IV_RESULT_REQUEST -
Data type: BRF_BOOLE_DOptional: Yes
Call by Reference: Yes
IS_ACTUAL - Values for Description of Current Claim Data
Data type: ICL_ACTUALOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ICL_IF_EVALUATE_EXPRESSION
EV_RESULT - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
EV_RESULT_VALUE - BRF: Result
Data type: BRF_RESULT_VALUEOptional: No
Call by Reference: No ( called with pass by value option)
EV_RESULT_DATA_MISSING - BRF: Data Missing
Data type: BRF_DATA_MISSINGOptional: No
Call by Reference: No ( called with pass by value option)
EV_RESULT_TYPE - BRF: Result Type
Data type: BRF_RESULT_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
EV_RESULT_LENGTH - BRF: Field Length/Structure Length
Data type: BRF_RESULT_LENGTHOptional: No
Call by Reference: No ( called with pass by value option)
EV_RESULT_DECIMALS - BRF: Decimal Places for Category P
Data type: BRF_RESULT_DECIMALSOptional: No
Call by Reference: No ( called with pass by value option)
EV_RESULT_OUTPUT_LENGTH - BRF: Output Length
Data type: BRF_RESULT_OUTPUT_LENGTHOptional: No
Call by Reference: No ( called with pass by value option)
EO_BRF_PLUS_RESULT -
Data type: DATAOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_IN_FUNCTION - A Function Module Reported an Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OTHER_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ICL_IF_EVALUATE_EXPRESSION 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_result | TYPE BOOLE_D, " | |||
| lv_iv_expression | TYPE BRF_EXPRESSION, " | |||
| lv_error_in_function | TYPE BRF_EXPRESSION, " | |||
| lv_other_error | TYPE BRF_EXPRESSION, " | |||
| lv_ev_result_value | TYPE BRF_RESULT_VALUE, " | |||
| lv_iv_result_request | TYPE BRF_BOOLE_D, " | |||
| lv_is_actual | TYPE ICL_ACTUAL, " | |||
| lv_ev_result_data_missing | TYPE BRF_DATA_MISSING, " | |||
| lv_ev_result_type | TYPE BRF_RESULT_TYPE, " | |||
| lv_ev_result_length | TYPE BRF_RESULT_LENGTH, " | |||
| lv_ev_result_decimals | TYPE BRF_RESULT_DECIMALS, " | |||
| lv_ev_result_output_length | TYPE BRF_RESULT_OUTPUT_LENGTH, " | |||
| lv_eo_brf_plus_result | TYPE DATA. " |
|   CALL FUNCTION 'ICL_IF_EVALUATE_EXPRESSION' "Determines Result of Expression |
| EXPORTING | ||
| IV_EXPRESSION | = lv_iv_expression | |
| IV_RESULT_REQUEST | = lv_iv_result_request | |
| IS_ACTUAL | = lv_is_actual | |
| IMPORTING | ||
| EV_RESULT | = lv_ev_result | |
| EV_RESULT_VALUE | = lv_ev_result_value | |
| EV_RESULT_DATA_MISSING | = lv_ev_result_data_missing | |
| EV_RESULT_TYPE | = lv_ev_result_type | |
| EV_RESULT_LENGTH | = lv_ev_result_length | |
| EV_RESULT_DECIMALS | = lv_ev_result_decimals | |
| EV_RESULT_OUTPUT_LENGTH | = lv_ev_result_output_length | |
| EO_BRF_PLUS_RESULT | = lv_eo_brf_plus_result | |
| EXCEPTIONS | ||
| ERROR_IN_FUNCTION = 1 | ||
| OTHER_ERROR = 2 | ||
| . " ICL_IF_EVALUATE_EXPRESSION | ||
ABAP code using 7.40 inline data declarations to call FM ICL_IF_EVALUATE_EXPRESSION
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