SAP Function Modules

CRIF_WEB_EVALUATION_DATA_READ SAP Function module







CRIF_WEB_EVALUATION_DATA_READ is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CRIF_WEB_EVALUATION_DATA_READ into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: WEB_EVALUATION_IF
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM CRIF_WEB_EVALUATION_DATA_READ - CRIF WEB EVALUATION DATA READ





CALL FUNCTION 'CRIF_WEB_EVALUATION_DATA_READ' "
  EXPORTING
    planversion =               " p1000-plvar
    object_type =               " p1000-otype
    object_id =                 " p1000-objid
*   eval_begda =                " p1000-begda
*   eval_endda =                " p1000-endda
*   eval_date =                 " p1000-begda
  IMPORTING
    eval_attributes =           " web_evaluation_attributes
  TABLES
    appraisers =                " web_evaluation_appraisers
    appraisees =                " web_evaluation_appraisees
    evaluation =                " web_evaluation
*   descriptions =              " p1002_exp
*   eval_ratings_q =            " web_eval_scales_q
*   eval_ratings_m =            " web_eval_scales_m
*   eval_ratings_descr =        " web_eval_ratdescr
*   eval_notes =                " web_eval_notes
  EXCEPTIONS
    FUNCTION_NOT_SUPPORTED = 1  "
    NO_AUTHORITY = 2            "
    NOT_FOUND = 3               "
    .  "  CRIF_WEB_EVALUATION_DATA_READ

ABAP code example for Function Module CRIF_WEB_EVALUATION_DATA_READ





The ABAP code below is a full code listing to execute function module CRIF_WEB_EVALUATION_DATA_READ including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_eval_attributes  TYPE WEB_EVALUATION_ATTRIBUTES ,
it_appraisers  TYPE STANDARD TABLE OF WEB_EVALUATION_APPRAISERS,"TABLES PARAM
wa_appraisers  LIKE LINE OF it_appraisers ,
it_appraisees  TYPE STANDARD TABLE OF WEB_EVALUATION_APPRAISEES,"TABLES PARAM
wa_appraisees  LIKE LINE OF it_appraisees ,
it_evaluation  TYPE STANDARD TABLE OF WEB_EVALUATION,"TABLES PARAM
wa_evaluation  LIKE LINE OF it_evaluation ,
it_descriptions  TYPE STANDARD TABLE OF P1002_EXP,"TABLES PARAM
wa_descriptions  LIKE LINE OF it_descriptions ,
it_eval_ratings_q  TYPE STANDARD TABLE OF WEB_EVAL_SCALES_Q,"TABLES PARAM
wa_eval_ratings_q  LIKE LINE OF it_eval_ratings_q ,
it_eval_ratings_m  TYPE STANDARD TABLE OF WEB_EVAL_SCALES_M,"TABLES PARAM
wa_eval_ratings_m  LIKE LINE OF it_eval_ratings_m ,
it_eval_ratings_descr  TYPE STANDARD TABLE OF WEB_EVAL_RATDESCR,"TABLES PARAM
wa_eval_ratings_descr  LIKE LINE OF it_eval_ratings_descr ,
it_eval_notes  TYPE STANDARD TABLE OF WEB_EVAL_NOTES,"TABLES PARAM
wa_eval_notes  LIKE LINE OF it_eval_notes .


DATA(ld_planversion) = some text here

DATA(ld_object_type) = some text here

DATA(ld_object_id) = Check type of data required

DATA(ld_eval_begda) = 20210129

DATA(ld_eval_endda) = 20210129

DATA(ld_eval_date) = 20210129

"populate fields of struture and append to itab
append wa_appraisers to it_appraisers.

"populate fields of struture and append to itab
append wa_appraisees to it_appraisees.

"populate fields of struture and append to itab
append wa_evaluation to it_evaluation.

"populate fields of struture and append to itab
append wa_descriptions to it_descriptions.

"populate fields of struture and append to itab
append wa_eval_ratings_q to it_eval_ratings_q.

"populate fields of struture and append to itab
append wa_eval_ratings_m to it_eval_ratings_m.

"populate fields of struture and append to itab
append wa_eval_ratings_descr to it_eval_ratings_descr.

"populate fields of struture and append to itab
append wa_eval_notes to it_eval_notes. . CALL FUNCTION 'CRIF_WEB_EVALUATION_DATA_READ' EXPORTING planversion = ld_planversion object_type = ld_object_type object_id = ld_object_id * eval_begda = ld_eval_begda * eval_endda = ld_eval_endda * eval_date = ld_eval_date IMPORTING eval_attributes = ld_eval_attributes TABLES appraisers = it_appraisers appraisees = it_appraisees evaluation = it_evaluation * descriptions = it_descriptions * eval_ratings_q = it_eval_ratings_q * eval_ratings_m = it_eval_ratings_m * eval_ratings_descr = it_eval_ratings_descr * eval_notes = it_eval_notes EXCEPTIONS FUNCTION_NOT_SUPPORTED = 1 NO_AUTHORITY = 2 NOT_FOUND = 3 . " CRIF_WEB_EVALUATION_DATA_READ
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_eval_attributes  TYPE WEB_EVALUATION_ATTRIBUTES ,
ld_planversion  TYPE P1000-PLVAR ,
it_appraisers  TYPE STANDARD TABLE OF WEB_EVALUATION_APPRAISERS ,
wa_appraisers  LIKE LINE OF it_appraisers,
ld_object_type  TYPE P1000-OTYPE ,
it_appraisees  TYPE STANDARD TABLE OF WEB_EVALUATION_APPRAISEES ,
wa_appraisees  LIKE LINE OF it_appraisees,
ld_object_id  TYPE P1000-OBJID ,
it_evaluation  TYPE STANDARD TABLE OF WEB_EVALUATION ,
wa_evaluation  LIKE LINE OF it_evaluation,
ld_eval_begda  TYPE P1000-BEGDA ,
it_descriptions  TYPE STANDARD TABLE OF P1002_EXP ,
wa_descriptions  LIKE LINE OF it_descriptions,
ld_eval_endda  TYPE P1000-ENDDA ,
it_eval_ratings_q  TYPE STANDARD TABLE OF WEB_EVAL_SCALES_Q ,
wa_eval_ratings_q  LIKE LINE OF it_eval_ratings_q,
ld_eval_date  TYPE P1000-BEGDA ,
it_eval_ratings_m  TYPE STANDARD TABLE OF WEB_EVAL_SCALES_M ,
wa_eval_ratings_m  LIKE LINE OF it_eval_ratings_m,
it_eval_ratings_descr  TYPE STANDARD TABLE OF WEB_EVAL_RATDESCR ,
wa_eval_ratings_descr  LIKE LINE OF it_eval_ratings_descr,
it_eval_notes  TYPE STANDARD TABLE OF WEB_EVAL_NOTES ,
wa_eval_notes  LIKE LINE OF it_eval_notes.


ld_planversion = some text here

"populate fields of struture and append to itab
append wa_appraisers to it_appraisers.

ld_object_type = some text here

"populate fields of struture and append to itab
append wa_appraisees to it_appraisees.

ld_object_id = Check type of data required

"populate fields of struture and append to itab
append wa_evaluation to it_evaluation.

ld_eval_begda = 20210129

"populate fields of struture and append to itab
append wa_descriptions to it_descriptions.

ld_eval_endda = 20210129

"populate fields of struture and append to itab
append wa_eval_ratings_q to it_eval_ratings_q.

ld_eval_date = 20210129

"populate fields of struture and append to itab
append wa_eval_ratings_m to it_eval_ratings_m.

"populate fields of struture and append to itab
append wa_eval_ratings_descr to it_eval_ratings_descr.

"populate fields of struture and append to itab
append wa_eval_notes to it_eval_notes.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CRIF_WEB_EVALUATION_DATA_READ or its description.