Technical user (live)
A read-only SAP communication user with least-privilege PFCG roles; AIPaddle adds filters from the asker's department scope and logs the real person. Good for getting query scenarios live fast.
Your most important data lives in the ERP. AIPaddle doesn't build a parallel copy: APIs only, never the database; read first, write-back only with approval; and your existing identities and permissions decide what AI can see and do in SAP.
Select a channel to see how data moves between WeCom, AIPaddle, SAP BTP and S/4HANA. Cycles automatically by default.
Fiori / BTP apps
Extension API /api/ext/v1: hashed keys, rate limits by key and IP, origin allow-lists
Call published agents from inside SAP screens, for example asking about a supplier's delivery record on a purchase order.
S/4HANA OData APIs published through API Management
API plugin: import OpenAPI, split operations into tools; parameter constraints, field masking, domain allow-lists
Ask about orders, stock and collections in WeCom; the PMO reads project budgets and actual costs.
An OData MCP server (self-built or third-party) exposing CDS views / OData services as MCP tools
MCP connection: company-level credentials, tools discovered at runtime
Let agents discover available SAP queries without configuring each interface.
S/4HANA business events delivered through Event Mesh
Webhook trigger → workflow / PMO reminder; IP allow-list and rate limits
When a sales order is created, a delivery slips or an invoice is blocked, the owner is notified in the project group.
Integration Suite iFlows wrapping BAPI / OData write services
Workflow + approval: irreversible actions are approved before the call
Creating a purchase requisition or changing a delivery date runs only after an authorized person approves in the group.
"Live" refers to AIPaddle's general integration capabilities; a dedicated SAP connector pack is planned.
A South China salesperson asks the assistant in WeCom: "Has customer A's order shipped?"
WeCom identity tells who, which department and which roles; client-side parameters are never trusted.
The department data scope adds a filter, South China sales org only, and picks the approved "sales order query" tool.
Using encrypted communication-user credentials, OData is called through API Management (via Cloud Connector on-premise).
Requests API_SALES_ORDER_SRV and the delivery API; SAP checks the communication user's PFCG role and org levels, read-only.
Order and delivery status come back; AIPaddle masks fields such as unit price and contact phone per tool settings.
"Shipped on 6 Oct, delivery 80001234, expected 9 Oct." Document numbers included for follow-up.
Who asked, which API was called, how many records and tokens, all visible to admins.
Illustrative data.
Identity mapping: employee ID / email ↔ WeCom userid ↔ SAP user. Maintained by IPS / SCIM and WeCom sync, so leavers and transfers take effect everywhere at once.
WeCom SSO is live; SAML / OIDC to your IdP.
WeCom directory sync is live; IPS / SCIM provisioning.
An SAP communication user, narrowed by AIPaddle department data scopes.
OAuth 2.0 SAML Bearer, so SAP authorizes by the person's own PFCG roles.
SAP org levels → AIPaddle department data scopes, logged on both sides.
A read-only SAP communication user with least-privilege PFCG roles; AIPaddle adds filters from the asker's department scope and logs the real person. Good for getting query scenarios live fast.
AIPaddle exchanges a SAML bearer assertion for an OAuth token on the person's behalf, so SAP authorizes by that person's PFCG roles and org levels and its audit log shows the real user. Suited to sensitive data and write-back.
Confirm SAP release and deployment, available OData / BAPIs, BTP subscriptions and network; pick 3–5 high-frequency queries.
Activate services or communication arrangements, create a read-only communication user with least-privilege PFCG roles; configure Cloud Connector on-premise.
Import OpenAPI → pick operations → set masking and allow-lists → draft, review, publish under the same governance as other objects.
Build an agent or workflow, pilot by department scope, verify fields and permissions, keep acceptance records.
Add event alerts and PMO warnings; add approvals and principal propagation for write-back or sensitive data.
A salesperson asks in WeCom: "Has customer A's order shipped?"
The "business query assistant" agent identifies customer and document
Read-only OData: sales order → delivery status
Replies with shipping status, ETA and document numbers
Legal drops a new contract into the project space
The AI contract reviewer reads the contract and review standard
Read-only OData: supplier master data and payment terms
Produces a clause risk list for a person to accept
The PMO's 08:00 daily check
The PMO Agent compares plan and actuals
Read-only OData: project budget, commitments and actual costs
Variance over threshold → warning in the project group, owner @-mentioned
SAP emits a "delivery delayed" business event
A webhook trigger starts a workflow
Read-only OData: order and customer details
Pushed to the project group with the owner @-mentioned
A 30-minute online demo built around your industry, including how we would connect to your WeCom and ERP.