SAP IGN_SEARCH_REQUEST_EVALUATE Function Module for Evaluate Printout for Stop Condition for Search Series









IGN_SEARCH_REQUEST_EVALUATE is a standard ign search request evaluate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Evaluate Printout for Stop Condition for Search Series 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 ign search request evaluate FM, simply by entering the name IGN_SEARCH_REQUEST_EVALUATE into the relevant SAP transaction such as SE37 or SE38.

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



Function IGN_SEARCH_REQUEST_EVALUATE 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 'IGN_SEARCH_REQUEST_EVALUATE'"Evaluate Printout for Stop Condition for Search Series
EXPORTING
IV_APPLCLASS = "BRF: Application Class
IV_EXPRESSION = "BRF Expression
* IS_CONTEXT = "Context for Checking Termination Condition for Search Sequences

IMPORTING
EV_VALUE = "Return Value
EV_TYPE = "Type of Return Value
EV_LENGTH = "Field 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 IGN_SEARCH_REQUEST_EVALUATE

IV_APPLCLASS - BRF: Application Class

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

IV_EXPRESSION - BRF Expression

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

IS_CONTEXT - Context for Checking Termination Condition for Search Sequences

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

EXPORTING Parameters details for IGN_SEARCH_REQUEST_EVALUATE

EV_VALUE - Return Value

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

EV_TYPE - Type of Return Value

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

EV_LENGTH - Field 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 - Invoice 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 IGN_SEARCH_REQUEST_EVALUATE 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 SYMSGV, "   
lv_iv_applclass  TYPE BRF_APPLCLASS, "   
lv_calculation_overflow  TYPE BRF_APPLCLASS, "   
lv_ev_type  TYPE ICL_CMC_TYPE, "   
lv_iv_expression  TYPE BRF_EXPRESSION, "   
lv_error_in_function  TYPE BRF_EXPRESSION, "   
lv_ev_length  TYPE BRF_RESULT_LENGTH, "   
lv_is_context  TYPE IGN_SEARCH_CONTEXT, "   
lv_field_not_found  TYPE IGN_SEARCH_CONTEXT, "   
lv_ev_outputlen  TYPE ICL_CMC_OUTLEN, "   
lv_exception_in_get_function  TYPE ICL_CMC_OUTLEN, "   
lv_ev_brf_plus_used  TYPE XFELD, "   
lv_request_not_found  TYPE XFELD, "   
lv_eo_brf_plus_result  TYPE DATA. "   

  CALL FUNCTION 'IGN_SEARCH_REQUEST_EVALUATE'  "Evaluate Printout for Stop Condition for Search Series
    EXPORTING
         IV_APPLCLASS = lv_iv_applclass
         IV_EXPRESSION = lv_iv_expression
         IS_CONTEXT = lv_is_context
    IMPORTING
         EV_VALUE = lv_ev_value
         EV_TYPE = lv_ev_type
         EV_LENGTH = lv_ev_length
         EV_OUTPUTLEN = lv_ev_outputlen
         EV_BRF_PLUS_USED = lv_ev_brf_plus_used
         EO_BRF_PLUS_RESULT = lv_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
. " IGN_SEARCH_REQUEST_EVALUATE




ABAP code using 7.40 inline data declarations to call FM IGN_SEARCH_REQUEST_EVALUATE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!