SAP CHECK_QM_DATA Function Module for NOTRANSL: Prüft, ob der Aufruf der QM-Prüfdaten erlaubt ist
CHECK_QM_DATA is a standard check qm data 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: Prüft, ob der Aufruf der QM-Prüfdaten erlaubt ist 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 check qm data FM, simply by entering the name CHECK_QM_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: MG02
Program Name: SAPLMG02
Main Program: SAPLMG02
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CHECK_QM_DATA 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 'CHECK_QM_DATA'"NOTRANSL: Prüft, ob der Aufruf der QM-Prüfdaten erlaubt ist.
EXPORTING
P_VERAR = "Processing indicator in T130M
* P_WERKS = "Plant
* P_AKTVSTATUS = "Maintenance status
* P_KZRFB = ' ' "Indicator: reset buffer for Material_Pre_Fetch
* P_FELDNAME = "Field Name In Full (Table Name + Hyphen + Field Name)
* FLG_FIELD_SELECT = ' ' "Propose Field Content from the Reference
* P_DLINE = ' ' "Key date
EXCEPTIONS
CHECK_ERROR = 1
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_SAPLMG02_001 Customer Exit: Internal Material Number Assignment
EXIT_SAPLMG02_002 Customer Exit: External Material Number Assignment
IMPORTING Parameters details for CHECK_QM_DATA
P_VERAR - Processing indicator in T130M
Data type: T130M-VERAROptional: No
Call by Reference: No ( called with pass by value option)
P_WERKS - Plant
Data type: RMMG1-WERKSOptional: Yes
Call by Reference: No ( called with pass by value option)
P_AKTVSTATUS - Maintenance status
Data type: T130M-PSTATOptional: Yes
Call by Reference: No ( called with pass by value option)
P_KZRFB - Indicator: reset buffer for Material_Pre_Fetch
Data type: MTCOM-KZRFBDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
P_FELDNAME - Field Name In Full (Table Name + Hyphen + Field Name)
Data type: T130F-FNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
FLG_FIELD_SELECT - Propose Field Content from the Reference
Data type: T130F-KZREFDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
P_DLINE - Key date
Data type: RMMG1-DLINEDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CHECK_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CHECK_QM_DATA 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_p_verar | TYPE T130M-VERAR, " | |||
| lv_check_error | TYPE T130M, " | |||
| lv_p_werks | TYPE RMMG1-WERKS, " | |||
| lv_p_aktvstatus | TYPE T130M-PSTAT, " | |||
| lv_p_kzrfb | TYPE MTCOM-KZRFB, " ' ' | |||
| lv_p_feldname | TYPE T130F-FNAME, " | |||
| lv_flg_field_select | TYPE T130F-KZREF, " ' ' | |||
| lv_p_dline | TYPE RMMG1-DLINE. " ' ' |
|   CALL FUNCTION 'CHECK_QM_DATA' "NOTRANSL: Prüft, ob der Aufruf der QM-Prüfdaten erlaubt ist |
| EXPORTING | ||
| P_VERAR | = lv_p_verar | |
| P_WERKS | = lv_p_werks | |
| P_AKTVSTATUS | = lv_p_aktvstatus | |
| P_KZRFB | = lv_p_kzrfb | |
| P_FELDNAME | = lv_p_feldname | |
| FLG_FIELD_SELECT | = lv_flg_field_select | |
| P_DLINE | = lv_p_dline | |
| EXCEPTIONS | ||
| CHECK_ERROR = 1 | ||
| . " CHECK_QM_DATA | ||
ABAP code using 7.40 inline data declarations to call FM CHECK_QM_DATA
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 VERAR FROM T130M INTO @DATA(ld_p_verar). | ||||
| "SELECT single WERKS FROM RMMG1 INTO @DATA(ld_p_werks). | ||||
| "SELECT single PSTAT FROM T130M INTO @DATA(ld_p_aktvstatus). | ||||
| "SELECT single KZRFB FROM MTCOM INTO @DATA(ld_p_kzrfb). | ||||
| DATA(ld_p_kzrfb) | = ' '. | |||
| "SELECT single FNAME FROM T130F INTO @DATA(ld_p_feldname). | ||||
| "SELECT single KZREF FROM T130F INTO @DATA(ld_flg_field_select). | ||||
| DATA(ld_flg_field_select) | = ' '. | |||
| "SELECT single DLINE FROM RMMG1 INTO @DATA(ld_p_dline). | ||||
| DATA(ld_p_dline) | = ' '. | |||
Search for further information about these or an SAP related objects