SAP Table

Connectivity Summary

An out of the box connector is available for SAP Table databases. It provides support for crawling database objects, profiling of sample data.

The connectivity to SAP Table is via API, which is included in the platform. 

The connector currently supports the following versions of SAP Table:

The drivers used by the connector are given below:

Connector Capabilities

The connector capabilities are shown below:

Crawling

Supported objects and data types for Crawling are:

Please see this article Crawling Data for more details on crawling.

Profiling

Please see Profiling Data for more details on profiling.

Querying 

By default the service account provided for the connector will be used for any query operations. If the service account has write privileges, then Insert / Update / Delete queries can be executed.

Pre-requisites

To use the connector, the following need to be available:

• Connection details as specified in the following section should be available.
• A Service account, for crawling and profiling. The minimum privileges required are:

• • Connection validate
  • Crawl Schemas
  • Crawl Tables
  • Profile Schemas, Tables
  • Query logs
  • Get Views, Procedures, Function code

Connection Details

The following connection settings should be added for connecting to a SAP Table database:

• Database Type: SAP Table
• Type:
  • Basic: Used for Table Data (Default)
  • Extended: Used for Large Table Data. (Enhanced feature)
• Connection Name: Select a Connection name for the SAP Table database. The name that you specify is a reference name to easily identify your SAP Table database connection in OvalEdge.
  Example : SAP Table Connection DB1
• SAP System:
  • SAP ECC
  • SAP CRM
  • SAP IS-Auto
  • SAP IS-Retail
  • SAP HCM
• Connection Method:
  • Connection via Application Server
  • Connection via Message Server (Load Balancing)
• RFC Destination: Enter RFC Destination Details
  Example : XYZ_S
• Application Server HOST/IP Address: Enter Application IP Address
  Example : 12.34.56.789
• Message Server Port: Enter Port for Connection via Message Server
  Example : 3601
• System ID/SID: Enter SAP System Id
  Example : EC1
• Instance Number: Enter Instance Number
  Example : 00
• Group/Server Name: Enter Group / Server Name for Connection via Message Server
  Example : SAPSERVER
• Client Number: Enter Client Number
  Example : 500
• Username: User account login credential (only for SAP Table Authentication)
• Password: Password (only for SAP Table Authentication)
• Language: Enter the language in which you want to get data i.e.., EN for English.
  Example: EN
• Destination File Path: Enter Destination File path (Optional)
• SNC Library: Enter the SNC Library file location
  Example : D:\\sapcrypto.dll

Once connectivity is established, additional configurations for Crawling and Profiling can be specified.

As there are  millions of tables in this connector, we have search feature to find the tables in SAP Table server by entering Table Name in the below Schema Name fields in crawl / profile options and hitting enter button. It will fetch all the relevant tables.

FAQs

1. What should be placed in the SNC Library field?
   We need to provide the sapcrypto.dll file location in this field.
   Ex : C:\\SAP_Cryptolib\\sapcrypto.dll.
2. What is the difference between Basic and Extended Type in Table Connector?
   In Basic, there are some limitations of space. If we want to view data which has millions of records then server will throw DATA_BUFFER_EXCEEDED exception. To overcome this space exception we have Extended type.