MSAMM
Back to course

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

Where each kind of request belongs

Lesson 7 of 177 · 2 min

A decision table for the requests you will actually receive. Four sentences, four modules. "We need a report." Ask one question back: does somebody need to LOOK at it, or does something need to RECEIVE it? Looking is OTBI (Module 5). Receiving — a PDF a supplier gets, a file another system reads, anything with a fixed layout — is BI Publisher (Module 4). Getting this wrong is recoverable and expensive, which is why Module 3 spends a whole module on it. "We need this field." Almost always a flexfield or an Application Composer extension (Modules 12 and 13), and almost always a design conversation first: a field with no reporting, no validation and no owner is a text box people fill in three different ways. "We need it in the other system." Real time or batch? Real time is REST or SOAP (Module 10). Batch is an extract plus

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