SAP Function Modules

comments icon Comments

TERM_DISPLAY_QCHECK SAP Function module







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

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


Pattern for FM TERM_DISPLAY_QCHECK - TERM DISPLAY QCHECK 





CALL FUNCTION 'TERM_DISPLAY_QCHECK' "
  EXPORTING
    i_terms =                   " sterm_qcheck_tt
    i_agency =                  " sterm_prj_tgroup-project_tgroup
    i_project =                 " sterm_prj_head-project_key
    i_project_name =            " sterm_prj_head-project_name
    i_slang =                   " sy-langu
    i_tlang =                   " sy-langu
    i_date_from =               " dats
    i_date_to =                 " dats
    i_overall =                 " i
    i_edit =                    " as4flag
*   i_error =                   " i
    i_evaluator =               " sy-uname
    i_comment =                 " sterm_q_check_h-ag_comment
    .  "  TERM_DISPLAY_QCHECK

ABAP code example for Function Module TERM_DISPLAY_QCHECK





The ABAP code below is a full code listing to execute function module TERM_DISPLAY_QCHECK 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_i_terms) = 'Check type of data required'.
 

SELECT single PROJECT_TGROUP 
  FROM STERM_PRJ_TGROUP 
  INTO @DATA(ld_i_agency).

 

SELECT single PROJECT_KEY 
  FROM STERM_PRJ_HEAD 
  INTO @DATA(ld_i_project).

 

SELECT single PROJECT_NAME 
  FROM STERM_PRJ_HEAD 
  INTO @DATA(ld_i_project_name).


DATA(ld_i_slang) = 'Check type of data required'.

DATA(ld_i_tlang) = 'Check type of data required'.

DATA(ld_i_date_from) = 'Check type of data required'.

DATA(ld_i_date_to) = 'Check type of data required'.

DATA(ld_i_overall) = 'Check type of data required'.

DATA(ld_i_edit) = 'Check type of data required'.

DATA(ld_i_error) = 'Check type of data required'.

DATA(ld_i_evaluator) = 'some text here'.
 

SELECT single AG_COMMENT 
  FROM STERM_Q_CHECK_H 
  INTO @DATA(ld_i_comment).

.

CALL FUNCTION 'TERM_DISPLAY_QCHECK'
  EXPORTING
    i_terms =                    ld_i_terms
    i_agency =                   ld_i_agency
    i_project =                  ld_i_project
    i_project_name =             ld_i_project_name
    i_slang =                    ld_i_slang
    i_tlang =                    ld_i_tlang
    i_date_from =                ld_i_date_from
    i_date_to =                  ld_i_date_to
    i_overall =                  ld_i_overall
    i_edit =                     ld_i_edit
*   i_error =                    ld_i_error
    i_evaluator =                ld_i_evaluator
    i_comment =                  ld_i_comment
    .  "  TERM_DISPLAY_QCHECK

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_i_terms  TYPE STERM_QCHECK_TT ,
ld_i_agency  TYPE STERM_PRJ_TGROUP-PROJECT_TGROUP ,
ld_i_project  TYPE STERM_PRJ_HEAD-PROJECT_KEY ,
ld_i_project_name  TYPE STERM_PRJ_HEAD-PROJECT_NAME ,
ld_i_slang  TYPE SY-LANGU ,
ld_i_tlang  TYPE SY-LANGU ,
ld_i_date_from  TYPE DATS ,
ld_i_date_to  TYPE DATS ,
ld_i_overall  TYPE I ,
ld_i_edit  TYPE AS4FLAG ,
ld_i_error  TYPE I ,
ld_i_evaluator  TYPE SY-UNAME ,
ld_i_comment  TYPE STERM_Q_CHECK_H-AG_COMMENT .




ld_i_terms = 'some text here'.

SELECT single PROJECT_TGROUP 
  FROM STERM_PRJ_TGROUP 
  INTO ld_i_agency.


SELECT single PROJECT_KEY 
  FROM STERM_PRJ_HEAD 
  INTO ld_i_project.


SELECT single PROJECT_NAME 
  FROM STERM_PRJ_HEAD 
  INTO ld_i_project_name.

ld_i_slang = 'Check type of data required'.
ld_i_tlang = 'Check type of data required'.
ld_i_date_from = 'Check type of data required'.
ld_i_date_to = 'Check type of data required'.
ld_i_overall = 'Check type of data required'.
ld_i_edit = 'Check type of data required'.
ld_i_error = 'Check type of data required'.
ld_i_evaluator = 'some text here'.

SELECT single AG_COMMENT 
  FROM STERM_Q_CHECK_H 
  INTO ld_i_comment.

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


   
 

TERM_DISPLAY_QCHECK - 
TERM_DISPLAY_PROPOSAL_POOL - 
TERM_DISPLAY_LONGTEXT - 
TERM_DISPLAY_LIST - 
TERM_DISPLAY_HTML - 
TERM_DISPLAY_CONCEPT_TREE -