SAP Function Modules

LSO_IF_EVAL_CHANGE SAP Function module







LSO_IF_EVAL_CHANGE 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 LSO_IF_EVAL_CHANGE into the relevant SAP transaction such as SE37 or SE80.

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


Pattern for FM LSO_IF_EVAL_CHANGE - LSO IF EVAL CHANGE





CALL FUNCTION 'LSO_IF_EVAL_CHANGE' "
  EXPORTING
    plvar =                     " plvar
    t_templates =               " lsohp_t_hrobject
    t_appraisors =              " lsohp_t_hrsobid
    t_appraisees =              " lsohp_t_hrsobid
    validity_begin =            " begdatum
    validity_end =              " enddatum
*   change = SPACE              " lso_x_c
*   with_sel_screen = SPACE     " lso_x_c
*   with_workload = SPACE       " char1
*   overview = 'X'              " lso_x_c
    .  "  LSO_IF_EVAL_CHANGE

ABAP code example for Function Module LSO_IF_EVAL_CHANGE





The ABAP code below is a full code listing to execute function module LSO_IF_EVAL_CHANGE 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_plvar) = 'Check type of data required'.
DATA(ld_t_templates) = 'Check type of data required'.
DATA(ld_t_appraisors) = 'Check type of data required'.
DATA(ld_t_appraisees) = 'Check type of data required'.
DATA(ld_validity_begin) = 'Check type of data required'.
DATA(ld_validity_end) = 'Check type of data required'.
DATA(ld_change) = 'Check type of data required'.
DATA(ld_with_sel_screen) = 'Check type of data required'.
DATA(ld_with_workload) = 'Check type of data required'.
DATA(ld_overview) = 'Check type of data required'. . CALL FUNCTION 'LSO_IF_EVAL_CHANGE' EXPORTING plvar = ld_plvar t_templates = ld_t_templates t_appraisors = ld_t_appraisors t_appraisees = ld_t_appraisees validity_begin = ld_validity_begin validity_end = ld_validity_end * change = ld_change * with_sel_screen = ld_with_sel_screen * with_workload = ld_with_workload * overview = ld_overview . " LSO_IF_EVAL_CHANGE
IF SY-SUBRC EQ 0. "All OK 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_plvar  TYPE PLVAR ,
ld_t_templates  TYPE LSOHP_T_HROBJECT ,
ld_t_appraisors  TYPE LSOHP_T_HRSOBID ,
ld_t_appraisees  TYPE LSOHP_T_HRSOBID ,
ld_validity_begin  TYPE BEGDATUM ,
ld_validity_end  TYPE ENDDATUM ,
ld_change  TYPE LSO_X_C ,
ld_with_sel_screen  TYPE LSO_X_C ,
ld_with_workload  TYPE CHAR1 ,
ld_overview  TYPE LSO_X_C .

ld_plvar = 'Check type of data required'.
ld_t_templates = 'Check type of data required'.
ld_t_appraisors = 'Check type of data required'.
ld_t_appraisees = 'Check type of data required'.
ld_validity_begin = 'Check type of data required'.
ld_validity_end = 'Check type of data required'.
ld_change = 'Check type of data required'.
ld_with_sel_screen = 'Check type of data required'.
ld_with_workload = 'Check type of data required'.
ld_overview = 'Check type of data required'.

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 LSO_IF_EVAL_CHANGE or its description.