SAP S/4HANA

Active

An AI agent for SAP S/4HANA. It works in a scene with a live connection to SAP S/4HANA. It asks before it writes, and every run is traced.

Connect Daslab scenes to SAP S/4HANA. Pin business partners, sales orders, and products as assets; query them with typed tools; or reach the full OData surface (purchase orders, billing, finance, stock, …) via the generic escape hatch. Works with real S/4HANA Cloud tenants and the public SAP API Business Hub sandbox.

Data & Databases Custom 19 asset types

What you can connect

Add these to your scene and AI gets access.

S/4HANA Account S/4HANA Accounts

A SAP S/4HANA tenant — OAuth, Basic, or the public API Business Hub sandbox.

NameAuthTenant

Business Partner Business Partners

A customer, supplier, or other business-partner master-data record.

BPNameCategoryGrouping

Sales Order Sales Orders

A sales order (OTC — order-to-cash).

OrderSold-toNet AmountCurrencyStatusCreated

Product Products

A material / product master record.

ProductTypeUoMGroup

Purchase Order Purchase Orders

A purchase order (PTP — procure-to-pay).

POSupplierTypeStatusCurrencyCreated

Purchase Requisition Purchase Requisitions

A request to procure — the upstream of a Purchase Order in P2P.

PRTypeDescription

Purchase Contract Purchase Contracts

An outline agreement with a supplier — POs draw down against it.

ContractSupplierTargetCurrencyValid FromValid To

Material Stock Material Stock

Inventory snapshot for a material — quantities live in the per-account-mode breakdown.

MaterialUnit

Inbound Delivery Inbound Deliveries

An expected goods receipt from a supplier — the Receiving tab in Fiori.

DeliverySupplier DocTypeDelivery Date

Outbound Delivery Outbound Deliveries

A goods issue to a customer — the Shipping tab in Fiori (closes the O2C loop).

DeliveryTypeSold-toShip-toDelivery DateGI Posted

Material Document Material Documents

A goods movement — receipt, issue, transfer, or reversal posted to inventory (audit trail for stock).

Doc #YearMovementPosting DateReference

Process Order Process Orders

A process-industry production order — recipe-based manufacturing with operations and components.

OrderTypeMaterialPlantStartEnd

Request For Quotation Requests For Quotation

A sourcing event — invite suppliers to bid on a procurement need.

RFQNameTypeCurrencyPublishedStatus

Supplier Invoice Supplier Invoices

An invoice posted by a supplier — A/P side of procure-to-pay.

InvoiceSupplierAmountCurrencyPostedPayment

Billing Document Billing Documents

A billing document (A/R invoice on the sales side).

BillingSold-toAmountCurrencyBilled

Sales Quotation Sales Quotations

A sales quotation (the pre-order step in O2C).

QuotationSold-toAmountCurrencyStatus

Production Order Production Orders

A manufacturing order — produce a material in a plant.

OrderMaterialPlantPlanned StartPlanned End

Query Queries

A saved OData query against S/4HANA. Pin to see matching records as a live widget that updates each time the scene refreshes.

TitleEntityFilterOrderMax

Guide Guides

SAP S/4HANA setup guides, troubleshooting, and reference — pin one to read it in-scene, or ask the agent.

TitleSummary

Connect SAP S/4HANA over MCP

Daslab is itself an MCP server.

Connect SAP S/4HANA in a scene, then pin that scene's URL in Claude Code, Cursor, or any MCP client. The agent there gets your SAP S/4HANA tools, and your approval gate and trace travel with them.

https://daslab.run/mcp/<your-world>/<your-scene>

One scene can hold SAP S/4HANA and everything else you connect, so a single endpoint carries them all. Set up a client.

Use cases

Pin a customer and browse their sales orders, invoices, and payments
Query today's sales across plants and render as a chart
Look up a material across the catalog and feed it to downstream tools

Knowledge base

Connecting on-prem SAP S/4HANA on-prem
Activate the standard OData services, create a technical user, and reach a private-network tenant (Cloud Connector / tunnel) — no code changes.
When your system has no standard SAP APIs custom-estates
On-premise systems often register only custom Z* services, so the typed tools have nothing to call. Three routes — activate the standard services, read-only SQL, or install a small view set — with the authorization each one really needs and why installed objects go through a transport rather than straight into production.

Ships with the integration — agents read these with docs_read, before the account is connected. Knowledge bases →