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

SAP OData Connection

Once the Synthesized transport is installed on your SAP system, add the connection in Governor as an SAP OData data source. For what the application-layer route is, and when to use it, see SAP Application Layer Integration.

Before you start

  • The Synthesized transport installed, and its OData service activated on the SAP Gateway by your SAP Basis team. Note the service name. Contact Synthesized for the transport.

  • A dedicated SAP service user, authorized for the service and for the tables in scope: read for a source, and write for a target.

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

Add the data source

  1. Click Data sources in the left sidebar, then Connect new data source.

  2. Choose SAP OData.

  3. Enter the connection details:

    Field Value

    Name

    A label for the connection.

    API endpoint URL

    The root of the service: https://<host>:<port>/sap/opu/odata/sap/<service name>.

    Username

    The SAP service user.

    Password

    That user’s password.

  4. Click Test connection, then save.

To keep the password out of Governor, store it in a secret manager. See Secret Managers.

Permissions

SAP’s own authorizations decide what the platform can read and write, not SQL grants. Ask your SAP Basis team for a role that covers the service and the tables in scope, and use a different service user in each environment.

TLS

The workers check the Gateway’s TLS certificate. If it’s self-signed, or signed by your organization’s own certificate authority, add the certificate or the CA to the truststore the workers use. See SSL certificate issues.

Troubleshooting

Test connection fails, or returns a sign-in page

Check the URL and the service name, that the service is activated on the Gateway, and that the user is authorized to call it.

Authentication fails (401)

Check the user name and password, and that the user isn’t locked.

Access is refused (403)

The user isn’t authorized for the service, or for a table in scope. Ask your SAP Basis team to check the user’s role.

An SSL or TLS handshake error

The workers don’t trust the Gateway’s certificate. See TLS.

Runs are slow, or time out

Contact Synthesized support at support@synthesized.io, with the run log.