SAP BAPI_INSPLOT_STATINTERFACE Function Module for QM-STI Interface
BAPI_INSPLOT_STATINTERFACE is a standard bapi insplot statinterface SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for QM-STI Interface 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 bapi insplot statinterface FM, simply by entering the name BAPI_INSPLOT_STATINTERFACE into the relevant SAP transaction such as SE37 or SE38.
Function Group: QIST
Program Name: SAPLQIST
Main Program: SAPLQIST
Appliation area: Q
Release date: 22-Sep-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_INSPLOT_STATINTERFACE 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 'BAPI_INSPLOT_STATINTERFACE'"QM-STI Interface.
IMPORTING
RETURN = "Standard BAPI Return Parameter
MIME_TYPE = "HTML content type
* MIME_LENGTH = "HTML content length
TABLES
* REPORT_HEADER = "Evaluation Header Data
* RESULTS_ADDITIONAL_DATA = "Additional Data: Inspection Results
* METHOD_DATA = "Evaluation Steps
* SAMPLE_QUANTITATIVE = "Summarized Quantitative Results for Characteristic
* SAMPLE_QUALITATIVE = "Summarized Qualitative Results
* MIME = "File Content
* XML = "Data in XML Format
* MATERIAL_DATA = "Material
* VENDOR_DATA = "Vendor
* CHARACTERISTIC_HEADER = "Characteristic Header Data
* CHARACTERISTIC_QUANTITATIVE = "Quantitative Characteristics
* CHARACTERISTIC_QUALITATIVE = "Qualitative Characteristics
* SAMPLE_HEADER = "Samples
* RESULTS_QUANTITATIVE = "Quantitative Inspection Results
* RESULTS_QUALITATIVE = "Qualitative Inspection Results
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_SAPLQIST_001 Generation of Report Header
EXIT_SAPLQIST_002 Generation of Material Data
EXIT_SAPLQIST_003 Generation of Vendor Data
EXIT_SAPLQIST_004 Generation of Characteristic Header
EXIT_SAPLQIST_005 Generation of Quantitative Characteristic
EXIT_SAPLQIST_007 Generation of Sample Header
EXIT_SAPLQIST_008 Generation of Additional Data for Results
EXIT_SAPLQIST_009 Generation of Quantitative Results
EXIT_SAPLQIST_010 Generation of Method Data
EXPORTING Parameters details for BAPI_INSPLOT_STATINTERFACE
RETURN - Standard BAPI Return Parameter
Data type: BAPIRETURN1Optional: No
Call by Reference: No ( called with pass by value option)
MIME_TYPE - HTML content type
Data type: BAPIQCI-CONT_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
MIME_LENGTH - HTML content length
Data type: BAPIQCI-CONT_LENOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_INSPLOT_STATINTERFACE
REPORT_HEADER - Evaluation Header Data
Data type: BAPIQMSTI1Optional: Yes
Call by Reference: No ( called with pass by value option)
RESULTS_ADDITIONAL_DATA - Additional Data: Inspection Results
Data type: BAPIQMSTI8Optional: Yes
Call by Reference: No ( called with pass by value option)
METHOD_DATA - Evaluation Steps
Data type: BAPIQMSTIAOptional: Yes
Call by Reference: No ( called with pass by value option)
SAMPLE_QUANTITATIVE - Summarized Quantitative Results for Characteristic
Data type: BAPIQMSTI71Optional: Yes
Call by Reference: Yes
SAMPLE_QUALITATIVE - Summarized Qualitative Results
Data type: BAPIQMSTI72Optional: Yes
Call by Reference: Yes
MIME - File Content
Data type: BAPIQGMIMEOptional: Yes
Call by Reference: Yes
XML - Data in XML Format
Data type: BAPIQGMIMEOptional: Yes
Call by Reference: Yes
MATERIAL_DATA - Material
Data type: BAPIQMSTI2Optional: Yes
Call by Reference: No ( called with pass by value option)
VENDOR_DATA - Vendor
Data type: BAPIQMSTI3Optional: Yes
Call by Reference: No ( called with pass by value option)
CHARACTERISTIC_HEADER - Characteristic Header Data
Data type: BAPIQMSTI4Optional: Yes
Call by Reference: No ( called with pass by value option)
CHARACTERISTIC_QUANTITATIVE - Quantitative Characteristics
Data type: BAPIQMSTI5Optional: Yes
Call by Reference: No ( called with pass by value option)
CHARACTERISTIC_QUALITATIVE - Qualitative Characteristics
Data type: BAPIQMSTI6Optional: Yes
Call by Reference: No ( called with pass by value option)
SAMPLE_HEADER - Samples
Data type: BAPIQMSTI7Optional: Yes
Call by Reference: No ( called with pass by value option)
RESULTS_QUANTITATIVE - Quantitative Inspection Results
Data type: BAPIQMSTI9Optional: Yes
Call by Reference: No ( called with pass by value option)
RESULTS_QUALITATIVE - Qualitative Inspection Results
Data type: BAPIQMSTI0Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_INSPLOT_STATINTERFACE 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_return | TYPE BAPIRETURN1, " | |||
| lt_report_header | TYPE STANDARD TABLE OF BAPIQMSTI1, " | |||
| lt_results_additional_data | TYPE STANDARD TABLE OF BAPIQMSTI8, " | |||
| lt_method_data | TYPE STANDARD TABLE OF BAPIQMSTIA, " | |||
| lt_sample_quantitative | TYPE STANDARD TABLE OF BAPIQMSTI71, " | |||
| lt_sample_qualitative | TYPE STANDARD TABLE OF BAPIQMSTI72, " | |||
| lt_mime | TYPE STANDARD TABLE OF BAPIQGMIME, " | |||
| lt_xml | TYPE STANDARD TABLE OF BAPIQGMIME, " | |||
| lv_mime_type | TYPE BAPIQCI-CONT_TYPE, " | |||
| lt_material_data | TYPE STANDARD TABLE OF BAPIQMSTI2, " | |||
| lv_mime_length | TYPE BAPIQCI-CONT_LEN, " | |||
| lt_vendor_data | TYPE STANDARD TABLE OF BAPIQMSTI3, " | |||
| lt_characteristic_header | TYPE STANDARD TABLE OF BAPIQMSTI4, " | |||
| lt_characteristic_quantitative | TYPE STANDARD TABLE OF BAPIQMSTI5, " | |||
| lt_characteristic_qualitative | TYPE STANDARD TABLE OF BAPIQMSTI6, " | |||
| lt_sample_header | TYPE STANDARD TABLE OF BAPIQMSTI7, " | |||
| lt_results_quantitative | TYPE STANDARD TABLE OF BAPIQMSTI9, " | |||
| lt_results_qualitative | TYPE STANDARD TABLE OF BAPIQMSTI0. " |
|   CALL FUNCTION 'BAPI_INSPLOT_STATINTERFACE' "QM-STI Interface |
| IMPORTING | ||
| RETURN | = lv_return | |
| MIME_TYPE | = lv_mime_type | |
| MIME_LENGTH | = lv_mime_length | |
| TABLES | ||
| REPORT_HEADER | = lt_report_header | |
| RESULTS_ADDITIONAL_DATA | = lt_results_additional_data | |
| METHOD_DATA | = lt_method_data | |
| SAMPLE_QUANTITATIVE | = lt_sample_quantitative | |
| SAMPLE_QUALITATIVE | = lt_sample_qualitative | |
| MIME | = lt_mime | |
| XML | = lt_xml | |
| MATERIAL_DATA | = lt_material_data | |
| VENDOR_DATA | = lt_vendor_data | |
| CHARACTERISTIC_HEADER | = lt_characteristic_header | |
| CHARACTERISTIC_QUANTITATIVE | = lt_characteristic_quantitative | |
| CHARACTERISTIC_QUALITATIVE | = lt_characteristic_qualitative | |
| SAMPLE_HEADER | = lt_sample_header | |
| RESULTS_QUANTITATIVE | = lt_results_quantitative | |
| RESULTS_QUALITATIVE | = lt_results_qualitative | |
| . " BAPI_INSPLOT_STATINTERFACE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_INSPLOT_STATINTERFACE
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 CONT_TYPE FROM BAPIQCI INTO @DATA(ld_mime_type). | ||||
| "SELECT single CONT_LEN FROM BAPIQCI INTO @DATA(ld_mime_length). | ||||
Search for further information about these or an SAP related objects