The chart of accounts as governed master data: one account list, its groupings, its company-code views and the mappings to every local chart.
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 |
|---|---|---|---|
| Chart of accounts | SKA1 · SKAT | KTOPL · SAKNR · TXT50 · XBILK · GVTYP | live; change capture where enabled |
| Company-code view | SKB1 | BUKRS · SAKNR · XSPEB · WAERS | live; change capture where enabled |
| Financial statement version | T011 · FAGL_011ZC | VERSN · ERGSL | live; change capture where enabled |
| Journal | ACDOCA | RACCT · RBUKRS · FISCYEARPER · HSL | live; change capture where enabled |
The first object above carries the strong keys; the standardised attributes come from the same rows. Local accounts map to exactly one group account per version; the mapping is master data with its own history.
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_ACC_GL_ACCOUNT_CREATE (where released) · IDoc GLMAST | golden values approved for write-back: account; groupings; company-code view | 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 |
|---|---|---|
| Chart of accounts | SKA1 · SKAT | SKA1/SKB1; journal in BKPF/BSEG |
| Company-code view | SKB1 | same objects |
| Financial statement version | T011 · FAGL_011ZC | same objects |
| Journal | ACDOCA | same objects |
General ledger account 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.
