ERP Integration: SAP S/4HANA

SAP S/4HANA is SAP’s enterprise-level ERP platform, used by large organizations for integrated management of finance, logistics, purchasing, sales, and controlling. Integration is done via OData APIs provided natively by the system.

This article guides you through preparing the SAP environment, configuring the credential, and details the reports available from this connector. For the step-by-step guide to using it in the data preparation flow — connector selection, credential, report, and parameters — see the ERP Step article.

Preparing the SAP environment — services and authorizations

The integration consumes SAP S/4HANA’s standard OData APIs, which are delivered inactive for security reasons. Three actions by the team that administers SAP (Basis/security) prepare the environment:

1. Activate the OData services

In transaction /n/IWFND/MAINT_SERVICE (Activate and Maintain Services), activate the services corresponding to the reports that will be used:

For the trial balance, the two confirmed services are C_TRIALBALANCE_CDS / C_TRIALBALANCE and C_GLACCOUNTBALANCEQUERY_CDS / C_GLACCOUNTBALANCEQUERY — the latter is common in environments with SAP Fiori.

In addition to the report services, the SAP Gateway catalog service (/IWFND/CATALOGSERVICE;v=2) must be accessible — this is how the platform discovers the services available in the environment.

The endpoint pattern is https://{host}:{porta}/sap/opu/odata/sap/{SERVICE}. The public documentation for each API is available on SAP Business Accelerator Hub, and the activation step-by-step guide is on SAP Help Portal.

How to activate a service

In transaction /n/IWFND/MAINT_SERVICE, check whether the service is active. If it is not:

1. Click Add Service.

2. Under System Alias, enter LOCAL.

3. Search for the service name (for example, C_GLACCOUNTBALANCEQUERY_CDS).

4. Select it and confirm.

5. Test in the browser: https://{host}:{porta}/sap/opu/odata/sap/{SERVICE}/$metadata.

The link should open and display the metadata XML. Use a user with permission to access the service and, if necessary, assign the authorizations.

2. Authorize the integration user

• Create a dedicated system/communication user for the integration (not a person’s dialog user).

• Grant the SAP Gateway runtime authorizations (objects /IWFND/* and /IWBEP/*) and execution authorization for the activated services (object S_SERVICE).

• Grant the business authorizations for the data in each report (for example, the FI objects for the trial balances), following the principle of least privilege — only the reports that will be consumed.

3. Expose the endpoint securely

The platform accesses SAP through outbound HTTPS calls, read-only. If S/4HANA is not internet-accessible, the connection is made through firewall opening or a site-to-site VPN/VPC — contact Dattos support to configure it together.

Use of middleware

The integration can use middleware between the platform and SAP Gateway, as long as it operates in pass-through mode (bypass), without altering the request or the response.

The following must be preserved:

• the HTTP method;

• the URL, route, and parameters;

• the headers;

• the request and response bodies;

• the status codes;

• the data format;

• SAP Gateway error messages.

The middleware can be used for security and infrastructure functions such as authentication, authorization, access control, network policies, logs, monitoring, certificates, rate limiting, and IP restriction. Authentication must use one of the modes supported by the integration, validated by the middleware or forwarded to SAP Gateway.

If the middleware requires an authentication type that is not yet supported by the integration, contact Dattos support.

Credential Configuration

SAP S/4HANA supports two authentication methods. Choose the one enabled in your environment:

Option 1 — SAP Basic Login (username and password)

Option 2 — SAP OAuth 2.0

Available Reports

Module: Materials

Products / Materials

Returns the product and material master data registered in SAP.

Filter parameters:

Returned fields:

Material Documents

Returns material movement documents (receipts, issues, physical transfers).

Filter parameters:

Returned fields:

Material Classification

Returns material classification by class type.

Filter parameters:

Returned fields:

Module: Business Partners

Business Partners

Returns customers, vendors, and partners registered in SAP.

Filter parameters:

Returned fields:

Module: Purchasing

Purchase Orders

Returns purchase orders issued in SAP.

Filter parameters:

Returned fields:

Module: Sales

Sales Orders

Returns the sales orders registered in SAP.

Filter parameters:

Returned fields:

Module: Accounts Payable

Vendor Invoices

Returns vendor invoices (incoming invoices) posted in SAP.

Filter parameters:

Returned fields:

Module: Accounting

Accounting Balance (Trial Balance)

Returns the accounting trial balance by account and fiscal period.

Filter parameters:

Returned fields:

General Ledger Trial Balance (Trial Balance)

Returns the general ledger trial balance with balances by account and period.

Filter parameters:

Returned fields:

Module: Controlling

Cost Centers

Returns the master data for cost centers configured in SAP.

Filter parameters:

Returned fields:

Profit Centers

Returns the master data for profit centers.

Filter parameters:

Returned fields:

Fixed Parameters (managed automatically)

These parameters are filled in automatically by the system and do not appear to the user:

Related articles

• ERP Step

• Introduction to integrations

• Custom integrations via REST API and SQL connectors