Work centres, capacities and routings as governed master data consistent with the BOMs and the site calendars.
Tables are read in place through the SAP connector, using released read interfaces and change capture where the basis team allows it. The rows stay in SAP.
| Object | Read from | Fields the domain uses | Freshness |
|---|---|---|---|
| Work centre | CRHD · CRTX · KAKO | ARBPL · WERKS · KAPAZ · KOSTL (CRCO) | live; change capture where enabled |
| Routing header and operations | PLKO · PLPO · PLAS · MAPL | PLNNR · PLNAL · VORNR · ARBID · VGW01… | live; change capture where enabled |
| Confirmations | AFRU | AUFNR · VORNR · ISMNW | live; change capture where enabled |
The first object above carries the strong keys; the standardised attributes come from the same rows. Operations name golden work centres, and the rules keep times and capacities inside the site's calendar.
Writes go through released BAPIs and IDocs. Each call returns a document number or an error message, and Lima records both beside the change.
| Interface | Used for | Result |
|---|---|---|
BAPI_ROUTING_CREATE · CRHD through work-centre BAPIs (BAPI_WORKCENTER_*) | golden values approved for write-back: work centre; routing; operations | the id or error SAP S/4HANA returns, stored beside the change |
Write-back is off per object until a test write succeeds, and approval rules can require a person per object. Reconciliation compares the source row with the golden value on a schedule.
SAP roles are mapped to Lima access policies once. A steward who sees purchasing organisation 1000 in SAP sees the same rows here.
| Object | On SAP S/4HANA | On SAP ECC |
|---|---|---|
| Work centre | CRHD · CRTX · KAKO | same tables |
| Routing header and operations | PLKO · PLPO · PLAS · MAPL | same objects |
| Confirmations | AFRU | same objects |
Routings and work centres on
Other domains on SAP S/4HANA
The golden record reads the objects above in place. History the pivot needs at scale is landed in your lake by the Backbone, under the same keys, security and audit.
Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in SAP S/4HANA.
Yes. Write-back stays off per object until a test write succeeds; the golden view, the API and the pivots work from day one on reads.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.
