Connection configuration - Precisely Data Integrity Suite

Data Integrity Suite
Product
Spatial_Analytics
dis_mcp
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
platform_spatial_analytics
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Precisely MCP
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

Review the fields and driver bundle requirements for SAP Business Suite 4 HANA (S/4HANA), ECC, and R/3 ERP connections.

Field Description
Connection Name Specifies the name of the data connection. This is a mandatory field used to identify and reference the connection within the system. Example: SAP_Prod
Description Allows you to describe the purpose and context of this data connection. This field helps document the connection's intended use and environment.
Agent to access data Specifies the agent that will be used to establish connectivity to the SAP (S/4HANA), ECC, R/3 ERP system. This is a mandatory field for on-premises deployments. Select from the dropdown list of available agents registered in your environment. If only one agent is available, it is selected by default.
Bundle Name Select the uploaded SAP S/4HANA driver bundle to use for Advanced Connectivity.
Application Server Specifies the hostname or IP address of the SAP (S/4HANA), ECC, R/3 ERP application server. This is the server where the SAP system is running and is a mandatory field.
Port number Specifies the port number used to connect to the SAP application server. Example: 8000
System Number Specifies the system number of the SAP (S/4HANA), ECC, R/3 ERP instance. This is a two-digit number that uniquely identifies the SAP system instance on the application server. This is a mandatory field.
Client Specifies the SAP client number to connect to. A client is a logical unit within an SAP system that contains independent data and configuration. This is a mandatory field.
Language The asset description appears based on the specified the language.
Processing environment for cataloging Specifies the metadata discovery scope for SAP (S/4HANA), ECC, and R/3 ERP. Choose one of the following options:
  • Application Component: Organizes metadata by SAP application component hierarchies.
  • Package: Organizes metadata by SAP development packages.
  • ODATA Service: Available for SAP (S/4HANA) through base connectivity. Use this option to catalog a specific ODATA service.
Advanced Options

Configure the connector log level and specify additional connection parameters. For large SAP (S/4HANA), ECC, R/3 ERP metadata harvesting jobs, increase the catalog job memory by setting catalogJobMemoryLimit in the Debug Parameter field. Specify a maximum value of 4Gi, using Gi for GB and Mi for MB.

You can also use the following flags to control the scope of metadata import and improve performance:

  • idocs.skip = true. Skips importing IDocs
  • functiongroups.skip = true. Skips importing function groups and function modules
  • programs.skip = true. Skips importing programs
  • import.table.functions = true. Imports table functions

Set skip flags to true when you want to reduce processing time by excluding objects that are not required for your cataloging use case.

SAP S/4HANA driver bundle for metadata extraction

Before creating an SAP (S/4HANA), ECC, or R/3 ERP connection that uses the Advanced Connectivity Bundle, download the SAP Java Connector (JCo) library, prepare the s4hana driver bundle, and upload the bundle to the agent.

The bundle ZIP file must include the following structure:

s4hana.zip/
|-- lib/
|   |-- sapjco3.jar
|   `-- <native-library>
`-- driver.properties

The driver.properties file includes the SAP S/4HANA driver name and support settings:

driver.display.name=s4hana
driver.byod.bundleName=s4hana
driver.class.name=com.sap.db.jdbc.Driver
driver.byod.support=true

On the agent machine, upload the bundle by running ./discli drivers upload --name "s4hana" --driverPath /temp/s4hana.zip. For the general driver upload workflow, see Upload custom JDBC drivers to agent.