What this is. A reference model. One consolidated, field-level definition of the Universal Journal and the structures around it, held in the open so that the people who work with it every day stop re-deriving it privately, in isolation, from the same documentation. It is a shared vocabulary — the thing a profession is supposed to have.
What this is not. It is not SAP software, an SAP product, or SAP data. There is nothing here to download from anybody's system, no code, no content of any customer's database. The structures are described so that a model can be reasoned about, and they are described in the source vendor's own vocabulary for one reason: a model that a practitioner cannot already read is a model nobody adopts.
Why extend the journal at all
S/4HANA's achievement was collapsing finance, controlling, assets and margin into one line — the Universal Journal. Every posting became one row, with every dimension it belongs to, in one place. But that row still answers exactly one question: what did this cost and where did the money sit. It cannot answer what the money did.
So the model extends it. Beside every accounting line sits an optional societal effect line — keyed on the accounting line's own key, so an effect cannot exist without a posting behind it and the financial record is never touched. Extension at the edges, never in the middle. A ledger that records only the amount is recording half the transaction.
Effect that travels down the organisation
Because the effect line carries the same cost object dimensions the accounting line does — cost centre, profit centre, WBS element, order, material, vendor, customer — an effect can be pushed down to the level that actually earned it. A branch, a crew, a parish, a single project. What a large organisation currently reports as one flat number at the top, this model can attribute to the part of the organisation that did the work. It also runs upstream and downstream: an effect can be recorded where it happened in the supply chain, not only where it was paid for.
Every claim carries its attribution method, its share, its evidence type, an evidence hash, and its verification status — self-attested, peer-reviewed, or independently assured. The taxonomy of effects is master data, so a community extends its own vocabulary without a schema change, and each category maps outward to the published disclosure point it answers, in the language a regulator or auditor already reads.
Recognition the community mints itself
An organisation that accomplishes what its peers could only plan for should be able to prove it and be visibly the better for it. Verified effect lines mint units into a recognition ledger — double-sided, reversible, hash-chained to its source, decaying if unspent. It is not a security and it is not a financial instrument; it is standing, and it is earned. Nothing is minted from an intention: no verified effect line behind it, no units. That is the whole difference between this and a sustainability brochure.
The same idea, applied to every interaction
If one line can carry a financial fact and its societal effect, it can carry any human interaction. ACDOCI is the Universal Journal's shape applied to interaction: a case, an incident, a phone call, a home visit, a class taught, a satellite session in a place with no road to it — the same row, the same dimensions, the same cost-object spine, so an interaction ties back to the money it caused and forward to the effect it produced.
The foundation is SAP, and it stays SAP. The consolidation begins with the two systems of record most interaction actually lives in — a CRM and a service-management platform — under one combined schema, then extends outward to telephony and satellite. That is not achieved by forcing two vendors to agree. It is achieved by a crosswalk registry that records, field by field, how each source maps onto the canonical line, with its transform, its confidence, and an honest unmapped where no mapping exists. A third system becomes configuration instead of a rewrite.
Voice keeps its call detail in IJTEL — numbers held only as salted hashes, because a mirror is not a wiretap. Remote links keep their pass window, elevation, rain fade and minutes-waiting-for-a-link in IJSAT, so service to places that have no other way to be reached can be measured honestly instead of averaged away against city traffic. Parties are pseudonymous keys: identity stays in the system already lawfully holding it. Every source is declared in the system-of-record register with its legal basis, because a mirror without a declared basis is surveillance.
A professional community, and the next generation
The member register is the point of the exercise. Firms, parishes, councils, schools and non-profits that post effects, verify each other's claims, and hold standing within a peer group — consolidating what they have each learned separately into one record the next generation can pick up and read, rather than learning it all again from scratch. Every member controls the visibility of its own record.
EVE DICOE Blueprint designs are available upon request and without charge to qualified non-profit organizations.
Vendors of legacy safety systems are offered these services free of charge. Emergency dispatch, alarm and monitoring, life safety, safety instrumented systems, marine and aviation safety, public safety communications. Work that keeps people alive is not a revenue opportunity.
Read the notice. Both waivers are recorded in the model itself, on the member register, so they cannot quietly stop being true.
How the model is written
Two names for every field. The legacy names are abbreviations
of German words — BUKRS from Buchungskreis, KOSTL from
Kostenstelle. A blueprint for those who come after should not hand them a foreign
language's consonant clusters, so every field also carries a canonical Latin name composed from
a published concept lexicon, with the legacy name preserved as the join key and shown on hover.
Translation happens at the concept layer, so switching the language selector renames the whole
model — all 9,872 fields — without one schema file changing.
Mirror, never cannibalise. Read-only, no write-back, no displacement of anybody's system of record. In exchange for cooperation, the model mirrors what it needs in order to offer a dimension the source platform does not offer. This page is that dimension.
It loads. The whole model materialises as PostgreSQL DDL — canonical column names, legacy names in column comments, round-trip views under the original table names, and a catalog that renames the model into ten languages with one query.
The extended journal · the Latin canon · the compact · coverage register