SAP BW & BW/4HANA to Databricks

Your BW flows, rebuilt as a Databricks lakehouse.

Point the accelerator at your BW system. It maps every flow from DataSource to query, converts standard BW patterns with the built-in rules of the Intellus framework, uses AI to translate custom ABAP into Python or SQL notebooks, and generates bronze, silver and gold pipelines with a star schema in gold. On Azure, AWS or GCP, with the ingestion route you choose.

SAP BW
RSDS2LIS_11_VAHDR
ADSOSALES_HDR
TRFNend routine · ABAP
IOBJ0MATERIAL
HCPRSALES_RPT
mapped, translated, generated
Databricks
BRZbronze.sd_vahdr
SLVsilver.sales_order_hdr
NBnb_sales_hdr_rpt.py
GLDgold.dim_material
GLDgold.fact_sales
4 steps
map, translate, generate, deploy
Cloud-agnostic
Azure, AWS and GCP alike
Open ingestion
Datasphere or the cloud's own service
Rules first
AI only for custom ABAP
Star schema
facts and conformed dimensions in gold
Why use this tool

Your BW logic, carried over instead of rewritten from memory.

Moving BW to Databricks is mostly translation. Hundreds of transformations, start and end routines, master-data lookups and delta rules all have to arrive as working code. Done by hand, each routine is opened, understood and rewritten one at a time, and the lineage back to BW gets lost along the way.

Rules for the standard. AI for the custom. The Intellus Databricks framework contains conversion rules for the patterns every BW system shares: InfoObjects, ADSOs, delta loads, time-dependent attributes, currency and unit conversion. These convert deterministically, with no AI involved. AI is only used for custom ABAP routines, and its output lands in the same framework, with the same medallion layers, naming and data-quality checks. Every notebook and table keeps a reference to the BW object it replaces.

Without the accelerator

Every DataSource, ADSO and transformation rebuilt by hand in Spark: reading ABAP routines line by line, re-deriving delta logic, and designing the gold model from scratch while the BW reports keep running.

With the accelerator

The BW landscape is mapped automatically, standard objects are converted by framework rules, custom routines arrive as reviewed notebooks, and bronze, silver and gold land in one consistent structure. Data engineers spend their time on validating results and on the routines that need real judgement.

Predictable by design: because the bulk of a BW landscape follows standard patterns, most objects go through framework rules instead of AI. That keeps results repeatable across runs and environments, and keeps AI cost limited to the routines that genuinely need it.

Lineage first: the BW dependency tree is the backbone of the migration. Only flows that are actually used come along, and each Databricks object can be traced back to its BW source for reconciliation.

Your cloud, your ingestion

Several paths, one lakehouse.

The cloud and the ingestion route are choices you make per project. The generated Databricks layers stay the same on every path. Pick a combination to see the route.

Cloud
Ingestion
Source
SAP BWBW 7.x or BW/4HANA, flows mapped
Ingestion
SAP DatasphereReplication flows, used for ingestion only
Landing
ADLS Gen2Raw files in your own storage account
Bronze
Raw Delta tablesOne per source, load metadata kept
Silver
Cleaned & conformedADSO logic and routines as notebooks
Gold
Star schemaFacts and conformed dimensions
Changes with your choiceGenerated the same on every path
Unity CatalogCatalogs and schemas per layer, with lineage and access control.
Python or SQLEach routine as a notebook in the language your team maintains.
Deployed as codeJobs and pipelines versioned in Git, promoted from dev to prod.
Checked routesEach ingestion route is checked against SAP's rules for third-party extraction before we recommend it.
What is automated

The translation work, carried for you.

Each BW object's metadata and code is read and its Databricks equivalent built inside the framework. Standard patterns go through framework rules, the same way every time. Custom ABAP goes through AI and is reviewed. Anything that needs a human decision is flagged, never guessed.

framework rule, no AI AI, reviewed by an engineer flagged for a human decision
Flow lineage, DataSource to query
InfoObjects as dimensions with attributes & texts
ADSOs as silver Delta tables with their keys
Field mappings, constants & standard formulas
Full and delta loads as MERGE logic
Time-dependent attributes as SCD type 2
Currency & unit conversion carried over
Start, end, field & expert routines as notebooks
Custom master-data lookups as joins
Star schema design in gold
Routines without a clean translation
translate · TRFN SALES_HDR → RPT · end routine
* BW end routine (ABAP) LOOP AT RESULT_PACKAGE ASSIGNING <res>. SELECT SINGLE matl_group FROM /bi0/pmaterial INTO <res>-matl_group WHERE material = <res>-material. IF <res>-netwr <= 0. DELETE RESULT_PACKAGE. ENDIF. ENDLOOP. ↓ custom routine: translated by AI, flagged for review # nb_sales_hdr_rpt.py · silver → gold mat = spark.table("silver.dim_material") .filter("objvers = 'A'").select("material", "matl_group") df = (spark.table("silver.sales_order_hdr") .join(mat, "material", "left").filter("netwr > 0")) write_gold(df, "gold.fact_sales", keys=["doc_number"])
One pipeline, end to end

Four steps. Each one feeds the next.

01

Map your BW

Reads metadata over RFC and maps the dependency tree from DataSource through transformations and ADSOs to CompositeProviders and queries. Unused objects stay behind.

02

Translate the logic

Standard transformations go through framework rules, with no AI. Custom ABAP routines are translated by AI into Python or SQL notebooks, each kept next to its source routine for review.

03

Generate the lakehouse

The framework builds bronze ingestion, silver conformed tables and a gold star schema: facts at the grain of your ADSOs, dimensions from your InfoObjects.

04

Deploy to your cloud

Jobs and pipelines deployed to Databricks on Azure, AWS or GCP, wired to the ingestion route you chose and registered in Unity Catalog.

Run it against your sandbox first

A demo takes 30 minutes. Bring your own BW flows.

Book a demo