SAP QDLI_SAMPLE_PLAN_CHECK Function Module for NOTRANSL: Überprüfung des im Plan angegeben Stichprobenverfahrens
QDLI_SAMPLE_PLAN_CHECK is a standard qdli sample plan check 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: Überprüfung des im Plan angegeben Stichprobenverfahrens 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 qdli sample plan check FM, simply by entering the name QDLI_SAMPLE_PLAN_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: QDLI
Program Name: SAPLQDLI
Main Program: SAPLQDLI
Appliation area: Q
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function QDLI_SAMPLE_PLAN_CHECK 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 'QDLI_SAMPLE_PLAN_CHECK'"NOTRANSL: Überprüfung des im Plan angegeben Stichprobenverfahrens.
EXPORTING
* BEWMODUS = ' ' "Valuation mode
QMKST_IMP = "Control indicator string for characteristics
* TAKTBEZUG = ' ' "Time-related sampling procedures, if set
* SLWBEZ = ' ' "
VERFAHREN = "Sampling procedure
* NO_CHECK_QMKST = ' ' "
IMPORTING
E_KZUMFS = "
EXCEPTIONS
NOT_CORRECT = 1 NOT_FOUND = 2 NOT_CORRECT_WITH_MESSAGE = 3
IMPORTING Parameters details for QDLI_SAMPLE_PLAN_CHECK
BEWMODUS - Valuation mode
Data type: QDSV-BEWERTMODDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
QMKST_IMP - Control indicator string for characteristics
Data type: QMKSTOptional: No
Call by Reference: No ( called with pass by value option)
TAKTBEZUG - Time-related sampling procedures, if set
Data type: PLKO-QKZRASTERDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
SLWBEZ -
Data type: PLKO-SLWBEZDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
VERFAHREN - Sampling procedure
Data type: QDSV-STICHPRVEROptional: No
Call by Reference: No ( called with pass by value option)
NO_CHECK_QMKST -
Data type: QM00-QKZDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for QDLI_SAMPLE_PLAN_CHECK
E_KZUMFS -
Data type: QDSV-KZUMFSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_CORRECT - Sampling procedure is not appropriate
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND - Sampling procedure not available
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_CORRECT_WITH_MESSAGE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for QDLI_SAMPLE_PLAN_CHECK 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_bewmodus | TYPE QDSV-BEWERTMOD, " ' ' | |||
| lv_e_kzumfs | TYPE QDSV-KZUMFS, " | |||
| lv_not_correct | TYPE QDSV, " | |||
| lv_not_found | TYPE QDSV, " | |||
| lv_qmkst_imp | TYPE QMKST, " | |||
| lv_taktbezug | TYPE PLKO-QKZRASTER, " ' ' | |||
| lv_not_correct_with_message | TYPE PLKO, " | |||
| lv_slwbez | TYPE PLKO-SLWBEZ, " ' ' | |||
| lv_verfahren | TYPE QDSV-STICHPRVER, " | |||
| lv_no_check_qmkst | TYPE QM00-QKZ. " ' ' |
|   CALL FUNCTION 'QDLI_SAMPLE_PLAN_CHECK' "NOTRANSL: Überprüfung des im Plan angegeben Stichprobenverfahrens |
| EXPORTING | ||
| BEWMODUS | = lv_bewmodus | |
| QMKST_IMP | = lv_qmkst_imp | |
| TAKTBEZUG | = lv_taktbezug | |
| SLWBEZ | = lv_slwbez | |
| VERFAHREN | = lv_verfahren | |
| NO_CHECK_QMKST | = lv_no_check_qmkst | |
| IMPORTING | ||
| E_KZUMFS | = lv_e_kzumfs | |
| EXCEPTIONS | ||
| NOT_CORRECT = 1 | ||
| NOT_FOUND = 2 | ||
| NOT_CORRECT_WITH_MESSAGE = 3 | ||
| . " QDLI_SAMPLE_PLAN_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM QDLI_SAMPLE_PLAN_CHECK
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 BEWERTMOD FROM QDSV INTO @DATA(ld_bewmodus). | ||||
| DATA(ld_bewmodus) | = ' '. | |||
| "SELECT single KZUMFS FROM QDSV INTO @DATA(ld_e_kzumfs). | ||||
| "SELECT single QKZRASTER FROM PLKO INTO @DATA(ld_taktbezug). | ||||
| DATA(ld_taktbezug) | = ' '. | |||
| "SELECT single SLWBEZ FROM PLKO INTO @DATA(ld_slwbez). | ||||
| DATA(ld_slwbez) | = ' '. | |||
| "SELECT single STICHPRVER FROM QDSV INTO @DATA(ld_verfahren). | ||||
| "SELECT single QKZ FROM QM00 INTO @DATA(ld_no_check_qmkst). | ||||
| DATA(ld_no_check_qmkst) | = ' '. | |||
Search for further information about these or an SAP related objects