The model the SAP pages assume

Every SAP page in this catalog ends the same way: the delivered path cannot, the owned model can. This page is that model, stated once: three structures, one dataflow, and the map of which page reads what.

RuleOne landed layer serves every SAP page in this catalog: journal lines with ledger and currency qualified, daily positions for anything with a balance, and history conformed across the migration seam.

Neverbuild a separate extract per report. Every page here reads the same three structures; a report with its own pipeline is a reconciliation you have not had yet.

Everything lands, conforms once, and serves every page. The three structures below are the whole vocabulary.

◆ The three structureswhat every SAP page on this site reads.

Structure	Grain	What it carries
fct_journal_line	one row per journal line	Amount with ledger, currency type, account, and partner as columns; every figure arrives qualified.
fct_daily_position	one row per object per day	Stock, open items, and order backlog as stored positions; as-of questions become one filter.
landed history	as the source kept it	Costing-based margin, painter definitions, pre-migration lines, conformed across an explicit seam.

Nothing here is exotic. The model’s whole job is that the delivered system stores now and recomputes then, while this layer stores then and reads it.

◆ What each page readsthe anchor map for the editorial layer.

Page	Reads
Currency and ledgers	fct_journal_line: the four-way qualification is a grouping.
Open items as of a past date	fct_daily_position: the stored aging that never rewinds.
Stock as of a past date	fct_daily_position: positions, not movement reversal.
Order backlog as of a past date	fct_daily_position: backlog by day, statuses preserved.
Inventory aging	fct_daily_position joined to receipts: age with value.
Uncleared receipts and invoices	fct_daily_position: the open-line snapshot with reasons.
Purchase price variance	fct_journal_line: the variance postings, pivotable at last.
Margin history	landed history: the seam explicit, one series.
The painter rebuild	landed history: definitions extracted as data.
Analytics that only know today	the whole layer: the memory the live tables lack.

Use case

Problem

Twelve SAP editorial pages describe owned answers, but the model they assume lived only as scattered references, and every kept query pointed at nothing.

What we build

One reference page for the layer: the three structures with their grain, the dataflow that fills them, and the anchor map from every page to what it reads.

What you get

A place for the queries to point: each editorial page anchors here, new pages inherit the vocabulary, and the layer reads as one build instead of twelve.

Want this layer running on your cloud?

We land, conform, and hand over the model every SAP page here assumes.

Talk to us

Terms on this page

SAP S/4HANA: The source system this layer lands from and outlives.
landed raw: Extracts kept as received; the layer that makes reloads honest.
conformed dimension: One meaning per key across every fact: material, partner, ledger.
daily position: A stored balance per object per day; the as-of answer.
journal line: The qualified grain: amount with ledger, currency type, account.
the seam: The dated boundary where migrated history meets new postings.