SAP EVAL_READ_CRITERIA Function Module for NOTRANSL: Lesen der Haupt- bzw. Teilkriterien in der Lieferantenbeurteilun

Search SAP Function Modules

EVAL_READ_CRITERIA is a standard eval read criteria SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Lesen der Haupt- bzw. Teilkriterien in der Lieferantenbeurteilun 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 eval read criteria FM, simply by entering the name EVAL_READ_CRITERIA into the relevant SAP transaction such as SE37 or SE38.

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

Function EVAL_READ_CRITERIA 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 'EVAL_READ_CRITERIA'"NOTRANSL: Lesen der Haupt- bzw. Teilkriterien in der Lieferantenbeurteilun
  EXPORTING
   P_ORG =  "
*  M_CRIT =  "

 IMPORTING
   MAX_SCORE =  "

TABLES
*  MAINCRIT =  "
   SUBCRIT =  "
*  CRITTYPES =  "

EXCEPTIONS
   NO_PARAMETERS = 1    NO_MAINCRIT = 2    NO_SUBCRIT_PER_MAINCRIT = 3    NO_TEXT_MAINCRIT = 4    NO_TEXT_SUBCRIT = 5 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLMEL0_001 User Exits for Vendor Evaluation

IMPORTING Parameters details for EVAL_READ_CRITERIA

P_ORG -

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

M_CRIT -

Data type: ELBP-HKRIT
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for EVAL_READ_CRITERIA

MAX_SCORE -

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

TABLES Parameters details for EVAL_READ_CRITERIA

MAINCRIT -

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

SUBCRIT -

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

CRITTYPES -

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

EXCEPTIONS details

NO_PARAMETERS -

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

NO_MAINCRIT -

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

NO_SUBCRIT_PER_MAINCRIT -

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

NO_TEXT_MAINCRIT -

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

NO_TEXT_SUBCRIT -

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

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

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