SAP TERM_DISPLAY_QCHECK Function Module for NOTRANSL: Qualitätsüberprüfung anzeigen
TERM_DISPLAY_QCHECK is a standard term display qcheck 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: Qualitätsüberprüfung anzeigen 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 term display qcheck FM, simply by entering the name TERM_DISPLAY_QCHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: STERM_QCHECK
Program Name: SAPLSTERM_QCHECK
Main Program: SAPLSTERM_QCHECK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TERM_DISPLAY_QCHECK 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 'TERM_DISPLAY_QCHECK'"NOTRANSL: Qualitätsüberprüfung anzeigen.
EXPORTING
I_TERMS = "Table Type for Terminology Check
I_EDIT = "Flag (X or Blank)
* I_ERROR = "Predefined Type
I_EVALUATOR = "ABAP System Field: Name of Current User
I_COMMENT = "String for STERM Editors
I_AGENCY = "Translator Group of Individual Agencies
I_PROJECT = "Project Key
I_PROJECT_NAME = "Project Description
I_SLANG = "ABAP System Field: Language Key of Text Environment
I_TLANG = "ABAP System Field: Language Key of Text Environment
I_DATE_FROM = "Field of type DATS
I_DATE_TO = "Field of type DATS
I_OVERALL = "Predefined Type
IMPORTING Parameters details for TERM_DISPLAY_QCHECK
I_TERMS - Table Type for Terminology Check
Data type: STERM_QCHECK_TTOptional: No
Call by Reference: Yes
I_EDIT - Flag (X or Blank)
Data type: AS4FLAGOptional: No
Call by Reference: Yes
I_ERROR - Predefined Type
Data type: IOptional: Yes
Call by Reference: Yes
I_EVALUATOR - ABAP System Field: Name of Current User
Data type: SY-UNAMEOptional: No
Call by Reference: Yes
I_COMMENT - String for STERM Editors
Data type: STERM_Q_CHECK_H-AG_COMMENTOptional: No
Call by Reference: Yes
I_AGENCY - Translator Group of Individual Agencies
Data type: STERM_PRJ_TGROUP-PROJECT_TGROUPOptional: No
Call by Reference: Yes
I_PROJECT - Project Key
Data type: STERM_PRJ_HEAD-PROJECT_KEYOptional: No
Call by Reference: Yes
I_PROJECT_NAME - Project Description
Data type: STERM_PRJ_HEAD-PROJECT_NAMEOptional: No
Call by Reference: Yes
I_SLANG - ABAP System Field: Language Key of Text Environment
Data type: SY-LANGUOptional: No
Call by Reference: Yes
I_TLANG - ABAP System Field: Language Key of Text Environment
Data type: SY-LANGUOptional: No
Call by Reference: Yes
I_DATE_FROM - Field of type DATS
Data type: DATSOptional: No
Call by Reference: Yes
I_DATE_TO - Field of type DATS
Data type: DATSOptional: No
Call by Reference: Yes
I_OVERALL - Predefined Type
Data type: IOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for TERM_DISPLAY_QCHECK 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_i_terms | TYPE STERM_QCHECK_TT, " | |||
| lv_i_edit | TYPE AS4FLAG, " | |||
| lv_i_error | TYPE I, " | |||
| lv_i_evaluator | TYPE SY-UNAME, " | |||
| lv_i_comment | TYPE STERM_Q_CHECK_H-AG_COMMENT, " | |||
| lv_i_agency | TYPE STERM_PRJ_TGROUP-PROJECT_TGROUP, " | |||
| lv_i_project | TYPE STERM_PRJ_HEAD-PROJECT_KEY, " | |||
| lv_i_project_name | TYPE STERM_PRJ_HEAD-PROJECT_NAME, " | |||
| lv_i_slang | TYPE SY-LANGU, " | |||
| lv_i_tlang | TYPE SY-LANGU, " | |||
| lv_i_date_from | TYPE DATS, " | |||
| lv_i_date_to | TYPE DATS, " | |||
| lv_i_overall | TYPE I. " |
|   CALL FUNCTION 'TERM_DISPLAY_QCHECK' "NOTRANSL: Qualitätsüberprüfung anzeigen |
| EXPORTING | ||
| I_TERMS | = lv_i_terms | |
| I_EDIT | = lv_i_edit | |
| I_ERROR | = lv_i_error | |
| I_EVALUATOR | = lv_i_evaluator | |
| I_COMMENT | = lv_i_comment | |
| I_AGENCY | = lv_i_agency | |
| I_PROJECT | = lv_i_project | |
| I_PROJECT_NAME | = lv_i_project_name | |
| I_SLANG | = lv_i_slang | |
| I_TLANG | = lv_i_tlang | |
| I_DATE_FROM | = lv_i_date_from | |
| I_DATE_TO | = lv_i_date_to | |
| I_OVERALL | = lv_i_overall | |
| . " TERM_DISPLAY_QCHECK | ||
ABAP code using 7.40 inline data declarations to call FM TERM_DISPLAY_QCHECK
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.| "SELECT single UNAME FROM SY INTO @DATA(ld_i_evaluator). | ||||
| "SELECT single AG_COMMENT FROM STERM_Q_CHECK_H INTO @DATA(ld_i_comment). | ||||
| "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). | ||||
| "SELECT single LANGU FROM SY INTO @DATA(ld_i_slang). | ||||
| "SELECT single LANGU FROM SY INTO @DATA(ld_i_tlang). | ||||
Search for further information about these or an SAP related objects