One record per real customer, assembled from the ERPs, the CRM and the portals, with every source key kept.
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 |
|---|---|---|---|
| Customer general data | KNA1 · ADRC (business partner BUT000 in S/4) | KUNNR · NAME1 · LAND1 · PSTLZ · STCEG (VAT) · KTOKD | live; change capture where enabled |
| Company-code and sales views | KNB1 · KNVV | BUKRS · ZTERM (terms) · VKORG · KDGRP · VSBED | live; change capture where enabled |
| Partner functions | KNVP | PARVW (sold-to, ship-to, payer) · KUNN2 | live; change capture where enabled |
| Credit | UKMBP_CMS_SGM | CREDIT_LIMIT · CREDIT_SGMNT | live; change capture where enabled |
| Sales orders | VBAK · VBAP | VBELN · KUNNR · NETWR · ERDAT | live; change capture where enabled |
The first object above carries the strong keys; the standardised attributes come from the same rows. Two records match when a strong key agrees, or when name and address agree closely and no strong key disagrees.
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_BUPA_CREATE_FROM_DATA · BAPI_CUSTOMER_CHANGEFROMDATA1 (S/4 business partner) · IDoc DEBMAS | golden values approved for write-back: identity; addresses; contacts and roles | 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 |
|---|---|---|
| Customer general data | KNA1 · ADRC (business partner BUT000 in S/4) | KNA1/KNB1/KNVV customer master, XD01 through BAPI; credit in KNKK |
| Company-code and sales views | KNB1 · KNVV | same objects |
| Partner functions | KNVP | same objects |
| Credit | UKMBP_CMS_SGM | same objects |
| Sales orders | VBAK · VBAP | same objects |
Customer 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.
