For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Functionality
Descriptions

Supported Data Objects

Crawl and Profile fetch data from the following data assets:

  • Transparent Table

  • Cluster Table

  • Pooled Table

  • Views

Crawling

Tables, Views & Columns

Profiling

  • Table Profiling: Row count, Column count, and View sample data

  • View Profiling: Row count, Columns count, View sample data

  • Column Profiling: Min, Max, Null count, distinct, top 50 values

Full Profiling

Performs profiling on supported SAP tables and views.

Sample Profiling

Supported

Incremental Crawling

Supported

Query Execution

Select

Search Tables

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

Driver
Version
Details

sapjco3.jar

3.0

This Jar is available at the SAP Service marketplace.

sapjco3.dll

-

The specified dll should be placed in the /home/ovaledge/jarpath

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)

BAPIs used in the OvalEdge Application

Sl. No.
BAPI Name
Connection Type
Usage Description

1

RFC_READ_TABAL

Basic

Reading and Querying a Table (Basic)

2

EM_GET_NUMBER_OF_ENTRIES

Basic/Extended

Searching a Table

3

Z_RFC_READ_TABLE

Extended

Reading and Querying a Table

4

Z_RFC_PROFILE_TABLE

Extended

Profiling a Table

Service Account Permissions

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

Operations
Objects
System Tables
Access Permissions

Connection Validation

SAP System

RFC Destination

Read

Crawling

Tables, Views, and Columns

RFC Tables

Read

Crawling & Profiling

Transparent Tables, Cluster Tables, Pooled Tables, and Views

RFC Tables

Read

Search Tables

Tables

RFC Tables

Read

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.

  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.

Fields
Details

Connector Type

The selected connection type, ‘SAP Table,’ is displayed by default. The drop-down list allows the user to change the connector type if necessary.

Credentials Manager*

Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on your selection.

Supported Credential Managers:

  • OE Credential Manager

  • AWS Secrets Manager

  • HashiCorp Vault

  • Azure Key Vault

For more details, click here.

Connector Name*

Select the connection name for the SAP Table database. Users can specify a reference name to identify the SAP Table database connection in OvalEdge.

Example: OvalEdge_SAP Table_Connection

Connector Environment

Select the environment (Example: PROD, STG) configured for the connector.

For more details, click here.

Type*

Select from the drop-down list.

  • Basic

  • Extended

Basic: Used for Table Data (Default)

Extended: Used for Large Table Data. (Enhanced feature)

SAP System*

Select SAP System from the drop-down list.

  • 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

Connection Method*

Select Connection Method from the drop-down list

  • Connection via Application Server

  • Connection via Message Server

Connection Method as Connection via Application Server

RFC Destination*

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.

Example: XYZ_S

Application Server HOST/IP*

Enter the hostname or IP address of the SAP Application Server to establish the connection.

Example: 12.34.56.789

System ID/SID*

Enter the SAP System ID (SID), a unique three-character identifier for the SAP system.

Example: EC1

Instance Number*

A two-digit identifier is assigned to an SAP instance (an application server or a central instance) within a specific SAP system.

Example: 00

Client Number*

Refers to a three-digit identifier that specifies a particular client within an SAP system.

Example: 500

Username*

Enter the SAP user name used to authenticate the connection.

Password*

Enter the password associated with the specified SAP user account.

Language

Enter the language in which you want to get data, i.e., EN for English.

Example: EN

SNC Mode

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.

Connection Method as Connection via Message Server

RFC Destination*

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.

Example: RFC_OVALEDGE_ERP

Message Server HOST/IP*

Refers to the hostname or IP address of the SAP message server.

Message Server Port*

Refers to the port number on which the SAP message server listens for incoming connections.

System ID/SID*

A unique identifier for an SAP system instance.

Instance Number*

Refers to a numeric identifier that uniquely identifies an SAP instance within a specific SAP system.

Group/Server Name*

Refers to the logical or physical name assigned to a group of application servers or a specific application server within an SAP system landscape.

Client Number*

Refers to a three-digit identifier that uniquely identifies a client within an SAP system.

Username*

Enter the SAP user name used to authenticate the connection.

Password*

Enter the password associated with the specified SAP user account.

Language

Enter the language in which you want to get data, i.e., EN for English.

Example: EN

SNC Mode

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.

If yes: user need to provide SNC certificate which is configured with the client’s SAP environment,

If No: Will bypass the validation

Default Governance Roles

Default Governance Roles*

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.

Admin Roles

Admin Roles*

Select one or more users from the dropdown list for Integration Admin and Security & Governance Admin. All users configured in OvalEdge Security are available for selection.

No of Archive Objects

No Of Archive Objects*

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.

Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.

Bridge

Select Bridge*

If applicable, select the bridge from the drop-down list.

The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.

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

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

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.

Connection Settings
Description

Crawler

Crawler settings are configured to connect to a data source and collect and catalog all the data elements in the form of metadata.

Profiler

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.

Query Policies

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.

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

Access Instruction

It allows the data owner to instruct others on using the objects in the application.

Business Glossary Settings

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.

Others

The Enable/Disable Metadata Change Notifications option sets the change notification about metadata changes of the data objects.

  • Users can use the toggle button to set the Default Governance Roles (Steward, Owner Custodian, etc.)

  • Using the Roles and Teams, users can select the role and team to receive the notification of metadata changes.

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

Last updated

Was this helpful?