The model the Oracle pages assume

Every Oracle editorial page here ends at the same door: the tenant purges, overwrites, or trims, and the owned layer remembers. This page states that layer once: three structures, one dataflow, and the map of which page reads what.

RuleOne landed layer serves every Oracle page in this catalog: document lines joined across the procure-to-pay spine, workflow events landed before the purge, and daily snapshots for anything the tenant stores only as now.

Neverlet each editorial answer imply its own build. The pages share three structures; pretending otherwise multiplies pipelines and divides trust.

Extracts, archives, and snapshots land once and serve every page. The three structures below are the whole vocabulary.

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

Structure	Grain	What it carries
fct_document_line	one row per document line	Orders, receipts, and invoices with the keys that join them; the spine no delivered view spans.
fct_workflow_event	one row per approval step	Who approved what, when, landed daily while the tenant still remembers.
fct_daily_snapshot	one row per object per day	On-hand quantities and balances the tenant stores for one date only: today.

The pattern repeats across platforms on purpose: land what disappears, snapshot what gets overwritten, conform the keys once. The Workday spine and the SAP layer are the same idea wearing different table names.

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

Page	Reads
Three-way match	fct_document_line: the exception list is a join.
Approval history vanishes	fct_workflow_event: landed before the 30-day purge.
Approval cycle time	fct_workflow_event: days per desk, forever answerable.
Stock as of any date	fct_daily_snapshot: year-end units, instantly.
The layer that remembers nothing	fct_daily_snapshot: the memory, built on purpose.
The export ceiling	the landing pattern: full extracts below the ceilings.
The report that lies quietly	the whole layer: one declared population, not per-user trims.
What you own	all three: the owned alternative the rent is measured against.

Use case

Problem

Eight Oracle editorial pages describe owned answers with queries that pointed at an unstated model; the layer existed only as an implication.

What we build

One reference page: three structures with their grain, the dataflow from extract paths, archives, and snapshots, and the anchor map from every page to what it reads.

What you get

The layer stated once: every query anchored, every page inheriting the same vocabulary, and the owned alternative concrete enough to price against the rent.

Want this layer running on your cloud?

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

Talk to us

Terms on this page

SAP S/4HANA: The sibling platform; its owned layer follows the same pattern.
landed raw: Extracts kept as received; reloadable, auditable.
conformed dimension: One meaning per key: supplier, item, ledger, date.
document spine: Order, receipt, and invoice lines with their joining keys.
workflow event: One approval step, landed daily before the purge.
daily snapshot: A stored per-day state for what the tenant keeps as now only.