> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/connectors/connector-repositories/application/sap-table/sap-table-connector-connectivity-and-rfc-reference.md).

# SAP Table Connector – Connectivity and RFC Reference

This article describes the SAP Table connector connectivity options, required connection properties, SAP authorization requirements, and RFC-based data retrieval used to establish communication between the OvalEdge SAP Table connector and SAP systems.

It also provides technical reference information for SAP Application Server and SAP Message Server connections, supported RFC implementations, and commonly used RFC query operators.

## Supported Connection Methods

The SAP Table connector supports the following connection methods:

* **Connection through SAP Application Server**
* **Connection through SAP Message Server**

<figure><img src="/files/xMjKWllORxZ9fh2Cxtq6" alt=""><figcaption></figcaption></figure>

### Connection through SAP Application Server

Use this connection method when connecting directly to a specific SAP Application Server instance.

<table><thead><tr><th width="168.33331298828125">Property</th><th width="312.3333740234375">Description</th><th>Required</th></tr></thead><tbody><tr><td>Connection Type</td><td>Must be set to <strong>SAP Table</strong>.</td><td>Yes</td></tr><tr><td>Application Server</td><td>Host name or IP address of the SAP Application Server.</td><td>Yes</td></tr><tr><td>System Number</td><td>Two-digit SAP system instance number.</td><td>Yes</td></tr><tr><td>System ID</td><td>Unique identifier of the SAP system.</td><td>Yes</td></tr><tr><td>Client ID</td><td>Three-digit SAP client identifier.</td><td>Yes</td></tr><tr><td>Username</td><td>SAP user account used to establish the connection.</td><td>Yes</td></tr><tr><td>Password</td><td>Password associated with the SAP user account. Stored in encrypted format within OvalEdge.</td><td>Yes</td></tr><tr><td>Language</td><td>SAP logon language. Default value is <strong>EN</strong>.</td><td>No</td></tr></tbody></table>

### Connection through SAP Message Server

Use this connection method when connecting through an SAP Message Server for load-balanced access across multiple application servers.

<table><thead><tr><th width="173.66668701171875">Property</th><th width="306.6666259765625">Description</th><th>Required</th></tr></thead><tbody><tr><td>Connection Type</td><td>Must be set to <strong>SAP Table</strong>.</td><td>Yes</td></tr><tr><td>Message Server Name</td><td>Host name or IP address of the SAP Message Server.</td><td>Yes</td></tr><tr><td>Message Service Name or Port Number</td><td>Service name or port number of the SAP Message Server.</td><td>Yes</td></tr><tr><td>Logon Group</td><td>SAP Logon Group configured for load balancing.</td><td>Yes</td></tr><tr><td>System ID</td><td>Unique identifier of the SAP system.</td><td>Yes</td></tr><tr><td>Client ID</td><td>Three-digit SAP client identifier.</td><td>Yes</td></tr><tr><td>Username</td><td>SAP user account used to establish the connection.</td><td>Yes</td></tr><tr><td>Password</td><td>Password associated with the SAP user account. Stored in encrypted format within OvalEdge.</td><td>Yes</td></tr><tr><td>Language</td><td>SAP logon language. Default value is <strong>EN</strong>.</td><td>No</td></tr></tbody></table>

## SAP Authorization Requirements

The SAP user configured for the SAP Table connector must have the following authorizations:

* Authorization to use **Remote Function Call (RFC)** destinations.
* Execute permission for the **S\_SDAUTH** authorization object.

These permissions are required to validate the connection and execute RFC operations used by the connector.

## RFC-Based Data Retrieval

The SAP Table connector retrieves metadata and profiling information using standard SAP RFCs and custom RFC implementations.

### Standard RFC

The connector supports the SAP standard **RFC\_READ\_TABLE** function module for retrieving metadata and table data.

### Limitations

The standard **RFC\_READ\_TABLE** function module is subject to the **DATA\_BUFFER\_EXCEEDED** exception when the total character length of the returned data exceeds **512 characters**.

<figure><img src="/files/Yu4N5vXptBf7n5wJjlB6" alt=""><figcaption></figcaption></figure>

### Custom RFC Support

To overcome the limitations of **RFC\_READ\_TABLE**, the SAP Table connector supports the custom RFC implementation **ZOE\_RFC\_READ\_TABLE**.

The custom RFC enables retrieval of larger datasets without encountering the standard data buffer limitation.

<figure><img src="/files/XOtggaFPz8xgaHcdw3aW" alt=""><figcaption></figcaption></figure>

### Custom RFC Parameters

<table><thead><tr><th width="198.3333740234375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Query Table</td><td>Name of the SAP table or view to retrieve data from.</td></tr><tr><td>Delimiter</td><td>Character used to separate field values in the returned data.</td></tr><tr><td>No Data Indicator</td><td>When enabled, retrieves only field metadata without returning table data.</td></tr><tr><td>Row Skips</td><td>Starting row for data retrieval.</td></tr><tr><td>Row Count</td><td>Number of rows to retrieve.</td></tr><tr><td>Options</td><td>Filter conditions applied during data retrieval.</td></tr><tr><td>Fields</td><td>Metadata describing the selected fields or columns.</td></tr><tr><td>Data</td><td>Returned dataset.</td></tr></tbody></table>

{% hint style="info" %}
OvalEdge does not store source system data. Only metadata and profiling statistics are retrieved from the SAP system.
{% endhint %}

## RFC Queries

The following operators can be used to define filter conditions in RFC queries.

<table><thead><tr><th width="199">Operator</th><th>Description</th></tr></thead><tbody><tr><td>EQ</td><td>Equal to</td></tr><tr><td>NE</td><td>Not equal to</td></tr><tr><td>LT</td><td>Less than</td></tr><tr><td>LE</td><td>Less than or equal to</td></tr><tr><td>GT</td><td>Greater than</td></tr><tr><td>GE</td><td>Greater than or equal to</td></tr><tr><td>IN</td><td>Matches a list of values (for example, <code>TABCLASS IN ('TRANSP', 'INTTAB')</code>)</td></tr><tr><td>LIKE</td><td>Pattern matching (for example, <code>LIKE 'Emma%'</code>)</td></tr></tbody></table>

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/connectors/connector-repositories/application/sap-table/sap-table-connector-connectivity-and-rfc-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.