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, which is the unique identifier of the RFC connection between the SLT Replication Server and the source ERP system. 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.
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).
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:
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.
The Force snapshot toggle controls whether the stream starts by reading the full table before polling for incremental updates. 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.
With add-on version 2.34 (SP34) or higher, SAP SLT syncs use the OData API by default. This is based on ODP-based data extraction via OData ↗, as recommended by SAP ↗. The legacy ODP API is no longer permitted by SAP.
Using the OData API requires:
PALODATA add-on component to be installed on the SLT system.| API | Description |
|---|---|
| OData | Only one active subscription per table is allowed. If a sync already exists for a table, any new sync targeting the same table will fail unless the existing subscription is released first. Does not include remote context or parallel paging. Selected by default for new syncs. |
| ODP (legacy) | Allows multiple subscriptions per table, enabling different syncs to ingest the same table independently. Includes remote context and parallel paging. No longer permitted by SAP. |
When using the OData API, the first sync configured for a table claims the active subscription. If you need to replace that sync with a different configuration, enable Reset queue registration to release the existing subscription and assign it to the current sync.
Enabling reset queue registration triggers a full reload of the dataset every time the sync runs. Disable this setting after the subscription has been reassigned to avoid repeated full reloads.