Overview
Replicate Preview supports data extraction from SAP systems using the SAP Remote Function Call (RFC) interface, enabling secure and efficient access to SAP business data without requiring direct database connectivity. Users can configure replication pipelines by defining SAP connection parameters, selecting source tables or extract structures, and configuring target destinations, allowing SAP data to be replicated with minimal setup and operational complexity.
The platform simplifies SAP integration workflows while ensuring reliable and scalable data delivery across SAP and non-SAP environments.
Note
SAP S/4HANA RFC Extraction is supported as source endpoint in Replicate Preview, limited to Snapshot (full load) replication mode, with Change Data Capture (CDC) replication not yet supported.
Supported Versions
The SAP Remote Function Call (RFC) Data Extraction is supported for S/4HANA System version 1909 and latest.
Implementation
Depending on the required functionality, you must create a user with the appropriate authorizations for Syniti Knowledge Platform (SKP) implementations when using an RFC connection. The required authorizations are summarized in this article.
For SAP implementations, you have two options to deploy the components required in your SAP S/4HANA:
Data Extractions Types
Replicate Preview provides the following three options to extract data from SAP S/4HANA:
RFC Standard Extraction
Performs data extraction from SAP tables using standard RFC-based queries. This method is recommended for general-purpose Snapshot extractions and supports broad compatibility across SAP S/4HANA environments versions. No additional requirements are needed, just select the proper Function Module: /BS4/SDRM_READ_TABLE in your connection properties.
RFC Streaming
Uses a high-performance streaming mechanism to extract large SAP datasets more efficiently by reducing RFC round trips and memory overhead. This option is optimized for high-volume table extractions and large transactional workloads. Refer to the SAP Streaming Setup section for more information.
Long Text Query
Extracts SAP Long Text objects stored in clustered text structures (such as STXH and STXL). This method is used when replicating SAP text fields including material descriptions, purchase order notes, sales text, and other SAP script or Smart Forms text content. Refer to Query Read Text for SAP ECC for more information.
Connection Considerations
If you do not have a connection configured, refer to Connecting to SAP Systems Using SAP NetWeaver for more information.
When configuring and using a connection to SAP NetWeaver for SAP S/4HANA environments, consider the following:
Configuration | Details |
|---|---|
Application Server vs Message Server Configuration | SAP connections can be configured using either a dedicated Application Server or a Message Server with Logon Groups. Ensure the correct connection type is selected based on your SAP landscape and load-balancing requirements. |
Client Configuration | Verify that the correct SAP Client number is configured. SAP systems may contain multiple clients with different datasets and security configurations. |
System Number and Instance Identification | Ensure that the SAP System Number matches the target SAP instance. Incorrect instance configuration may prevent successful connectivity. |
SAP Router Configuration | If your environment uses SAP Router for secure network routing, confirm that the SAP Router string is correctly configured and reachable from Replicate Preview. |
User Credentials and Authentication | Ensure that the SAP user credentials are valid and not locked or expired. Password policies in SAP environments may automatically expire service accounts. |
Required RFC Connectivity | Replicate Preview communicates with SAP systems using RFC. Ensure that RFC communication is enabled and that firewalls or network rules do not block SAP gateway communication. |
Gateway Host and Service Accessibility | Verify that the SAP Gateway Host and Gateway Service are accessible, especially when using RFC-based extraction scenarios. Incorrect gateway configuration may prevent RFC sessions from initializing. |
SAP SNC / Secure Network Communication | If SNC is enabled, ensure that all SNC parameters, partner names, and security libraries are correctly configured. Mismatched SNC settings are a common source of connection failures. |
Unicode and Character Encoding | Confirm that the SAP system character encoding is compatible with the target environment. Unicode SAP systems may require validation of character mappings during replication. |
Metadata Discovery Considerations | Replicate Preview may query SAP metadata structures to discover tables and fields. Restricted metadata access can prevent schema discovery or table enumeration. |
Network Latency and Timeout Settings | High network latency between Replicate Preview and the SAP environment may impact extraction performance. Review timeout settings if connections terminate during large Snapshot operations. |
Large Table Extraction Considerations | Extracting large SAP transactional tables may increase workload on the SAP application server. Consider scheduling Snapshot replications during low-usage periods to minimize operational impact. |
The SAP NetWeaver connection supports multiple connection properties such as hostname, system number, client, timeout, pooling, SNC configuration, and message server settings.
Limitations
When replicating from SAP NetWeaver sources to any target, READ tables such as SDR_READ_TABLE and SDRM_READ_TABLE may fail if the combined size of selected columns exceeds the SAP RFC buffer/row width limit, resulting in a BUFFER_LIMIT_EXCEED error. To resolve this, the SAP Server Administrator must increase or update the relevant RFC buffer configuration parameters.