SAP EWM runs the warehouse in SAP estates, embedded in S/4HANA or as a separate system. Lima reads stock, warehouse tasks and deliveries through the same released interfaces as the SAP connector, and writes back through BAPIs and released APIs.
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 |
|---|---|---|
| Released CDS views and table reads | Reads EWM tables and views. | Stock and tasks. |
| BAPIs and released APIs | Writes back. | Instructions. |
Released interfaces only; no ODP RFC (SAP Note 3255746); no HANA log capture (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 |
|---|---|
| /SCWM/ stock and bin tables | stock by bin and status |
| Warehouse tasks and orders | execution |
| Inbound and outbound deliveries | documents |
| Pattern | Supported |
|---|---|
| Full load | Yes |
| Incremental | Yes |
| Change capture | change pointers and table-level change capture |
| Streaming | — |
| Write-back | BAPIs and released APIs, confirmed |
The prerequisites are what the team that runs SAP Extended Warehouse Management 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.
Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
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.