MSAMM
Back to course

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

Release trains and what they mean for you

Lesson 8 of 177 · 2 min

Quarterly updates arrive whether you are ready or not. You get a window, not a veto: the date is set, the test environment is updated first, and production follows on a published schedule. There is no "we will skip this one". What changes: new features, changed screens, occasionally a changed default, and periodically the retirement of something Oracle told you two years ago it would retire. What does not change: your data, your configuration, and the shape of the supported interfaces. WHICH OF YOUR ARTEFACTS ARE EXPOSED IS NOT THE ANSWER MOST PEOPLE EXPECT. The instinct is that extensions are the fragile ones, because they feel like customisation. They are usually the safest thing you own — a flexfield and an Application Composer field sit on published extension points and are carried forward deliberately. The exposed ones are your REPORTS. A BI Publisher data model reads a specific set of

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