SAP ICLE_EVALUATE_REQUEST Function Module for Determines Result of Request

Search SAP Function Modules

ICLE_EVALUATE_REQUEST is a standard icle evaluate request 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 Request 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 evaluate request FM, simply by entering the name ICLE_EVALUATE_REQUEST into the relevant SAP transaction such as SE37 or SE38.

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

Function ICLE_EVALUATE_REQUEST 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_EVALUATE_REQUEST'"Determines Result of Request
  EXPORTING
   IV_REQUEST =  "Value Request
*  IS_ACTUAL =  "Values for Description of Current Claim Data

 IMPORTING
   EV_VALUE =  "Messages, Message Variable
   EV_TYPE =  "Field Category
   EV_LENGTH =  "BRF: Field Length/Structure Length
   EV_OUTPUTLEN =  "Output Length
   EV_BRF_PLUS_USED =  "
   EO_BRF_PLUS_RESULT =  "

EXCEPTIONS
   CALCULATION_OVERFLOW = 1    ERROR_IN_FUNCTION = 2    FIELD_NOT_FOUND = 3    EXCEPTION_IN_GET_FUNCTION = 4    REQUEST_NOT_FOUND = 5 

.

IMPORTING Parameters details for ICLE_EVALUATE_REQUEST

IV_REQUEST - Value Request

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

IS_ACTUAL - Values for Description of Current Claim Data

Data type: ICLE_ACTUAL
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ICLE_EVALUATE_REQUEST

EV_VALUE - Messages, Message Variable

Data type: SYMSGV
Optional: No
Call by Reference: Yes

EV_TYPE - Field Category

Data type: ICL_CMC_TYPE
Optional: No
Call by Reference: Yes

EV_LENGTH - BRF: Field Length/Structure Length

Data type: BRF_RESULT_LENGTH
Optional: No
Call by Reference: Yes

EV_OUTPUTLEN - Output Length

Data type: ICL_CMC_OUTLEN
Optional: No
Call by Reference: Yes

EV_BRF_PLUS_USED -

Data type: XFELD
Optional: No
Call by Reference: Yes

EO_BRF_PLUS_RESULT -

Data type: DATA
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CALCULATION_OVERFLOW -

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

ERROR_IN_FUNCTION - A Function Module Reported an Error

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

FIELD_NOT_FOUND - Assignment Failed

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

EXCEPTION_IN_GET_FUNCTION - A GET Function Module Reports an Exception

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

REQUEST_NOT_FOUND - Value Request Not Found

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

Copy and paste ABAP code example for ICLE_EVALUATE_REQUEST 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.

ABAP code using 7.40 inline data declarations to call FM ICLE_EVALUATE_REQUEST

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