Skip to main content
Use the @bijection/connectors/sap-slt entrypoint to declare SAP Landscape Transformation Replication Server (SLT) resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Replicated table

odp: ODP delta queue over OData: initial load, trigger deltas and deletions

The following example matches configuration standard.

Configuration: standard

Case: sap-slt/table/odp/standard. Connection and resource configuration are declared by this exact case. Credential kind: odata. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

sapSlt.table.odp({ schema, key, fields?, filter? }) reads one table that an SLT configuration replicates into the Operational Data Provisioning (ODP) framework. It is the native odata transport over the OData v2 service SAP Gateway generates for the configuration’s ODP context, so an SLT table gets an initial load, then trigger-based deltas with deletions, and the ODP subscription is the retained position.

Setup on the SAP side

  1. In LTRC, create a configuration with the SLT system as target and the scenario Operational Data Provisioning (ODP), and a six-character queue alias. Activate the BAdI implementation ODQ_ENH_SLT_REPLICATION (Expert Functions > ODP/ODQ Specific Functions). The ODP context is SLT~<queue alias>; each table is an ODP named after the table.
  2. In SEGW on the system that hosts the queue, create a project, then Data Model > Redefine > ODP Extraction, choose the context SLT~<alias> and the tables, generate, and register the service in /IWFND/MAINT_SERVICE. Each table is an entity set such as FactsOfVBAK, with the properties ODQ_CHANGEMODE and ODQ_ENTITYCNTR, and the function import TerminateDeltasForFactsOfVBAK.
  3. Create a technical user for Bijection alone. SAP keeps one delta subscription per service and per user: another consumer, or a manual request without a delta token, under the same user re-initialises the subscription this source follows.

Binding

Bind an odata connection: serviceUrl (the generated service root, such as https://slt.example/sap/opu/odata/sap/ZSLT_SALES_SRV), version: "v2", sapClient where the system needs it, and the odata credential (basic, OAuth client credentials or an X.509 client certificate). The resource’s entitySet is the generated FactsOf<TABLE> name. key must equal the entity type’s key in $metadata; filter narrows the published rows by equality on filterable properties, and a row that leaves it is withdrawn.

What is read

The first read asks for the entity set with Prefer: odata.track-changes, which is the ODP delta initialization: SLT’s initial load in pages, ending in a delta link. Each later read follows that link. ODQ_CHANGEMODE D is a deletion and becomes an explicit absence; C/U after images publish; a U before image (counter -1) is skipped; any other mode is refused. Packed numbers (Edm.Decimal) stay exact text.

Recovery

  • A delta link the service answers 410, or 400/404 on this ODP service (an ended or re-initialised subscription; SAP documents no status for it), is a typed gap: acquisition stops until an operator rebaselines.
  • A rebaseline calls TerminateDeltasFor…, reads a new delta initialization, and withdraws the previously published keys that initialization did not list: ODP serves it from one queue request, the table’s full image, and ODP services are not read by key.
  • ODQMON reorganisation removes queue requests after their retention. Whether a subscription paused beyond it still answers its delta link is not established; if it is refused, the source records the same gap.
No SAP system has been reached: the transport’s ODP behaviour is proven against controlled histories and a loopback stand-in modelled on SAP’s documented ODP OData responses only.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.