The reporting layer that remembers nothing
Ask the delivered reporting layer what is true and it answers instantly. Ask what was true, and it has nothing to consult: it queries the live tables, the live tables hold the present, and the past was overwritten where it stood.
◆ The architecture, plainlya real-time view with no store of the past behind it.
Delivered reporting reads the transactional schema through view objects, live. That design is why it is current to the second, and why it cannot remember: there is no warehouse underneath, no nightly copy, no snapshot store. Oracle says as much in its own positioning, which assigns deep historical trend analysis to its separately priced analytics product and keeps the delivered layer for operational questions about the present.
Understood that way, the layer is fine at its job. The trouble is every request that assumes memory: the five-year headcount trend, aging as it stood at the prior year end, the backlog a restructuring erased. Those fail not because a report was built wrong but because nothing was ever stored to build it on.
◆ How the absence shows upfive shapes of the same missing store.
| The request | What actually happens |
|---|---|
| A trend | Someone exports the number monthly into a spreadsheet archive. The trend is a person, remembering on a schedule. |
| An as-of date | Effective-date prompts re-run the present query against one past date at a time, where the tables support it at all. |
| Workforce history | A few pre-aggregated trend subject areas exist, monthly grain, fixed slices, not joinable to the rest. |
| Aging as it stood | Structurally unanswerable from open items that have since been paid. The method is on aging as of any date. |
| Usage history | Even the layer's own usage tracking purges records older than about six months, practitioner-observed. |
◆ The owned memorysnapshot facts as first-class tables, one pattern, every platform.
The fix is structural and small: a warehouse you own, where dated snapshot tables are first-class citizens. Receivables balances by day for aging, on-hand by day for inventory, workers by day for headcount. Each snapshot is one more partition of a table that only grows, and every trend, as-of, and comparison question becomes a filter.
The pattern is not an Oracle quirk. This catalog documents the same missing memory in Workday, where the delivered store keeps three years of month ends and purges the rest; the headcount history and trending store pages tell that half of the story. Different vendor, same sentence: the system only knows now, and the warehouse you own is where the past gets to exist.
- ERP
- Enterprise resource planning, the system of record for operations and finance.
- OTBI
- Oracle Transactional Business Intelligence, the delivered reporting layer.
- view object
- The query definition the reporting layer reads live tables through.
- transactional schema
- The live tables the business runs on, holding current state.
- subject area
- A delivered reporting bundle of related fields.
- pre-aggregated
- Summarized in advance at a fixed grain, so detail cannot be recovered.
- snapshot fact
- A table storing dated copies of a state, one row per thing per date.
- effective-date prompt
- A report input that re-runs the query as of one chosen past date.
- partition
- A storage segment of a large table, often one date each.