ShenZhen Nebula Rover Technology Limited·深圳市星云智航科技有限公司Hotline400-990-0246Emailperry.xu@airover.net
SAP / ERP integration

Connected data.
One identity.

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.

  • 1APIs only, no direct database access
  • 2Read first
  • 3Write-back needs approval
  • 4Encrypted credentials
  • 5Every call audited
Integration architecture

Five channels: how data flows in and out

Select a channel to see how data moves between WeCom, AIPaddle, SAP BTP and S/4HANA. Cycles automatically by default.

AIPaddleSAP BTPSAP S/4HANACloud Connector (on-premise)③Extension APIFiori / BTP appsFiori Launchpad①API plugin · toolAPI ManagementOData API⑤MCP connectionOData MCP ServerCDS view OData②Webhook triggerEvent MeshBusiness events④Workflow + approvalIntegration Suite iFlowBAPI / OData writePlannedAgents · workflowsIdentity · permissions · auditEmployeesWeComWeb / mobile
SAP side

Fiori / BTP apps

AIPaddle side

Extension API /api/ext/v1: hashed keys, rate limits by key and IP, origin allow-lists

Used for

Call published agents from inside SAP screens, for example asking about a supplier's delivery record on a purchase order.

"Live" refers to AIPaddle's general integration capabilities; a dedicated SAP connector pack is planned.

One query, step by step

"Has customer A's order shipped?"

01 · Ask Employee · WeCom → AIPaddle

A South China salesperson asks the assistant in WeCom: "Has customer A's order shipped?"

Illustrative data.

Shared authentication

One enterprise identity, three systems

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.

Enterprise IdPSAP Cloud Identity Services (IAS / IPS) · Microsoft Entra ID · WeCom directory
SAML / OIDC sign-inAIPaddleUsers · departments · roles
WeCom OAuth SSOWeComuserid · directory
IAS sign-inSAP S/4HANABTP · PFCG roles · org levels
Employee ID / email ↔ WeCom userid ↔ SAP user
  1. ①
    Single sign-onPlanned

    WeCom SSO is live; SAML / OIDC to your IdP.

  2. ②
    User and org provisioningPlanned

    WeCom directory sync is live; IPS / SCIM provisioning.

  3. ③
    Calling SAP · technical userLive

    An SAP communication user, narrowed by AIPaddle department data scopes.

  4. ④
    Calling SAP · principal propagationPlanned

    OAuth 2.0 SAML Bearer, so SAP authorizes by the person's own PFCG roles.

  5. ⑤
    Permission alignment and auditPlanned

    SAP org levels → AIPaddle department data scopes, logged on both sides.

Whose identity does AIPaddle use to call SAP?

A

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.

B

Principal propagation (planned)

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.

Same question, different people, different data

Q"How are collections this month?"
  1. Enterprise identityWeCom SSO · Sales / South China
  2. ERP role mappingERP: sales manager (South China sales org)
  3. Data scopeSouth China customers only · line detail for own accounts only
  4. AnswerSouth China collected 12.4M this month, 82% of target; 1 of your 3 accounts is 15 days overdue.
Figures are illustrative.
Connection methods

The right method for each SAP product, no changes to the ERP core

Read
OData / SOAP APIs published on SAP Business Accelerator Hub, e.g. API_SALES_ORDER_SRV, API_BUSINESS_PARTNER, API_PRODUCT_SRV
Setup
Create a communication system, communication user and communication arrangement in SAP, enabling only the scenarios needed
Events
Business events pushed to AIPaddle webhooks via SAP Event Mesh
Identity
SAP Cloud Identity Services (IAS / IPS); principal propagation via OAuth 2.0 SAML Bearer
Implementation

Start with one query scenario and expand

  1. 01

    Assess

    Confirm SAP release and deployment, available OData / BAPIs, BTP subscriptions and network; pick 3–5 high-frequency queries.

  2. 02

    Enable in SAP

    Activate services or communication arrangements, create a read-only communication user with least-privilege PFCG roles; configure Cloud Connector on-premise.

  3. 03

    Connect in AIPaddle

    Import OpenAPI → pick operations → set masking and allow-lists → draft, review, publish under the same governance as other objects.

  4. 04

    Pilot

    Build an agent or workflow, pilot by department scope, verify fields and permissions, keep acceptance records.

  5. 05

    Expand

    Add event alerts and PMO warnings; add approvals and principal propagation for write-back or sensitive data.

Typical scenarios

From one message in WeCom to one controlled SAP call

  1. Trigger

    A salesperson asks in WeCom: "Has customer A's order shipped?"

  2. AIPaddle

    The "business query assistant" agent identifies customer and document

  3. SAP call

    Read-only OData: sales order → delivery status

  4. Result

    Replies with shipping status, ETA and document numbers

Want to see it running in your business?

A 30-minute online demo built around your industry, including how we would connect to your WeCom and ERP.

Book a demo