AlisQI SAP ECC integration

Overview

The AlisQI – SAP ECC integration can be configured to support bi-directional data exchange. SAP acts as the system of record for master and transactional data, while AlisQI manages quality execution, inspections and results.

Typical use cases include:

• Synchronizing materials, batches, vendors and customers from SAP to AlisQI
• Triggering inspections in AlisQI based on SAP transactions, such as goods receipts, production orders or SAP QM inspection lots
• Sending inspection results, usage decisions and quality statuses back to SAP

Integration type

✅ Interface-based integration (IDocs, BAPIs/RFCs and SOAP web services)

✅ Middleware-driven (SAP PI/PO, SAP Integration Suite, MuleSoft, SEEBURGER or other third-party middleware)

✅ Event-driven (change pointers, output determination) or scheduled synchronization

✅ Bi-directional data flow

Key capabilities

The integration can be configured to support the following capabilities:

• Create and update master data in AlisQI based on SAP data (e.g. materials, batches, vendors, customers, plants)
• Trigger inspections based on SAP documents, detected via IDocs, output determination, change pointers or scheduled polling
• Work alongside SAP QM: SAP creates and maintains the inspection lot, inspection execution takes place in AlisQI, and the integration records results, the usage decision and, where applicable, stock postings in SAP
• Work without SAP QM: update batch characteristics, batch status or stock status based on AlisQI results
• Support batch-level or material-level quality tracking
• Use middleware for transformation, routing and orchestration
• Log and monitor integration flows centrally

Architecture

The integration uses middleware as an intermediary layer between SAP ECC and AlisQI.

High-level architecture:

• SAP ECC exposes data and events via:
  • IDocs (e.g. MATMAS, BATMAS, CREMAS, DEBMAS)
  • BAPIs/RFCs (e.g. inspection lot, results recording and batch BAPIs)
  • SOAP web services (configured via SOAMANAGER), directly or through middleware
  • OData services via SAP Gateway, where available
• Middleware (SAP PI/PO, SAP Integration Suite, MuleSoft, SEEBURGER or other) handles:
  • Authentication
  • Data transformation (e.g. IDoc or BAPI structures to JSON)
  • Business logic and routing
  • Connectivity to SAP ECC (e.g. via SAP Cloud Connector for cloud middleware)
• AlisQI exposes APIs to:
  • Receive master and transactional data
  • Create or update inspection records
  • Return inspection results and statuses

Use SAP application interfaces for this integration; avoid direct database access and direct updates to SAP application tables. This architecture decouples both systems and allows flexible scaling and error handling.

Prerequisites

Before setting up the integration, ensure the following:

• Active AlisQI subscription with API access
• SAP ECC 6.0 (customer-managed or hosted)
• Access to one of the following middleware options:
  • SAP Process Orchestration (PI/PO), for existing landscapes; SAP positions Integration Suite as its successor, and PO 7.5 mainstream maintenance ends in 2027
  • SAP Integration Suite (Cloud Integration), with SAP Cloud Connector
  • Third-party middleware, such as MuleSoft Anypoint Platform (with its SAP connector for IDocs, BAPIs and RFCs) or SEEBURGER Business Integration Suite (with SAP-certified adapters)
• Required SAP interfaces activated and accessible: IDoc partner profiles and ports, RFC destinations, and/or SOAP web services
• Technical (communication) user accounts in both systems
• A decision on the role of SAP QM: either SAP creates and maintains the inspection lot, inspection execution takes place in AlisQI, and the integration records the results, usage decision and, where applicable, stock postings in SAP; or AlisQI manages inspections without SAP QM and the integration updates SAP logistics objects

Setup and configuration

Step 1: Prepare SAP ECC

• Configure IDoc message types, partner profiles and ports for outbound master data (e.g. via the ALE distribution model)
• Create RFC destinations and authorize the required BAPIs, or expose SOAP web services via SOAMANAGER, used directly or through middleware
• Set up change pointers, output determination or user exits to signal relevant transactions
• Create a technical user with sufficient (and minimal) authorizations
• Identify relevant business objects (e.g. Materials, Batches, Purchase Orders, Goods Receipts, Production Orders, Inspection Lots)
• If SAP QM is used, align inspection types, inspection characteristics (master and inspection-plan level), specifications and usage decision codes with the AlisQI setup

Step 2: Configure middleware

• Create integration flows or scenarios
• Configure connectors for:
  • SAP ECC (IDoc, RFC and/or SOAP adapter)
  • AlisQI API
• Define triggers (event-based or scheduled)
• Map SAP data structures to AlisQI entities

Step 3: Configure AlisQI

• Generate an API key in AlisQI
• Identify analysis sets for incoming and outgoing data, depending on whether entities represent master data or transactional data
• Align inspection templates and selection lists with SAP data (e.g. material numbers, plants, inspection characteristics). See AlisQI templates for SAP master data siblings.

Authentication

AlisQI authentication

• Uses API key authentication
• API keys are generated in the AlisQI platform
• Keys must be stored securely in the middleware
• API supports access_token url parameter or Bearer Authentication headers

SAP authentication

• Technical RFC/communication user; SNC is recommended to secure RFC connections
• Basic authentication or X.509 client certificates for SOAP web services
• Credentials managed by the middleware
• Secure HTTPS (or SNC for RFC) communication required

Data mapping

Data mapping is handled in the middleware layer. Common mappings include:

Exact mappings depend on the SAP configuration and the AlisQI data model that you can define yourselves.

Results are typically written back to SAP using one of the following, depending on whether SAP QM is active:

• With SAP QM: results recording and usage decision on the inspection lot, where, depending on configuration, the usage decision can trigger stock postings (e.g. from quality inspection stock to unrestricted or blocked stock); SAP also offers separate inspection lot stock postings
• Without SAP QM: batch classification characteristics, batch status (restricted/unrestricted), stock transfer postings, or custom fields for quality statuses, inspection references or blocking indicators

These options have different effects. Classification and custom fields store quality values, batch status controls batch usability, and stock postings change the stock type. A stored quality value does not block inventory unless an enforcement mechanism is configured explicitly.

Error handling

• Middleware captures and logs all integration events (e.g. PI/PO message monitoring, or Monitor Message Processing in SAP Integration Suite, Cloud Integration)
• Failed messages can be retried or reprocessed
• AlisQI returns standard HTTP status codes and error messages
• SAP errors are logged in IDoc status monitoring (e.g. WE02/BD87) and RFC logs

Common error scenarios include authentication failures, data validation issues, mapping errors and locked SAP objects (e.g. a batch or inspection lot being edited by another user).

Security and rate limits

• All communication uses HTTPS (or SNC for RFC connections)
• API keys and credentials must be stored securely
• SAP technical users follow the least-privilege principle
• Middleware controls access and message routing; SAP Cloud Connector controls access from cloud middleware
• AlisQI enforces API rate limits to ensure platform stability

Example integration flow

Scenario: Incoming goods inspection

1. A goods receipt for a purchase order is posted in SAP ECC (with SAP QM and an active inspection setup for the material, an inspection lot is created automatically)
2. Middleware detects the transaction via an IDoc, output determination or polling
3. An inspection is created in AlisQI, including material, batch, vendor and, if applicable, the inspection lot number
4. The quality inspection is executed in AlisQI
5. Inspection results are sent back to SAP
6. SAP updates the quality status: with SAP QM through results recording and a usage decision; without SAP QM through batch characteristics, batch status or a stock transfer

Troubleshooting