The SAP S/4HANA connector is the bridge most enterprise tenants need to make Invoice & AP, Procure-to-Pay, and Finance work end-to-end. SAP holds the master data + the GL; Apragya AI handles the intake, the agent layer, and the workflow; the connector ferries records both ways.
What it connects
- Material master, vendor master, customer master, GL account master (read)
- Purchase orders, sales orders, goods receipts (read + write)
- Invoices (write - posting via SAP MIRO transaction)
- Journal entries (write)
- Custom OData services if your SAP team has exposed them
Connect SAP S/4HANA
- Sidebar > Integrations > Connectors > SAP S/4HANA > Connect
- Provide the OData v4 endpoint URL (typically https://<sap-host>/sap/opu/odata/sap/<service>/)
- Pick the authentication option that matches your SAP setup: Basic + SAP user, SAML 2.0, OAuth 2.0, X.509 client certificate
- Verify the connection - the connector runs a metadata fetch + an idempotent read to confirm credentials and routing
Batch vs real-time
- Batch: scheduled OData query, typically every 30 min to 4 hours depending on master-data volatility
- Real-time: SAP Event Mesh (if your SAP team has it stood up) pushes change events; the connector subscribes
- Mix: master data on a 4-hour batch, transactional data real-time
SAP rate limits are governed by your Gateway tier, not by the connector. If you see 503s under load, talk to your SAP basis team about the Gateway thread budget - the connector respects per-host rate limits but cannot raise them.
Common gotchas
- OData strict-typing - SAP's date fields use a non-standard /Date(...)/ format; the connector handles this but custom field types need explicit transformation rules
- Unicode in master data - if your SAP runs ECC + S/4 in mixed mode, watch for codepage issues; the connector defaults to UTF-8
- Long-running queries - any OData query over 4 minutes will time out at the SAP Gateway; chunk large reads or move to a delta-token-based incremental