This documentation is available to agents as Markdown at https://docs.synthesized.io/tdk/latest/user_guide/070_integrations/sap/odata.md. For the complete documentation index, see llms.txt.

SAP Application Layer Integration

The platform can read and write SAP data through OData services at SAP’s application layer, instead of a JDBC connection to the database. This is SAP’s recommended integration route. It needs no database access, so it works with RISE with SAP and wherever direct database access isn’t allowed.

When to use it

  • You’re on RISE with SAP, or your policies don’t allow direct database access.

  • You want SAP’s own authorizations to decide what the platform can read and write.

  • The platform can reach SAP only over HTTPS.

If you run SAP HANA yourself and your DBA approves a dedicated database user, you can also connect to the database directly. See SAP HANA Connection.

Compared with SAP HANA

Application layer (OData) SAP HANA (JDBC)

Access

An SAP user, over HTTPS

A database user, over JDBC

Works with RISE with SAP

Yes

Only where database access is allowed

Permissions

SAP authorizations, set by your SAP Basis team

SQL grants on schemas and system views

Setting it up

Your SAP Basis team installs a small transport from Synthesized through your normal change process. Contact Synthesized for the transport, and for help with the setup.

You’ll also need:

  • A dedicated SAP service user, authorized by your SAP Basis team.

  • HTTPS access from the platform’s workers to the SAP Gateway.

  • A license key: in free mode, SAP data sources are blocked.

Then add the connection in Governor. See SAP OData Connection.

Related pages