SAP ECC is the SAP ERP release that about half of SAP's ERP customers still run, with mainstream maintenance ending on December 31, 2027. Lima reads its tables and business objects through released interfaces and writes planned orders, requisitions and master-data corrections back through BAPIs and IDocs, each write confirmed by SAP.
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 |
|---|---|---|
| Table reads through a released function module | Reads any application table in partitions, many tables at a time, inside a session cap agreed with the Basis team. | First loads, migrations, archives and nightly copies. |
| BAPIs and function modules | Reads business objects with their business logic applied, and writes them back. | Stock, orders and master data; every write-back. |
| Change pointers and table-level change capture | Reads only the rows that changed since the last run. | Incremental loads on the planning calendar. |
| Extractor delta queues | Reads the delta of a standard extractor, where the extractor is released for the purpose. | Logistics and finance extractors with a working delta. |
| IDocs | Sends or receives standard business documents. | Orders, deliveries and master-data messages in both directions. |
Lima reads SAP through released interfaces: table reads through a named function module, BAPIs, CDS views where available, change pointers and extractor delta queues. It does not use the ODP RFC interface that SAP Note 3255746 restricts, it does not use RFC_READ_TABLE in production (SAP Note 382318), and it does not read the HANA database log (SAP Note 2971304). No add-on is installed in SAP.
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 |
|---|---|
| MARA · MARC · MARD | material master: general, plant and storage-location views |
| STKO · STPO · MAST | bills of material and their assignment to plants |
| PLKO · PLPO · MKAL | routings and production versions |
| EKKO · EKPO · EKET | purchase orders, lines and schedule lines |
| VBAK · VBAP · VBEP | sales orders, lines and schedule lines |
| AFKO · AFPO · AFRU | production orders and confirmations |
| MSEG · MKPF · MBEW | material movements and valuation |
| KNA1 · LFA1 | customers and suppliers |
| BKPF · BSEG | accounting documents (cluster table read through a released module) |
| Pattern | Supported |
|---|---|
| Full load | Yes |
| Incremental | Yes |
| Change capture | change pointers, table-level change capture, extractor deltas |
| Streaming | — |
| Write-back | BAPIs and IDocs, each write confirmed |
A planning dataset is assembled from these objects. The pair pages show how each planning application shapes them.
| Planning object | Source objects in SAP ECC |
|---|---|
| Items | MARA · MARC · MARD · MBEW |
| Bills of material | STKO · STPO · MAST · STAS |
| Routings and production versions | PLKO · PLPO · MKAL |
| Stock by status and date | MARD · MSKA · MSLB · MCHB |
| Open purchase orders | EKKO · EKPO · EKET · EKBE |
| Open sales orders | VBAK · VBAP · VBEP · VBUP |
| Production orders | AFKO · AFPO · AFRU |
| Forecast and planned independent requirements | PBIM · PBED |
| Customers and suppliers | KNA1 · KNVV · LFA1 · LFM1 |
| Calendars | TFACD · TFACS · T001W |
The prerequisites are what the team that runs SAP ECC 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 →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 →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 →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 →3 more pair pages for SAP ECC are listed in the directory.
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.
