MSAMM
Back to course

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

What SaaS actually forbids, and why

Lesson 6 of 177 · 2 min

No custom tables. No triggers. No direct DML. Those three refusals define the job. Read as a limitation, this is frustrating. A requirement that would take an afternoon on-premises — a staging table, a trigger, a nightly script — has to be rebuilt out of the supported pieces, and sometimes the answer is that it cannot be built the way it was asked for. Read as a contract, it is what makes a quarterly update safe. Oracle can replace the code under you four times a year because nothing you built reaches into it. Every artefact in this course sits on a stable surface — a service, a subject area, a file interface, a published extension point — and those are the things Oracle undertakes not to break silently. The trade is real and it is the right way round: you give up reach and you get an upgrade that

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
What SaaS actually forbids, and why — Oracle Fusion Technical: Reports, Data, Integrations and Extensions — MSAMM