Integrations / SAP ECC via Gateway OData V2

SAP ECC via Gateway OData V2

Read-only access to SAP Gateway OData V2 service collections exposed by a customer SAP ECC estate. The customer must identify an activated, released service and entity set for its exact ECC/Gateway release and configure network reach and a read-authorized communication user. This does not provide RFC, BAPI, IDoc, write, or private-network bridge support.

Basic auth

Actions

What Telara does

Capability matrix

Indexes No Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

An SAP ECC release with SAP Gateway OData V2 and the Gateway service catalog available to the target communication user.

An SAP administrator who can confirm the activated service name, technical service version, entity set, HTTPS endpoint, and read authorization for this exact estate.

Vendor setup

Get the credential

Confirm the exposed service

Use the Gateway service catalog and the service metadata for the target instance to identify a released service name, version, and entity set. Availability depends on the installed ECC and Gateway release and the user's authorization.

Create a read-only communication user

Grant the communication user only the service and entity-set read permissions needed for the connection. This catalog route uses HTTPS Basic Authentication when the Gateway is configured to accept it.

Configure the connection

In Telara’s SAP ECC integration settings, enter the verified host base URL and communication username and password. Confirm the host is reachable from the integration service before testing.

In Telara

Connect in Telara

Basic auth

SAP Gateway communication user over HTTPS, when the customer has enabled Basic authentication for the exposed OData service.

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for

Base Url
Username
Password

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

The catalog supports Gateway service discovery and GET reads for a customer-selected OData V2 entity set only.

RFC, BAPI, IDoc, write operations, a customer-approved bridge, and private-network reach are not included.