SAP HANA is also used as a standalone database for custom applications and data marts. Lima reads customer-owned schemas over SQL in partitions and loads HANA targets. SAP application tables under S/4HANA are read through the SAP connector's released interfaces; Lima does not read the HANA database log for them.
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 |
|---|---|---|
| SQL reads over JDBC | Reads customer schemas in partitions. | Data marts and custom apps. |
| Bulk inserts | Loads HANA targets. | HANA as a target. |
Direct SQL reads apply to customer-owned schemas. SAP application tables are read through released interfaces (see SAP S/4HANA). No reading of the HANA database log (SAP Note 2971304).
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 |
|---|---|
| Customer schemas | tables and calculation views the customer owns |
| Pattern | Supported |
|---|---|
| Full load | Yes |
| Incremental | Yes |
| Change capture | by change columns (no log capture) |
| Streaming | — |
| Write-back | — |
The prerequisites are what the team that runs SAP HANA (as a database) 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 →
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.