Connectors SAP BW and BW/4HANA

SAP BW and BW/4HANA data integration with Lima.

SAP BW is SAP's data warehouse. Many estates keep years of reporting history in it. Lima reads InfoProviders and advanced data store objects through Open Hub destinations and released interfaces, and reads the active tables through HANA SQL where the licence allows, so the history can move to a lakehouse with a count check per object.

SOURCESAP BW and BW/4HANAOpen Hub destinations · Active-table rea…LIMA BACKBONEExtractfull · incrementalCheckevery row valid, or an exception with an…Transform and load150+ operators · Python · loads on the c…TARGETSPlanning applicationsKinaxis · o9 · Blue Yonder · IBP · OMPWarehouses and lakehousesSnowflake · Databricks · Fabric · S3 …Reporting and partnersPower BI · Tableau · EDI · files
How SAP BW and BW/4HANA fits the six Backbone steps. It is a source: Lima extracts from it, checks and transforms the rows, and loads them where they are needed.
3
ways to read it
this connector
2
patterns supported
this connector
3
ways to run: SaaS, private cloud, on-premise
product
22 days
from contract to production
showcase estate
How Lima reads SAP BW and BW/4HANA

Method by method.

Each method has a job. The first load uses the bulk method; the daily run uses the incremental or change-capture method; write-back uses the interface the system itself uses.

MethodWhat it doesWhen it is used
Open Hub destinationsExports InfoProvider content to tables or files that Lima reads.Scheduled extracts of reporting data.
Active-table reads through HANA SQLReads the active tables of advanced data store objects directly, where the licence allows.Migrations and archives of BW history.
Released query and view interfacesReads BW queries and CDS views released for extraction.Curated reporting data.
Compliance statement for this connector

Open Hub destinations and released interfaces. No ODP RFC (SAP Note 3255746). Direct active-table reads are used only where the customer's licence permits database access; confirm with the licence owner.

Dated draft, pending sign-off by engineering and legal. The full statement, with the named function module, is on the trust center.

What it covers

Objects and patterns.

The objects are the tables, views or records Lima reaches through the methods above. The patterns say how a copy is made and kept current.

ObjectPlain meaning
ADSO active tablesadvanced data store objects: the tables that hold the data
InfoObjectsmaster data and texts
CompositeProviderscombined views for reporting
Open Hub tablesexported data sets
PatternSupported
Full loadYes
Incrementalby request or load date
Change capture—
Streaming—
Write-back—
Before you start

Prerequisites, then four steps.

The prerequisites are what the team that runs SAP BW and BW/4HANA grants. The four steps are the same for every connector.

  • Open Hub licence where required
  • Read access to the BW schema in HANA for active-table reads
  • Agreed run windows
Register the connectionEndpoint, credentials from the vault, and the method. The connection is tested and a failed test names the cause.
Choose the objects and the patternPick tables or objects from the discovered schema, and the pattern: full, incremental, change capture or streaming.
Run the first load with checks onEvery row is valid or becomes an exception with an owner. The run ends with a count and a control total per table.
Schedule it on the business calendarA run window with a deadline; pause, resume and replay if a check trips; the report after every run.
What happens to a bad record

Incoming data = valid records + exception records. A row that fails a check is kept, routed to the person who owns it with a deadline, and replayed once fixed. The load carries on with the valid rows and the report says exactly what was held back. How exceptions work →

Pair pages

SAP BW and BW/4HANA in a source-to-target path.

Each pair page covers one path end to end: objects out, model in, checks, cadence and the offer.

/connectors/sap-bw-to-snowflake

SAP BW and BW/4HANA to Snowflake

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/sap-bw-to-databricks

SAP BW and BW/4HANA to Databricks

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/sap-bw-to-microsoft-fabric

SAP BW and BW/4HANA to Microsoft Fabric

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/sap-bw-to-bigquery

SAP BW and BW/4HANA to Google BigQuery

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/sap-bw-to-amazon-redshift

SAP BW and BW/4HANA to Amazon Redshift

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/sap-bw-to-azure-synapse

SAP BW and BW/4HANA to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/sap-bw-to-amazon-s3

SAP BW and BW/4HANA to Amazon S3

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/sap-bw-to-azure-data-lake-storage

SAP BW and BW/4HANA to Azure Data Lake Storage Gen2

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/sap-bw-to-google-cloud-storage

SAP BW and BW/4HANA to Google Cloud Storage

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
Status and evidence

Stated plainly, with dates.

Active-table read path: confirm licence position with SAP account team
Terms on this page

Plain meanings.

ConnectorA packaged way to read or write one kind of system, with its authentication, methods and prerequisites described.
Full, incremental, change capture, streamingFour ways to make and keep a copy: read everything; read what changed since last time; read changes from a log as they happen; consume events in small batches.
Write-backWriting a result into the system that owns it through its released interface; the system's response is the confirmation.
Control totalThe sum of a key amount column compared between source and target, along with the row count, at the end of a run.
Exception recordA row that failed a check: kept, routed to an owner, replayed once fixed.
Released interfaceAn SAP interface SAP documents and supports for external use: BAPIs, released function modules, released CDS views, IDocs. The ODP RFC path is the one SAP restricts.
Questions

Asked about this connector.

Does Lima install anything in SAP BW and BW/4HANA?

No add-on is installed. Lima connects from outside through the interfaces listed above, with a user and authorisations your administrators grant.

How is load on SAP BW and BW/4HANA kept in check?

Parallel reads are capped and the cap is agreed with the team that runs the system. Large reads run inside an agreed run window. Change capture keeps the daily volume small.

What do we see when a run finishes?

A report per run: rows in, rows out, control totals and variance per table, the exceptions held back and who owns them, and whether the deadline was met.

Can we start small?

Yes. Most estates start with one source, one target and one dataset, then add tables and patterns on the same connection.

Try SAP BW and BW/4HANA on your own estate.

A trial connects this system, runs a first load and ends with a reconciliation report. Your administrators see the prerequisites before anything is installed.