Connect SAP OData to Apragya: Read and Write S/4HANA Objects Through Your Gateway
For SAP teams and IT heads running S/4HANA: let Apragya workflows read and update SAP business objects through the OData services you already expose.
To connect SAP OData to Apragya, you enter your SAP Gateway base URL and the OData service path, choose version 2 or 4, pick Basic or OAuth authentication, and test. The test reads the service's metadata, so a success means the service is really reachable.
Many Indian manufacturers run SAP for finance and production while sales teams, vendors or plants use lighter tools. Moving data between them is usually a file exchange.
This page covers the connection settings, how to reach an on-premise system without opening your firewall, and an illustrative example from a manufacturing group.
What file exchanges with SAP cost
Delayed updates
Material and vendor changes wait for the next file run.
Format errors
A column moves and the upload fails quietly.
Wide access
Shared SAP users with more rights than needed.
IT bottleneck
Every new field is a ticket for the SAP team.
Double entry
Staff key the same record into both systems.
Weak trail
Nobody can say which file changed what.
An example: a Chennai auto parts group
Take an illustrative group with S/4HANA at head office and plants that raise requests on the shop floor. Material master changes took two days to reach the plants.
One OData connection, several flows
SAP OData service
Reached through the Gateway.
Material lookup
Plant requests read current materials.
Vendor details
Vendor data read for onboarding checks.
Metadata picker
Entity sets and fields listed for mapping.
Status write-back
Approved changes updated in SAP.
Tenant Runner
Outbound link from inside the network.
Plants now see the current material data when they raise a request, and approved updates are written back through the same service. The SAP team set up one technical user instead of answering file tickets.
How the SAP Gateway connector works
Step 1 of 5
Base URL and service
Gateway base URL, the OData service path and version 2 or 4.
- Base URL and service: Gateway base URL, the OData service path and version 2 or 4.
- Authentication: Basic auth, or OAuth client credentials with a token URL.
- Test on metadata: The test fetches the service metadata.
- Read: Read collections with filters, paging, sorting and selected fields, or one entity by key.
- Write: Create, update and delete, with SAP's CSRF token handled for you.
Choosing an SAP S/4HANA integration in India
Middleware suites are powerful and need their own team. For a set of well-defined flows, a connector inside the workflow is often enough, provided it handles SAP's quirks properly.
File interfaces, against Apragya
| Feature | File interface | Apragya OData connector |
|---|---|---|
| Timing | Batch runs | When the workflow runs |
| Write safety | Upload and hope | CSRF-protected calls, errors returned |
| Field discovery | Spec documents | Read from service metadata |
| On-premise reach | Shared folder | Tenant Runner, outbound only |
| Credentials | In scripts | Encrypted at rest |
Checked against public information on 16 September 2026.
What sets it apart
V2 and V4
The same connection handles both OData versions.
Function imports
Service-specific function imports can be called too.
Behind the firewall
The Tenant Runner avoids inbound firewall rules.
Least privilege
Use a technical user limited to the services you expose.
Agents with SAP data
An agent can read SAP data before it drafts its output.
Audit log
Connection changes are recorded.
For older systems with no Gateway, see connecting SAP RFC. For a wider view, see SAP Business One alternatives.
Getting started
- Ask your Basis team which OData services are active and which technical user to use.
- If the Gateway is internal, install the Tenant Runner inside the network.
- Add the connection and run the metadata test.
- Build one read-only workflow first.
- Add writes once the SAP team has reviewed the calls.
A service that is not activated in the Gateway fails the metadata test; that is the first thing to check.
What it costs to start
Connecting SAP OData, answered
Does it work with S/4HANA Cloud and on-premise?
Our SAP system is not on the internet.
Can it call custom Z services?
We run ECC without Gateway.
What does it cost to start?
Test your first SAP service
Add the Gateway URL, run the metadata test, and read one collection.