The Oracle finance stack, one map
ERP is where transactions happen. EPM is where they are consolidated, planned, and controlled. The warehouse you own is where they are analyzed. One map, three zones, and every arrow is a number moving.
Three zones, five arrows. BICC is the Business Intelligence Cloud Connector, the ERP side's extractor; export jobs carry the EPM side. Boxes and tools are doors: red on hover means it drills, into module references, tool guides, the FDI comparison, and the warehouse model. The rest link up as they go live.
◆ Drill: the overlaps that matter— where the products genuinely touch, and what each connection is for.
| Connection | What actually flows |
|---|---|
| General Ledger to Financial Consolidation and Close, FCCS | Trial balances by entity, loaded through Data Integration, consolidated into the group result. The single most travelled arrow in the stack. |
| General Ledger to Planning, EPBCS | Actuals land in the plan cube so budget and forecast have real actuals to compare against. Without this arrow, planning is fiction reviewed monthly. |
| Ledger and subledgers to Account Reconciliation, ARCS | Both sides of every reconciliation. ARCS is the referee between the ledger and its subledgers, and between the ledger and the outside world. |
| Consolidation to Tax Reporting, TRCS | The tax provision starts from consolidated results. Tax reads what consolidation produced, not the raw ledger. |
| Ledger and consolidation to Narrative Reporting | The statements. One report grid can read the ledger and the consolidation side by side, which is exactly what an income statement over a group needs. |
| Enterprise Data Management, EDMCS, above both | The hierarchies an organization actually configures, governed in one place: chart of accounts segments and their values, entity trees, cost center rollups, and alternate hierarchies for management views, all effective-dated, with subscriptions pushing approved changes to both sides. The cure for the chart of accounts drifting apart between the two worlds. |
| The quiet family resemblance | The GL balances cube inside Fusion is Essbase, the same engine EPM runs on. It is why Smart View talks to both, and why the skills transfer. |
| Everything to the warehouse | BICC extracts carry the ERP side, export jobs carry the EPM side, and the star holds them together, actuals beside plan beside consolidated, reconciled entity by entity. The analysis zone, and the one you own outright. |
The map is also a buying guide read backwards: Oracle sells each box separately, the arrows are where implementations succeed or fail, and the arrows are what this catalog documents, the extraction pattern, the owned star, and the module pages behind every box. Structure verified against Oracle's documentation, July 2026.
◆ Drill: the tool belt, every acronym placed— what reads, what moves, and what runs underneath, one line each.
| Tool | Full name, home, and the one thing it does |
|---|---|
| OTBI | Oracle Transactional Business Intelligence, inside Fusion ERP. Live operational reporting on subject areas, straight off the transaction tables. Best when someone needs an operational answer right now, this period, from one subject area. Known walls: cross-subject-area joins, the export row cap, timeouts on heavy close reports, no point-in-time history. |
| BIP | BI Publisher, now Oracle Analytics Publisher, inside Fusion. Pixel-perfect output from SQL data sets. Best for formatted documents, invoices, statements, statutory formats, anything a human signs or files. Not an analysis tool, and heavy data sets hit memory and time limits. Its scheduled data extracts, report files burst to storage, are also a legitimate light extraction route. |
| Smart View | The Excel add-in, both sides: the GL balances cube on ERP, every application cube on EPM. Best for ad hoc analysis by a finance power user who lives in Excel. Long refreshes can drop mid-flight, which is a design signal, not a network problem. |
| Financial Reporting | The legacy formatted-reporting studio on the balances cube and EPM. Best only for existing books already built on it; new work belongs in Reports. |
| FBDI | File-Based Data Import, into Fusion ERP. Best for bulk loads and conversions going in through the interface tables. Inbound only, the opposite of extraction. |
| BICC | Business Intelligence Cloud Connector, out of Fusion ERP. Best for exactly one thing, and the only right tool for it: bulk, scheduled, incremental extraction into your own storage. The ERP half of the owned pipeline. |
| REST and SOAP, ERP side | Fusion's per-object web services. Best for targeted pulls and transactional integration, one business object at a time. The wrong shape for bulk warehouse loads, which belong to BICC; the right shape when another system needs one record now. |
| OIC | Oracle Integration Cloud, between Fusion and other systems. Best for transactional flows to edge and third-party systems, orders out to a logistics platform, employee events to a badge system, and for orchestrating FBDI loads. Not an analytics pipeline. |
| Data Integration | Inside EPM, its front door for data. Best for pulling ledger trial balances and files into the EPM applications and mapping them on the way in, with Pipelines chaining the loads. Direction matters for a newcomer: it brings data in; the exits are EPM Automate and REST. Replacing old Data Management piece by piece. |
| EPM Automate and REST | The EPM side's exits, the command line and the API, both running named jobs. Best for scheduled extraction and orchestration from outside, cron calls the first, other systems call the second. |
| OAC | Oracle Analytics Cloud, Oracle's dashboarding platform. Best if a company is committed to all-Oracle visualization; a rented layer in the same role Power BI plays. |
| ADW | Autonomous Data Warehouse, Oracle's managed warehouse database. Best as the engine under FDI or an all-Oracle stack; a rented warehouse engine. |
| FDI | Fusion Data Intelligence, formerly Fusion Analytics Warehouse, now folding into Oracle's Fusion AI Data Platform branding: ADW plus OAC plus prebuilt pipelines, sold as a package. What is in the box: prebuilt KPIs, Oracle claims north of a thousand for ERP alone, dashboards, a semantic model, and managed pipelines into the warehouse. Best for teams that want Oracle to run the analysis zone and can live inside that prebuilt content. When the out-of-box content does not fit, the owned star above is the alternative, same job, your name on it. |
| OCI | Oracle Cloud Infrastructure, the cloud everything above runs on. Best as the home for a small compute instance and a bucket running your extraction cron near the source. |
The pattern worth noticing: every tool is either a reader, a mover, or a platform, and the confusion in most teams comes from tools being sold as more than they are. The catalog's OTBI, BIP, and BICC guide settles the ERP side in depth; the extraction pattern settles the EPM side.
◆ Where Irvine Analytics sits on this map— the layer we build, the pattern behind it, and the console on top.
We build the bottom box. Oracle owns the top two zones and does them well; the analysis zone is the one a company should own outright, and that is our whole business.
| The pattern, four layers | What it is |
|---|---|
| 1 · Extract everything | BICC pulls the ERP modules, ledger and subledgers. Export jobs pull the EPM side, consolidated results, plans, reconciliation status. Every module on the map above, one landing zone. |
| 2 · Preserve, then model | Raw data lands unchanged, then flattens into the one star: facts at level zero, dimensions from the metadata, actuals beside plan beside consolidated. The Kimball shape, on your cloud. |
| 3 · Reconcile before anyone reports | The consolidated number ties to the ledger, entity by entity, as a gate. Payables tie to the ledger control accounts. Nothing publishes until the ties pass, and the pass log is yours. |
| 4 · The console on top | The product face: reports, and the read-only Analyst console, an assistant that answers close questions from the reconciled star. It computes nothing and writes nothing, which is exactly why its answers can be trusted in a close. Deterministic ground underneath, probabilistic questions on top. |
The engagement shape is fixed-price and short, the first module live in about ten business days, and everything, the pipeline, the star, the reconciliation queries, the runbook, is handed over owned. Not a platform subscription on top of your Oracle subscriptions; the one zone of this map with your name on it. The working console is on the home page, live, using the same pattern.
- system of record
- The ERP. Transactions happen here, and every number ties back here.
- system of control
- EPM. Consolidation, planning, reconciliation, provision, statements.
- system of analysis
- The warehouse you own. Both sides, one star, reconciled.
- the arrows
- Where numbers move, and where implementations succeed or fail.
- balances cube
- The Essbase cube inside Fusion GL. The family resemblance between the zones.