AlisQI SAP S4/HANA integration

Overview

The AlisQI – SAP S/4HANA 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/products, batches, suppliers 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
• Supporting compliant and auditable quality workflows

Integration type

✅ API-based integration (OData and SOAP APIs)

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

✅ Event-driven (SAP business events) 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/products, batches, suppliers, customers, plants)
• Trigger inspections based on SAP documents, detected via SAP business events, output management 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 S/4HANA and AlisQI.

High-level architecture:

• SAP S/4HANA exposes data and events via:
  • OData and SOAP APIs published on the SAP Business Accelerator Hub (e.g. Product, Batch, Business Partner, Material Document, Inspection Lot)
  • SAP business events (e.g. via SAP Event Mesh)
  • BAPIs/RFCs and IDocs (on-premise and Private Cloud)
• Middleware (SAP Integration Suite, MuleSoft, SEEBURGER or other) handles:
  • Authentication
  • Data transformation
  • Business logic and routing
  • Connectivity to on-premise or Private Cloud systems (e.g. via SAP Cloud Connector)
• 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 S/4HANA (on-premise, Private Cloud or Cloud Public Edition)
• Access to one of the following middleware options:
  • SAP Integration Suite (Cloud Integration), with SAP Cloud Connector for on-premise and Private Cloud systems
  • Third-party middleware, such as MuleSoft Anypoint Platform (with its SAP connector) or SEEBURGER Business Integration Suite (with SAP-certified adapters)
• Required SAP APIs activated and accessible; for Cloud Public Edition, a communication arrangement for the relevant communication scenarios
• 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 S/4HANA

• Identify the APIs to use on the SAP Business Accelerator Hub (e.g. Product, Batch, Business Partner, Material Document, Inspection Lot)
• Activate the required OData services (on-premise/Private Cloud) or set up a communication system, communication user and communication arrangement (Cloud Public Edition)
• Configure business events or output management if the integration is event-driven
• 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 S/4HANA (OData/SOAP and, where relevant, IDoc or RFC adapters)
  • 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 endpoints 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)

Authentication

AlisQI authentication

• Uses API key authentication
• API keys are generated in the AlisQI platform
• Keys must be stored securely in the middleware

SAP authentication

• Communication user with basic authentication, OAuth 2.0 or X.509 client certificates, depending on edition and API
• Credentials managed by the middleware
• Secure HTTPS 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. 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 API/OData error logs (e.g. SAP Gateway error log)

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
• 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 to on-premise and Private Cloud systems
• 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 S/4HANA (with SAP QM and an active inspection setup for the material, an inspection lot is created automatically)
2. Middleware detects the transaction via a business event or polling
3. An inspection is created in AlisQI, including material, batch, supplier 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

Migrating from SAP ECC

If you are moving from SAP ECC to SAP S/4HANA, the AlisQI side of the integration largely carries over. On the SAP side, interfaces typically move from IDocs and BAPIs to released OData APIs and business events, and vendor and customer masters are replaced by Business Partners. Plan the middleware mappings accordingly.