BW to Datasphere | Intellus Accelerator

Why use this tool

Less repetition, more judgement.

A BW to Datasphere migration is mostly volume: hundreds of InfoObjects and (a)DSOs that all follow the same pattern. Handled by hand, that volume is where most of a project's hours go, time that should be spent on the parts that actually need a person.

20–40% Estimated project effort gain when the accelerator carries the bulk of the migration.

Without the accelerator

Every InfoObject, (a)DSO and transformation rebuilt by hand, field by field: the same mechanical work repeated hundreds of times across the landscape.

With the accelerator

The bulk of that volume is converted automatically, so data engineers spend their time on the complex transformations and on verifying that what came out is correct.

Pre-trained, not per-run AI: the conversion logic is already trained on the Intellus Datasphere methodology, so no AI tokens are consumed for the bulk of the migration. Tokens are only spent where custom logic genuinely needs converting, keeping the migration cost-efficient.

What is automated

The repetitive modeling work, carried for you.

Each BW object's metadata is read and its native Datasphere equivalent generated, with the SAP modeling rules built in. Anything that needs a human decision is flagged, never guessed.

Dimensions with attributes & texts

Fact & staging tables from ADSOs

Replication & transformation flows

Keys, measures, currencies & units

ABAP routine translation (AI, reviewed)

Deployment to the right spaces

Hierarchies, where a CDS alternative exists

Full & delta load logic carried over

convert · ADSO_SALES_HDR.xml

// BW ADSO in <adso:dataStore name="SALES_HDR" activateData="true"> <element name="VBELN" keyElement="true" .../> <element name="NETWR" semantics="AMO" .../> ↓ converted in seconds // Datasphere local table out "SALES_HDR": { "@ObjectModel.modelingPattern": "ANALYTICAL_FACT", "VBELN": { "key": true, "type": "cds.String" }, "NETWR": { "@Semantics.amount.currencyCode": "WAERK" } }

One pipeline, end to end

Three steps. Each one feeds the next.

Inventorize your BW

Connects over RFC and maps the dependency tree of a flow. Only objects that are actually used come along — unused ones stay behind.

Convert with the rules built in

Keys, measures, currencies, time-dependency, text tables: the SAP modeling rules are encoded so you don't rediscover them per object.

Deploy to the right spaces

Staging objects go to your inbound space, models to the warehouse space, routed automatically via the Datasphere CLI.

Your BW models, automatically rebuilt in Datasphere.