Objective
Design a finance reporting pack that answers close and operational questions quickly with consistent definitions.
Case study 10
Portfolio knowledge project
OTBI & Smart View Reporting Pack
A controller-ready reporting pack design — trial balance, account analysis, AP/AR aging, close dashboards, and Smart View retrieval patterns that support decisions, not just extracts.
Knowledge / portfolio case study only. Not employment history, not a named client engagement, and not a certification claim.
Context
Teams often rebuild spreadsheets every month because reports are inconsistent, slow, or not trusted.
Scope
Core GL/AP/AR report catalog, prompt standards, Smart View layout notes, and close dashboard wireframes.
Approach
List decisions by role → map to reports → define prompts & filters → design folder structure → document refresh cadence → UAT with sample periods.
- 01Audience & decisionsController, AP, AR, FP&A needs.
- 02Catalog designOfficial vs working reports.
- 03Prompt standardsLedger, period, entity filters.
- 04Smart View packClose workbook structure.
- 05UAT & handoverValidate and document owners.
01Audience decisions
02Catalog design
03Prompt standards
04Smart View pack
OTBI & Smart View Reporting Pack
Key design decisions
- One official TB definition
- Stop version wars.
- Smart View for repeating close packs
- OTBI for operational queries.
- Name reports by decision, not module only
- Improve findability.
Walkthrough
Run TB by ledger → drill account analysis → pull AP aging → refresh Smart View close pack → compare to prior period.
Controls
Report definitions owned by finance systems; ad-hoc extracts labeled as non-official; period prompts mandatory.
Oracle modules in focus
OTBI
Smart View
GL
AP
AR
Deliverables
Report catalog
prompt standard
Smart View pack outline
dashboard wireframes
UAT checklist.
Outcomes
Demonstrates reporting design that supports close and leadership conversations.