Permissions - Precisely Data Integrity Suite

Data Integrity Suite

Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
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

This import bridge uses the SAP Java Connector (JCo) API libraries to connect to the SAP system and retrieve metadata. Ensure that the SAP JCo libraries are installed and accessible on the machine where the import bridge is executed.

The SAP JCo API communicates with the SAP server over the network using the following ports:

  • Dispatcher port: 32NN — Used by SAP GUI for Windows and Java
  • Gateway port: 33NN — Used for CPIC and RFC communications
  • SNC-secured Gateway port: 48NN — Used for encrypted CPIC and RFC communications

In these port numbers, NN represents the SAP instance number (0099). Verify that firewall rules allow communication through the required ports.

Before using this import bridge, configure the SAP ECC server by deploying the required ABAP RFC function module. An SAP user account with ABAP development permissions is required to create and deploy the RFC function module on the SAP server.

The RFC function module enables the import bridge to retrieve metadata from the SAP system. Additional deployment instructions are available in the following directory: <InstallDir>/conf/MIRModelBridgeTemplate/SapR3/

The SAP user account used by the import bridge must have sufficient permissions to connect to the SAP server and execute the following RFC function modules:

  • STFC_CONNECTION — Verifies connectivity
  • RFC_SYSTEM_INFO — Retrieves system information
  • OCS_GET_INSTALLED_COMPS — Retrieves software version information
  • Z_MITI_DOWNLOAD — Performs the primary metadata extraction

The SAP JCo libraries may also invoke additional RFC function modules, such as:

  • RFC_PING
  • RFC_METADATA_GET