The SAP SLT connector allows you to connect Foundry to SAP systems via an SAP Landscape Transformation (SLT) Replication Server. Data is replicated from source SAP ERP systems to corresponding Operational Delta Queues (ODQ) in the SLT system based on database triggers. The SAP SLT connector enables Foundry to interact with:
Using the SAP SLT source requires the installation of the Palantir Foundry Connector 2.0 for SAP Applications add-on on the SAP SLT Replication Server. Learn more about connecting via SLT.
| Capability | Status |
|---|---|
| Exploration | 🟢 Generally available |
| Batch syncs | 🟢 Generally available |
| Incremental | 🟢 Generally available |
| Streaming syncs | 🟢 Generally available |
| Use in code repositories | 🟢 Generally available |
Learn more about setting up a connector in Foundry.
The SAP SLT connector requires a Remote context value to uniquely identify the RFC connection between the SLT Replication Server and the source ERP system. Use the format SLT~<Alias_Name>, where <Alias_Name> is the alias name configured in the SAP SLT LTRC transaction. Learn more about configuring this in the SLT configuration guide and about SLT connections.
The SAP SLT connector supports the following authentication methods:
| Authentication method | Description |
|---|---|
| Basic Auth | Provide the username and password of the technical user created when installing the Connector. |
| Authentication token | Provide a token to authenticate. |
| Custom authentication header | Provide a custom authentication header. |
| No authentication | An option used if authentication is set up on the agent machine via certificates. |
You must properly configure egress policies (if using a Foundry worker) or your agent networking (if using an agent worker) to make sure your SAP SLT system can communicate with Foundry.
Agent worker is in the legacy phase of development. We recommend using Foundry worker connections for new sources. See Foundry worker vs agent worker.
Many SAP systems use custom-signed certificates which can cause SSL handshake exceptions when configuring the connection for the first time. Make sure you have the correct custom certificates from your system and add them to the source (if using a Foundry worker) or to the agent directly (if using an agent worker).
To reach this SAP system through SAP Data Accelerator (SAP's managed connectivity service for systems exposed through an SAP Cloud Connector), set the source's host and port to your Cloud Connector virtual host and port. Then, assign the client certificate provided by Palantir, allow egress to the SAP Data Accelerator control plane and data plane, and add the SAP Data Accelerator property with your control plane URL. This path requires using a Foundry worker.
Use the exploration view to create syncs for SAP SLT tables. From the source overview page, select + New next to batch sync, then choose your desired object type from the dropdown:
For batch syncs, the following settings appear under Advanced settings. Some are also configurable at the source level.
| Setting | Description |
|---|---|
| Max file size | Maximum size of each output Parquet file. Defaults to 50,000 rows per file. |
| Clean field names for Avro | Sanitizes field names so they conform to the Avro ↗ schema rules used by Foundry streams. Required if the dataset will be used in a streaming pipeline. |
| Ignore unexpected values | When enabled, date or number values that fail to parse are written as null and a summary of parse exceptions is logged at the end of the sync. |
| Convert dates to strings | Ingests date fields as strings. Useful when SAP date fields contain unparseable values that hold a special meaning and need to be handled downstream. |
| Page size | Rows returned per page when retrieving data from SAP. Defaults to 50,000. Minimum 5,000. |
| Parallel paging threads | Number of SAP work processes used to generate page data. Applies to legacy ODP syncs only; not applied to OData syncs. |
| Plugin worker threads | Number of Data Connection agent threads used to retrieve page data. |
| Remote context | RFC connection identifier to the source system. If set, the initial load bypasses the SLT Replication Server queue and consumes data over RFC instead. Not applicable to OData syncs. |
| Serialization engine | Serialization method used for data transfer. |
| Retries and timeouts | Retry count, retry delay, and request timeouts. |
| Resource checks | Memory and CPU checks during extraction. Disabling can put excess load on the SAP system. |
| Debug settings | Trace logging and debug logging. Debug logging starts a background process in SAP — use with caution. |
For incremental batch syncs, the Max rows per sync setting bounds the approximate number of rows returned per run. Use it to split the initial sync of a large table into a series of smaller, more resilient runs if intermittent issues (such as network failures) disrupt long-running syncs.
SAP SLT replication syncs extract data through one of two APIs. Select the API in the API version card of the batch or streaming sync editor.
| API | Description |
|---|---|
| OData | Uses SAP's ODP-based data extraction via OData ↗. Allows one active subscription per table for the SAP user that the source authenticates as. Does not include remote context or parallel paging. New syncs default to OData when the add-on supports it. |
| ODP | Uses SAP's ODP Data Replication API over RFC (ODP-RFC). Allows multiple subscriptions per table, enabling different syncs to ingest the same table independently. Includes remote context and parallel paging. SAP is restricting access to this API. |
SAP is restricting access to the ODP-RFC API, as described in SAP Note 3255746 ↗. SLT syncs that use the ODP API will fail once SAP's security patch, which rejects unauthorized ODP-RFC calls, is applied to your SAP system. Migrate these syncs to OData.
The OData API requires SAP add-on version 2.34 (SP34) or later with the PALODATA component installed on the SLT system, and SAP_BASIS 7.50 SP09 or later. We recommend SP39 Fix Pack 4 or later. Learn more about the prerequisites and configuration.
Follow Use OData for SAP SLT syncs to:

When using the OData API, the first sync configured for a table claims the active subscription for the source's SAP user. Reset queue registration resets the current sync's own subscription. It cannot take over a subscription held by another sync; in that case, the run fails with You cannot reset this sync, an active sync is already configured for this table. To resolve a conflict with another sync, coordinate termination of that subscription with your SAP Basis team or use a different SAP user. Learn more about subscription conflicts.
For batch syncs, use Reset incremental state rather than this setting to reload a table. For streaming syncs, use Force snapshot.
Enabling reset queue registration triggers a full reload every time a batch sync runs. On a streaming sync, it is sent with every polling request and can re-initialize the stream repeatedly while it runs. Keep this setting off.
The SAP SLT connector supports streaming syncs for real-time data replication. To create a streaming sync, select + New next to Streaming sync from the source overview page. Streaming syncs use the same API version setting as batch syncs. Keep Reset queue registration off for streaming syncs.
The Force snapshot toggle controls whether the stream starts by reading the full table before polling for incremental updates. The setting applies each time the stream starts. Enable this setting when:
After the full table has been streamed to Foundry, disable this setting and save so that subsequent streaming only polls for updates.