MSAMM
Back to course

Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 1 · The Fusion technical landscape

The layers, end to end

Lesson 5 of 177 · 3 min

From the browser to the database and back, so you know what you can reach. The UI layer is what a user sees, and almost none of it is yours to change — what you can change is covered in Modules 12 and 13, and the boundary is narrower than people expect. The application services layer holds the business logic: it validates, it derives, it enforces. Everything you load or call goes through it, which is why a file that looks correct in a spreadsheet can still be rejected. The reporting stack is two tools over one set of data — BI Publisher for documents and extracts, OTBI for analysis — and each reads through a different structure. The scheduler (ESS) runs everything that happens in the background. The integration surface is REST and SOAP services plus file-based loading, and it is the only supported way in and out. DIRECT

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 1 · The Fusion technical landscape

  1. 1The layers, end to end
  2. 2What SaaS actually forbids, and why
  3. 3Where each kind of request belongs
  4. 4Release trains and what they mean for you
  5. 5Reading Oracle documentation without drowning
  6. 6The technical consultant toolkit
  7. 7Lab briefing · Mapping a real request