Database · Beta
SAP HANA
API integration
Ship Database features without building the integration. Full SAP HANA API access via Proxy and 10+ MCP-ready tools for AI agents — extend models and mappings to fit your product.
Built for specific customer use cases. Issues are resolved quickly.
Talk to usUse Cases
Why integrate with SAP HANA
Common scenarios for SaaS companies building SAP HANA integrations for their customers.
Sync master data from SAP HANA into your SaaS product
Pull Business Partners, Material Masters, G/L Accounts, and Cost Centers from your customers' SAP environments so your application always reflects their source of truth — without asking them to export CSVs or maintain flat files.
Write back transactional documents to SAP HANA
When your SaaS completes a workflow — like approving an expense, closing a work order, or fulfilling an order — push the resulting Journal Entry, Supplier Invoice, or Goods Issue directly into SAP so your customers avoid double data entry and reconciliation headaches.
Power real-time inventory and order visibility
SaaS companies in supply chain, e-commerce, or field service need live stock levels and order statuses from SAP HANA. Offering this integration lets your users make decisions based on real-time ERP data rather than stale overnight extracts.
Automate procure-to-pay workflows across SAP and your platform
Spend management and AP automation products can read vendor data and chart of accounts from SAP, then write back completed invoices or payment postings — closing the loop between your specialized workflow and the customer's general ledger.
React to SAP business events in real time
Instead of polling for changes, listen for SAP events like new Sales Orders or inventory movements via SAP Event Mesh, enabling your SaaS to trigger downstream automations the moment something happens in your customer's ERP.
What You Can Build
Ship these features with Truto + SAP HANA
Concrete product features your team can ship faster by leveraging Truto’s SAP HANA integration instead of building from scratch.
Automatic vendor and customer directory sync
Continuously import Business Partner records from SAP HANA so your app's contact lists, vendor directories, or customer databases stay current without manual uploads.
Real-time product catalog and inventory display
Pull Material Master data and plant-level stock quantities from SAP HANA to power storefront availability, configure-price-quote flows, or warehouse dashboards inside your product.
One-click journal entry and invoice write-back
Let users push approved expenses, invoices, or accruals from your platform directly into SAP's General Ledger as properly coded financial documents.
Sales order creation from external workflows
Convert completed carts, signed quotes, or approved requisitions in your SaaS into SAP Sales Orders via API, triggering downstream fulfillment in your customer's warehouse.
Cross-plant inventory deduction on field events
When a technician logs parts usage or a warehouse confirms a shipment in your app, automatically post a Goods Issue in SAP HANA to keep inventory valuations accurate.
G/L account and cost center picker
Embed a native SAP-aware dropdown in your UI that lets end users select the correct General Ledger account or Cost Center when categorizing transactions, eliminating coding errors.
SuperAI
SAP HANA AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
list_all_sap_hana_users
List users in SAP Cloud Identity Services (Identity Authentication) via the SCIM 2.0 API (GET /service/scim/Users). Returns SCIM user resources with userName, name, emails, active, userType, groups, enterprise and SAP extension attributes and meta timestamps. Supports SCIM filter expressions (e.g. userName eq "x" or meta.lastModified gt "date"), attribute selection, sorting and startIndex/count paging. No parameters are required.
get_single_sap_hana_user_by_id
Get a single user from SAP Cloud Identity Services by id via SCIM 2.0 (GET /service/scim/Users/{id}). Returns the full SCIM user resource including name, emails, phone numbers, active flag, userType, group memberships, enterprise attributes (employeeNumber, department, manager) and SAP specific attributes. Required: id (the user UUID).
create_a_sap_hana_user
Create a user in SAP Cloud Identity Services via the Identity Directory SCIM 2.0 API (POST /service/scim/Users). Requires schemas, userName and at least one email; optional name, active, userType, enterprise and SAP extension attributes. Set the SAP extension sendMail to true to send the activation email. Returns the created SCIM user with its generated id.
update_a_sap_hana_user_by_id
Replace a user in SAP Cloud Identity Services (PUT /service/scim/Users/{id}, SCIM 2.0). Sends the full user representation; attributes not included are cleared, so read the user first and resend it with your changes. Required: id and a complete user body with schemas and userName. Returns the updated user.
sap_hana_users_partial_update
Update selected attributes of a user in SAP Cloud Identity Services without resending the whole record (PATCH /service/scim/Users/{id}, SCIM PatchOp). Use operations such as replace active=false to deactivate, replace name.givenName, or add emails. Required: id (query) and Operations.
delete_a_sap_hana_user_by_id
Delete a user from SAP Cloud Identity Services (DELETE /service/scim/Users/{id}, SCIM 2.0). This is permanent; to keep history deactivate the user instead with partial_update (replace active with false). Required: id. Returns no content on success.
list_all_sap_hana_groups
List groups in SAP Cloud Identity Services (Identity Authentication) via the SCIM 2.0 API (GET /service/scim/Groups). Returns SCIM group resources with displayName, members (user ids and display names), the SAP group extension (technical name, description, type) and meta timestamps. Supports SCIM filter expressions (e.g. displayName eq "Admins"), attribute selection, sorting and startIndex/count paging. No parameters are required.
get_single_sap_hana_group_by_id
Get a single group from SAP Cloud Identity Services by id via SCIM 2.0 (GET /service/scim/Groups/{id}). Returns the SCIM group resource with displayName, the full member list and the SAP group extension. Required: id (the group UUID).
create_a_sap_hana_group
Create a group in SAP Cloud Identity Services via the Identity Directory SCIM 2.0 API (POST /service/scim/Groups). Requires schemas and displayName; the SAP extension name sets the technical group name; members can be supplied as user ids. Returns the created group with its id.
update_a_sap_hana_group_by_id
Replace a group in SAP Cloud Identity Services (PUT /service/scim/Groups/{id}, SCIM 2.0). Sends the full group including the complete members list; members omitted are removed. Required: id and a full group body. Returns the updated group.
sap_hana_groups_partial_update
Add or remove members or change attributes of a group in SAP Cloud Identity Services (PATCH /service/scim/Groups/{id}, SCIM PatchOp). To add a member: op add, path members, value [{"value": "
delete_a_sap_hana_group_by_id
Delete a group from SAP Cloud Identity Services (DELETE /service/scim/Groups/{id}, SCIM 2.0). Members are not deleted, only the group and its assignments. Required: id. Returns no content on success.
Why Truto
Why use Truto’s MCP server for SAP HANA
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 850+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
How It Works
From zero to integrated
Go live with SAP HANA in under an hour. No boilerplate, no maintenance burden.
Link your customer’s SAP HANA account
Use Truto’s frontend SDK to connect your customer’s SAP HANA account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call SAP HANA
Truto’s Proxy API is a 1-to-1 mapping of the SAP HANA API. You call us, we call SAP HANA, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate SAP HANA’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about SAP HANA on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
How does authentication work for SAP HANA integrations?
SAP S/4HANA typically supports OAuth 2.0 (via SAP Authorization Server), SAML-based SSO, and Basic Authentication for service-to-service calls. For cloud editions, OAuth 2.0 with client credentials is standard. Truto manages the auth lifecycle so your team doesn't need to handle token refresh or credential storage.
What API protocols does SAP HANA expose?
SAP S/4HANA primarily exposes OData v2 and v4 REST APIs through SAP Gateway. The SAP Cloud Application Programming (CAP) model also surfaces RESTful endpoints. BAPI and RFC interfaces exist for on-premise scenarios but are less common in modern integrations.
Are there rate limits or throttling on SAP APIs?
SAP Cloud APIs enforce rate limits that vary by tenant configuration and API type. On-premise deployments depend on the customer's SAP Gateway capacity. Truto can handle retry logic and backoff strategies so your integration remains resilient under throttling.
Is this integration available today on Truto?
SAP HANA is built on request. Truto works with you to scope the specific SAP API endpoints, business objects, and workflows your product needs, then builds and maintains the connector. No generic tools or Unified API mappings exist out of the box — the integration is tailored to your use case.
Can I read and write custom fields or extension fields from SAP?
Yes. SAP S/4HANA supports custom fields via the Key User Extensibility framework, and these fields are exposed through OData APIs. Truto can map these extension fields into your integration so you can read and write customer-specific data.
How fresh is the data when reading from SAP HANA?
Because SAP HANA is an in-memory database with no separate analytics layer, API reads reflect real-time transactional data. There is no replication lag. Data freshness in your app depends on your polling interval or whether you use event-driven patterns via SAP Event Mesh.
SAP HANA
Get SAP HANA integrated into your app
Our team understands what it takes to make a SAP HANA integration successful. A short, crisp 30 minute call with folks who understand the problem.