Connectors SAP Extended Warehouse Management

SAP Extended Warehouse Management data integration with Lima, in both directions.

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.

SOURCESAP Extended Warehouse ManagementReleased CDS views and table reads · BA…LIMA BACKBONEExtractfull · incremental · change captureCheckevery row valid, or an exception with a…Transform and load150+ operators · Python · loads on the…TARGETSPlanning applicationsKinaxis · o9 · Blue Yonder · IBP · OMPWarehouses and lakehousesSnowflake · Databricks · Fabric · S3 …Reporting and partnersPower BI · Tableau · EDI · filesRESULTS RETURN TO SAP EXTENDED WAREHOUSE MANAGEMENT · EACH WRITE CONFIRMED
How SAP Extended Warehouse Management fits the six Backbone steps. It is a source and a target: data comes out through the methods below, and results go back in with confirmation.
2
ways to read or write it
this connector
4
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 and writes SAP Extended Warehouse Management

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
Released CDS views and table readsReads EWM tables and views.Stock and tasks.
BAPIs and released APIsWrites back.Instructions.
Compliance statement for this connector

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.

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
/SCWM/ stock and bin tablesstock by bin and status
Warehouse tasks and ordersexecution
Inbound and outbound deliveriesdocuments
PatternSupported
Full loadYes
IncrementalYes
Change capturechange pointers and table-level change capture
Streaming—
Write-backBAPIs and released APIs, confirmed
Before you start

Prerequisites, then four steps.

The prerequisites are what the team that runs SAP Extended Warehouse Management grants. The four steps are the same for every connector.

  • As for SAP S/4HANA, with EWM authorisations
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 Extended Warehouse Management in a source-to-target path.

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

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 Extended Warehouse Management?

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 Extended Warehouse Management 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 Extended Warehouse Management 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.