Theobald to Datasphere

Why use this tool

The extraction layer doesn't have to break your project.

ODP-RFC is prohibited for SAP-to-non-SAP scenarios like Theobald Xtract Universal, on-premise and private cloud alike — and since the June 2026 security patch, unauthorized calls are technically blocked. Every existing extraction, master data and transactional, delta and full, needs a new home now that the old path is closed — whether it was originally built on a CDS view or a classic SAPI DataSource. Rebuilt by hand, that's the same mapping exercise repeated for every object in the landscape.

One flow per group, not per object Extractions that share the same data type and load pattern — every delta master-data object, or every delta transactional object, say — are consolidated into a single replication flow regardless of whether their source is a CDS view or a SAPI DataSource, so you get fewer flows to manage instead of a 1-for-1 copy of every extraction you used to have.

Without the accelerator

Every Theobald extraction re-created by hand in Datasphere: re-deriving whether it's a CDS view or a SAPI DataSource, re-checking whether it was delta or full, re-building the replication flow one at a time.

With the accelerator

Xtract Universal and your S/4 system are read directly, each extraction is resolved as a CDS view or a SAPI DataSource and grouped by type and load mode automatically, and everything in the same group — master or transactional — lands in a single replication flow, not one per object.

Built on what you already have: your existing Theobald extraction definitions and your S/4 system's CDS views and SAPI DataSources are the source of truth, so nothing is re-specified from scratch.

What is automated

The mapping work, carried for you.

Each Theobald extraction is read, classified, and matched to its Datasphere equivalent. Anything that needs a human decision is flagged, never guessed.

Master vs. transactional classification

Delta vs. full load detection

CDS view or SAPI DataSource resolution, via S/4

Replication flow generation

Matching master or transactional extractions merged into one flow

Direct load into your own data lake

Naming carried over from your extractions

Objects without a clean CDS or SAPI match, flagged

Deployment to the right space

migrate · MATERIAL_MASTER.xml

// Theobald extraction in <xu:extraction name="MATERIAL_MASTER" mode="DELTA"> <source cds="ZC_MATERIAL_MASTER" system="S4H"/> ↓ migrated in seconds // Datasphere replication flow out { "replicationFlow": "RF_MATERIAL_MASTER", "source": { "connection": "S4_CDS", "object": "ZC_MATERIAL_MASTER" }, "target": { "connection": "DATA_LAKE", "loadType": "DELTA" } }

One pipeline, end to end

Three steps. Each one feeds the next.

Inventorize

Connects to Xtract Universal and lists every existing extraction, classifying each as master or transactional, delta or full.

Match

Connects to your S/4 system to resolve each extraction as a CDS view or a classic SAPI DataSource — no manual lookup required.

Migrate

Generates the equivalent Datasphere replication flow for each extraction — combining matching ones into a single flow — and loads straight into your own data lake.

Your Theobald extractions, automatically rebuilt as replication flows.