> 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.md).

# SAP Table

The SAP Table connector enables OvalEdge to connect to SAP systems and retrieve metadata from supported SAP database objects. It supports crawling, profiling, query execution, and table search through Remote Function Calls (RFC).

The connector supports connectivity to the following SAP systems:

* SAP ERP (Enterprise Resource Planning)
* SAP CRM (Customer Relationship Management)
* SAP SRM (Supplier Relationship Management)
* SAP SCM (Supply Chain Management)
* SAP PLM (Product Lifecycle Management)
* SAP Industry Solutions
* SAP HCM
* SAP S/4 HANA
* Other SAP Systems

The connector supports:

* Crawling Transparent Tables, Cluster Tables, Pooled Tables, and Views
* Profiling supported SAP data objects
* Connecting through SAP Application Server or SAP Message Server
* Authentication using Basic Authentication or Secure Network Communication (SNC)
* Retrieving data using standard RFCs or custom RFC implementations

## **Connector Capabilities**

The following is the list of objects supported by the SAP Table connector.

<table><thead><tr><th width="220.25">Functionality</th><th>Descriptions</th></tr></thead><tbody><tr><td>Supported Data Objects</td><td><p>Crawl and Profile fetch data from the following data assets:</p><ul><li>Transparent Table
</li><li>Cluster Table
</li><li>Pooled Table
</li><li>Views</li></ul></td></tr><tr><td>Crawling</td><td>Tables, Views &#x26; Columns</td></tr><tr><td>Profiling</td><td><ul><li><strong>Table Profiling</strong>: Row count, Column count, and View sample data</li><li><strong>View Profiling</strong>: Row count,   Columns count, View sample data</li><li><strong>Column Profiling:</strong> Min, Max, Null count, distinct, top 50 values</li></ul></td></tr><tr><td>Full Profiling</td><td>Performs profiling on supported SAP tables and views.</td></tr><tr><td>Sample Profiling</td><td>Supported</td></tr><tr><td>Incremental Crawling</td><td>Supported</td></tr><tr><td>Query Execution</td><td>Select</td></tr><tr><td>Search Tables</td><td>Searching a table</td></tr></tbody></table>

## **Prerequisites**

This section lists the prerequisites to establish a connection between the connector and the OvalEdge application.

1. Driver Details
2. Service Account Permission

### **Driver Details**

SAP Java Connector is an application library provided by SAP for integrating Java-developed applications. OvalEdge uses this library for its integration with the SAP Business Suite systems.

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

<table><thead><tr><th width="148.16668701171875">Driver</th><th width="99.66668701171875">Version</th><th>Details</th></tr></thead><tbody><tr><td>sapjco3.jar</td><td>3.0</td><td>This Jar is available at the SAP Service marketplace.</td></tr><tr><td>sapjco3.dll</td><td>-</td><td>The specified dll should be placed in the /home/ovaledge/jarpath</td></tr></tbody></table>

In case it needs to be changed, add SAP Table drivers to the OvalEdge JAR path (/home/ovaledge/jarpath) to communicate with the SAP Table database.

### **Integration Approach – Via RFC (BAPI)**

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

#### **BAPIs used in the OvalEdge Application**

<table><thead><tr><th width="95.6666259765625">Sl. No.</th><th width="210.33331298828125">BAPI Name</th><th width="181.33331298828125">Connection Type</th><th width="252.6666259765625">Usage Description</th></tr></thead><tbody><tr><td>1</td><td>RFC_READ_TABAL</td><td>Basic</td><td>Reading and Querying a Table (Basic)</td></tr><tr><td>2</td><td>EM_GET_NUMBER_OF_ENTRIES</td><td>Basic/Extended</td><td>Searching a Table</td></tr><tr><td>3</td><td>Z_RFC_READ_TABLE</td><td>Extended</td><td>Reading and Querying a Table</td></tr><tr><td>4</td><td>Z_RFC_PROFILE_TABLE</td><td>Extended</td><td>Profiling a Table</td></tr></tbody></table>

### **Service Account Permissions**

The minimum privileges required for a service account to crawl and profile the data are as follows:

<table><thead><tr><th width="192">Operations</th><th width="204">Objects</th><th width="206.3333740234375">System Tables</th><th width="180.3333740234375">Access Permissions</th></tr></thead><tbody><tr><td>Connection Validation</td><td>SAP System</td><td>RFC Destination</td><td>Read</td></tr><tr><td>Crawling</td><td>Tables, Views, and Columns</td><td>RFC Tables</td><td>Read</td></tr><tr><td>Crawling &#x26; Profiling</td><td>Transparent Tables, Cluster Tables, Pooled Tables, and Views</td><td>RFC Tables</td><td>Read</td></tr><tr><td>Search Tables</td><td>Tables</td><td>RFC Tables</td><td>Read</td></tr></tbody></table>

The SAP User who is being used in the OvalEdge application while making a new connection to the  SAP system must have the following permissions:

* Authorization for using Remote Function Call (RFC) destinations.
* Permissions to execute the activity of the S\_SDAUTH authorization object.

## **Set up a connection**

To establish the SAP Table Connection, fill out the required fields with the relevant information in the Manage Connector pop-up window.

{% hint style="warning" %}
Users are required to have the Connector Creator role in order to configure a new connection.
{% endhint %}

1. Log into the **OvalEdge** application.
2. In the left menu, click on the **Administration** module and then on the Connectors sub-module. The **Connectors Information** page will then be displayed.
3. Click on **+ New Connector**. The **Add Connector** pop-up window is displayed.
4. Select the connection type **SAP Table**. The Add Connector with SAP Table details is displayed.&#x20;

<table><thead><tr><th width="219.58331298828125">Fields</th><th>Details</th></tr></thead><tbody><tr><td>Connector Type</td><td>The selected connection type, ‘SAP Table,’ is displayed by default. The drop-down list allows the user to change the connector type if necessary.</td></tr><tr><td>Credentials Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on your selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp Vault</li><li>Azure Key Vault</li></ul><p>For more details, click<a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration"> here</a>.</p></td></tr><tr><td>Connector Name*</td><td><p>Select the connection name for the SAP Table database. Users can specify a reference name to identify the SAP Table database connection in OvalEdge. </p><p><strong>Example:</strong> OvalEdge_SAP Table_Connection</p></td></tr><tr><td>Connector Environment</td><td><p>Select the environment (Example: PROD, STG) configured for the connector.</p><p>For more details, click<a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment"> here</a>.</p></td></tr><tr><td>Type*</td><td><p>Select from the drop-down list.</p><ul><li>Basic</li><li>Extended</li></ul><p><strong>Basic</strong>: Used for Table Data (Default)</p><p><strong>Extended</strong>: Used for Large Table Data. (Enhanced feature)</p></td></tr><tr><td>SAP System*</td><td><p>Select SAP System from the drop-down list.</p><ul><li>SAP ERP (Enterprise Resource Planning)</li><li>SAP CRM (Customer Relationship Management)</li><li>SAP SRM (Supplier Relationship Management)</li><li>SAP SCM (Supply Chain Management)</li><li>SAP PLM (Product Lifecycle Management)</li><li>SAP Industry Solutions</li><li>SAP HCM</li><li>SAP S/4 HANA</li><li>Other SAP Systems</li></ul></td></tr><tr><td>Connection Method*</td><td><p>Select Connection Method from the drop-down list</p><ul><li>Connection via Application Server</li><li>Connection via Message Server</li></ul></td></tr><tr><td><strong>Connection Method as Connection via Application Server</strong></td><td></td></tr><tr><td>RFC Destination*</td><td><p>An RFC (Remote Function Call) destination is a configuration that sets the parameters for establishing a communication channel between an SAP system and an external system.</p><p><strong>Example</strong>: XYZ_S</p></td></tr><tr><td>Application Server HOST/IP*</td><td><p>Enter the hostname or IP address of the SAP Application Server to establish the connection.</p><p><strong>Example: 12.34.56.789</strong></p></td></tr><tr><td>System ID/SID*</td><td><p>Enter the SAP System ID (SID), a unique three-character identifier for the SAP system.</p><p><strong>Example: EC1</strong></p></td></tr><tr><td>Instance Number*</td><td><p>A two-digit identifier is assigned to an SAP instance (an application server or a central instance) within a specific SAP system.</p><p><strong>Example: 00</strong></p></td></tr><tr><td>Client Number*</td><td><p>Refers to a three-digit identifier that specifies a particular client within an SAP system.</p><p><strong>Example: 500</strong></p></td></tr><tr><td>Username*</td><td>Enter the SAP user name used to authenticate the connection.</td></tr><tr><td>Password*</td><td>Enter the password associated with the specified SAP user account.</td></tr><tr><td>Language</td><td><p>Enter the language in which you want to get data, i.e., EN for English.</p><p>Example: EN</p></td></tr><tr><td>SNC Mode</td><td>Refers to the configuration setting that determines how Secure Network Communications is enabled and configured for communication between SAP systems or between SAP systems and external components.</td></tr><tr><td><strong>Connection Method as Connection via Message Server</strong></td><td></td></tr><tr><td>RFC Destination*</td><td><p>An RFC (Remote Function Call) destination is a configuration that sets the parameters for establishing a communication channel between an SAP system and an external system.</p><p><strong>Example: RFC_OVALEDGE_ERP</strong></p></td></tr><tr><td>Message Server HOST/IP*</td><td>Refers to the hostname or IP address of the SAP message server. </td></tr><tr><td>Message Server Port*</td><td>Refers to the port number on which the SAP message server listens for incoming connections.</td></tr><tr><td>System ID/SID*</td><td>A unique identifier for an SAP system instance.</td></tr><tr><td>Instance Number*</td><td>Refers to a numeric identifier that uniquely identifies an SAP instance within a specific SAP system.</td></tr><tr><td>Group/Server Name*</td><td>Refers to the logical or physical name assigned to a group of application servers or a specific application server within an SAP system landscape.</td></tr><tr><td>Client Number*</td><td>Refers to a three-digit identifier that uniquely identifies a client within an SAP system. </td></tr><tr><td>Username*</td><td>Enter the SAP user name used to authenticate the connection.</td></tr><tr><td>Password*</td><td>Enter the password associated with the specified SAP user account.</td></tr><tr><td>Language</td><td><p>Enter the language in which you want to get data, i.e., EN for English.</p><p>Example: EN</p></td></tr><tr><td>SNC Mode</td><td><p>Refers to the configuration setting that determines how Secure Network Communications is enabled and configured for communication between SAP systems or between SAP systems and external components.</p><p>If yes: user need to provide SNC certificate which is configured with the client’s SAP environment,</p><p>If No: Will bypass the validation</p></td></tr></tbody></table>

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="220.33331298828125"></th><th></th></tr></thead><tbody><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are displayed for selection.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="220.33331298828125"></th><th></th></tr></thead><tbody><tr><td>Admin Roles*</td><td>Select one or more users from the dropdown list for Integration Admin and Security &#x26; Governance Admin. All users configured in OvalEdge Security are available for selection.</td></tr></tbody></table>

**No of Archive Objects**

<table data-header-hidden><thead><tr><th width="219"></th><th></th></tr></thead><tbody><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr></tbody></table>

**Bridge**

<table data-header-hidden><thead><tr><th width="219"></th><th></th></tr></thead><tbody><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.</p></td></tr></tbody></table>

5. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
6. The saved connection will appear on the Connectors home page.

For detailed information about SAP connection methods, authorization requirements, RFC implementation, and RFC queries, refer to [**SAP Table Connector – Connectivity and RFC Reference**](https://docs.ovaledge.com/connectors/connector-repositories/application/sap-table/sap-table-connector-connectivity-and-rfc-reference)**.**

## **Connector Settings**

Once the connection is validated successfully, various settings are provided to retrieve and display the information from the data source.  The connection settings include Crawler, Profiler, Query Policies, Access Instruction, Business Glossary Settings, and Others.

<table><thead><tr><th width="220.25">Connection Settings</th><th>Description</th></tr></thead><tbody><tr><td>Crawler</td><td>Crawler settings are configured to connect to a data source and collect and catalog all the data elements in the form of metadata.</td></tr><tr><td>Profiler</td><td>Profiling is the process of gathering statistics and informative summaries about the connected data source(s). Statistics can help assess the data source's quality before using it in an analysis. Profiling is always optional; crawling can be run without profiling.</td></tr><tr><td>Query Policies</td><td><p>The Query Policies in the Crawler setting provide the right access to the Query sheet functions (Join, Union, SUM, or aggregate functions). You can specify the desired roles and permission to deny the usage of the query sheet function. A role that has been denied policy permission will not have access to those functions in the Query Sheet.</p><p><strong>Example:</strong> If the user selects the Role as “OE_HRADMIN,” Query Type as “JOIN,” and the Access Type as “DENY,” then the users associated with the OE_HRADMIN privileges are restricted from using the JOIN function in the Query Sheet page.</p></td></tr><tr><td>Access Instruction </td><td>It allows the data owner to instruct others on using the objects in the application. </td></tr><tr><td>Business Glossary Settings</td><td>The Business Glossary setting provides flexibility and control over how they view and manage term association within the context of a business glossary at the connector level. </td></tr><tr><td>Others</td><td><p>The Enable/Disable Metadata Change Notifications option sets the change notification about metadata changes of the data objects.</p><ul><li>Users can use the toggle button to set the Default Governance Roles (Steward, Owner Custodian, etc.) </li><li>Using the <strong>Roles</strong> and <strong>Teams</strong>, users can select the role and team to receive the notification of metadata changes.</li></ul></td></tr></tbody></table>

## **Crawling a Table**

1. Navigate to the **Connectors** page and click **Crawl/Profile.**
2. A search field will be displayed, where you can search for specific tables by entering 3 characters followed by %, and based on this, all the matched tables will be displayed.
3. Select **Crawl**, **Profile**, **Unprofiled**, or **Scheduled** based on the requirement.
4. Click on **Run** to gather all metadata from the connected source into the **Data Catalog**.

***

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.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.