SAP QINT_PUT_SAMPLE_VALUES Function Module for Transfer inspection results to results recording (sample results)
QINT_PUT_SAMPLE_VALUES is a standard qint put sample values SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Transfer inspection results to results recording (sample results) 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 qint put sample values FM, simply by entering the name QINT_PUT_SAMPLE_VALUES into the relevant SAP transaction such as SE37 or SE38.
Function Group: QINT
Program Name: SAPLQINT
Main Program: SAPLQINT
Appliation area: Q
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function QINT_PUT_SAMPLE_VALUES 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 'QINT_PUT_SAMPLE_VALUES'"Transfer inspection results to results recording (sample results).
TABLES
T_QAISRTAB = "Sample results (input)
T_QIERRTAB = "Error log (output)
TABLES Parameters details for QINT_PUT_SAMPLE_VALUES
T_QAISRTAB - Sample results (input)
Data type: QAISR3Optional: No
Call by Reference: Yes
T_QIERRTAB - Error log (output)
Data type: QIERROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for QINT_PUT_SAMPLE_VALUES 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: | ||||
| lt_t_qaisrtab | TYPE STANDARD TABLE OF QAISR3, " | |||
| lt_t_qierrtab | TYPE STANDARD TABLE OF QIERR. " |
|   CALL FUNCTION 'QINT_PUT_SAMPLE_VALUES' "Transfer inspection results to results recording (sample results) |
| TABLES | ||
| T_QAISRTAB | = lt_t_qaisrtab | |
| T_QIERRTAB | = lt_t_qierrtab | |
| . " QINT_PUT_SAMPLE_VALUES | ||
ABAP code using 7.40 inline data declarations to call FM QINT_PUT_SAMPLE_VALUES
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.Search for further information about these or an SAP related objects