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.
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.
| Method | What it does | When it is used |
|---|---|---|
| Open Hub destinations | Exports InfoProvider content to tables or files that Lima reads. | Scheduled extracts of reporting data. |
| Active-table reads through HANA SQL | Reads the active tables of advanced data store objects directly, where the licence allows. | Migrations and archives of BW history. |
| Released query and view interfaces | Reads BW queries and CDS views released for extraction. | Curated reporting data. |
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.
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.
| Object | Plain meaning |
|---|---|
| ADSO active tables | advanced data store objects: the tables that hold the data |
| InfoObjects | master data and texts |
| CompositeProviders | combined views for reporting |
| Open Hub tables | exported data sets |
| Pattern | Supported |
|---|---|
| Full load | Yes |
| Incremental | by request or load date |
| Change capture | — |
| Streaming | — |
| Write-back | — |
The prerequisites are what the team that runs SAP BW and BW/4HANA grants. The four steps are the same for every connector.
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 →
Each pair page covers one path end to end: objects out, model in, checks, cadence and the offer.
Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →No add-on is installed. Lima connects from outside through the interfaces listed above, with a user and authorisations your administrators grant.
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.
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.
Yes. Most estates start with one source, one target and one dataset, then add tables and patterns on the same connection.
A trial connects this system, runs a first load and ends with a reconciliation report. Your administrators see the prerequisites before anything is installed.