SAP S/4HANA Cloud

ERP & FinanceService accountLive

Connect your customers' SAP S/4HANA Cloud tenants so your product can read and write business documents through the S/4HANA OData and REST APIs. The customer's SAP basis admin registers an OAuth client in their tenant; Askel mints client_credentials tokens per request so no long-lived secrets are stored.

Book a demo

View docs

What you can do

Read and create sales orders

Fetch open sales orders by order type, customer, or creation date, or POST new orders using the Sales Order API (A_SalesOrder). Covers header data, line items, pricing conditions, and delivery blocks.

Manage business partners and customers

Read and create business partner records including name, address, tax numbers, and role assignments. Used to sync your product's customer master with the S/4HANA BP master data.

Read purchase orders and GR/IR status

Fetch purchase orders and their goods-receipt and invoice-receipt status. Useful for procurement-visibility workflows that surface open POs or unmatched receipts to your product's dashboard.

Access material master data

Read plant and valuation data, units of measure, and material descriptions from the Material Master API. Lets your product resolve product codes without a separate master-data export.

Read financial posting documents

Fetch FI documents from the Journal Entry API (A_JournalEntry) for reconciliation or cost-allocation workflows that need to see actual posted amounts in the customer's S/4HANA ledger.

Trigger output management for documents

Request output processing for sales or billing documents via the Output Management API so your product can trigger invoice PDF generation or EDI dispatch without navigating the SAP GUI.

Sample use case

Pulling open sales orders into a customer order-visibility dashboard

You sell an order-management visibility platform. A new customer, Nordvik Manufacturing AG, processes thousands of sales orders per day in SAP S/4HANA Cloud. Their sales ops team needs a live view of open orders, delivery status, and billing status that does not require logging into the SAP Fiori launchpad.

1
Basis admin registers an OAuth client
Nordvik's SAP basis admin opens SAP BTP in their S/4HANA Cloud tenant, creates an OAuth client under the Communication Arrangements for the Sales Order (read) scope, and downloads the client ID and secret. They paste both into your product's connection wizard.
2
Token validation
Askel makes a client_credentials token request to Nordvik's tenant token URL using the provided client ID and secret. The token is valid for one hour. Askel immediately discards it and mints a fresh one on the first real API call.
3
Sales order fetch
Askel calls the A_SalesOrder OData endpoint with a filter for open orders created in the last 30 days. Nordvik's tenant returns 4,200 order header records including order number, customer, requested delivery date, and overall status.
4
Line items and delivery status read
For orders flagged as partially delivered, Askel calls A_SalesOrderItem to read individual line items and their delivery quantities. Your dashboard shows Nordvik's sales ops team which orders are on track and which are at risk.
5
Dashboard live before training
Nordvik's sales ops team sees their first live order view in your platform before the end of the onboarding call. No SAP GUI navigation training is needed for this view.

Authentication

Service account

The customer's SAP basis admin creates an OAuth client in their S/4HANA Cloud tenant via Communication Arrangements in SAP BTP, selecting the API scopes needed. They provide Askel with the client ID, client secret, and tenant-specific token URL. Askel mints a client_credentials token per request and never stores access tokens. The client secret is stored encrypted in Askel and never forwarded to your servers.

Data flow

How Askel sits between your product and the customer's system

Sales ordersBusiness partnersPurchase ordersMaterial masterFI documents

Related integrations

Oracle NetSuite

Read and write records in customer NetSuite accounts via SuiteTalk REST.

Business Central

Manage items, customers, and transactions in customer Business Central tenants.

Dynamics 365 F&O

Read and write OData entities in customer Dynamics 365 Finance and Operations environments.

FAQ for SAP S/4HANA Cloud

Does this work with SAP S/4HANA on-premises as well as the public cloud edition?+

This integration targets S/4HANA Cloud Public Edition, which uses SAP BTP-managed OAuth clients and the standard S/4HANA Cloud API endpoints. S/4HANA on-premises and private-cloud editions may use different auth mechanisms (Basic auth or certificate-based OAuth) and require a different connector setup.

Which SAP APIs are covered?+

Askel can call any S/4HANA Cloud OData or REST API that the customer's OAuth client has been scoped for. Common starting points are the Sales Order, Business Partner, Purchase Order, and Journal Entry APIs. The customer's basis admin controls which APIs are exposed by choosing the correct Communication Scenario in the Communication Arrangement.

How do we handle SAP's per-tenant API host?+

Each S/4HANA Cloud tenant has a unique host of the form <tenant-id>-api.s4hana.cloud.sap. The customer provides this host as part of the connection setup. Askel stores it per connection and prefixes every API path with it.

What happens if the OAuth client secret is rotated?+

Askel's token requests will start failing, which surfaces as a credential-expired alert on the customer's connection page. The customer's basis admin generates a new secret in BTP and pastes it into Askel to restore the connection.

Ready to ship integrations faster?customers faster?implementations faster?

Join onboarding teams delivering integrations without the engineering queue,
catching drift before it breaks, and hitting go-live dates.

Book a demo

Security & Compliance

Askel.ai

Automation for customer onboarding teams

Product

Features Documentation Integrations

Company

About us Our team Blog Contact

Resources