# SAP QM Integration With LIMS: How the Hand-Off Works > Source: https://netray.co/erp-help/sap-qm-integration-with-lims > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer A LIMS connects to SAP QM by receiving the inspection lot and its characteristics, running the lab work, then returning results (and sometimes the usage decision) to SAP. The main options are the QM-STI subsystem interface, released BAPIs such as BAPI_INSPOPER_RECORDRESULT, IDocs through middleware, or modern APIs. Choose by who owns the usage decision. ## Kind advanced ## System sap ## Erp SAP ERP / S/4HANA ## Module QM / Subsystem and LIMS Interfaces ## Query sap qm integration with lims ## Alternate Queries - sap qm and lims integration - lims integration with sap qm - sap qm lims interface qm-sti ## Applies To SAP ECC 6.0 and S/4HANA QM; LIMS products vary, and many ship their own SAP adapter ## Steps ### Planning the integration **Items:** - Decide the system of record for each object: inspection plans and lots in SAP, samples and analytical results in LIMS. - Standardise master data first: material, plant, batch, master inspection characteristics and method IDs must map one to one between SAP and the LIMS. - Choose the transport: QM-STI for classic subsystem exchange, BAPIs or RFC through middleware, IDocs, or an API on the SAP side. - Pass the inspection lot, operations, characteristics, sample information and batch from SAP to the LIMS when the lot is created. - Return results by characteristic to the inspection lot using the results recording BAPI or the subsystem interface. - Decide where the usage decision is made. Either the LIMS proposes and SAP decides, or SAP makes it automatically from valuation. - Test rejections, retests, re-sampling, cancelled lots and rounding or unit conversion before go-live. ## Sections ### The interface options **Body:** QM-STI is SAP's subsystem interface for QM. External systems register as subsystems, receive inspection tasks, and return results. It is the older, well-known path for lab and measuring systems and is still found in many plants. The alternative is calling released function modules and BAPIs, such as BAPI_INSPLOT_GETLIST and BAPI_INSPOPER_RECORDRESULT, usually through middleware like SAP Integration Suite or an ESB, with IDocs where asynchronous exchange is preferred. Many LIMS vendors supply a connector, so check what yours supports before building one. ### What flows each way **Body:** Outbound from SAP: inspection lot number, material, batch, plant, characteristics with tolerance, method and unit, sample size, and due dates. Inbound to SAP: results per characteristic (mean values or single values), valuation (accept or reject), and in some designs the proposed usage decision with a code from the catalog. Keep units and decimals consistent. A common failure is the LIMS reporting in a different unit or precision than the master inspection characteristic, so SAP rejects the value or valuates it wrongly. ### Where integrations fail **Body:** Typical problems are locked inspection lots (the result is being edited in QE51N), characteristics that do not exist in the plan, closed characteristics already confirmed, and lots whose usage decision is already made. Treat the interface as eventually consistent: queue results, log every message, and build a visible error list so the lab does not have to guess whether a result reached SAP. Plan for reprocessing, because lab systems resend after downtime. ## Pitfalls - Mapping characteristics by text instead of by master inspection characteristic ID. - Letting both systems make the usage decision, creating conflicting stock postings. - Ignoring batch determination and shelf-life data that QM and LIMS both touch. - No retry or dead-letter handling when SAP is down for maintenance. - Skipping unit and precision tests on real values. ## Ai Angle A private AI layer can sit beside the integration rather than replace it: it can read inspection lots and results from SAP QM, explain why a lot is stuck waiting for LIMS results, and summarise out-of-spec trends. Any write to SAP still goes through the controlled interface with approval. ## Faq ### What is QM-STI? **Answer:** It is the SAP QM subsystem interface that lets external systems such as lab or measuring systems receive inspection requests and return results. It is a classic option for LIMS and shop-floor measuring tools connected to SAP QM. ### Can LIMS make the usage decision? **Answer:** It can propose or supply a valuation, but the formal usage decision and stock posting are SAP QM functions. Most designs let SAP decide automatically from valuation and have a person confirm exceptions. ### Does SAP provide a LIMS? **Answer:** SAP QM covers inspection planning and results but not a full laboratory system. Sample management, instruments and analytical workflows normally come from a separate LIMS product. ### Which interface should I choose? **Answer:** Use what your LIMS vendor supports and what your integration team can run. QM-STI suits classic subsystems, BAPIs and IDocs suit middleware designs, and newer APIs suit S/4HANA with a cloud or hybrid platform. ## Search terms sap qm integration with lims, sap qm and lims integration, lims integration with sap qm, qm-sti sap, sap lims interface, bapi_inspoper_recordresult, sap qm results recording interface, sap lab integration --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json