MSAMM
Back to course

Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 2 · Security, roles and what you are allowed to see

Data access sets and business unit security

Lesson 14 of 177 · 3 min

A data access set gates which LEDGERS a user can work in; business unit security gates which BUSINESS UNITS they can transact against. Between them they decide most of what a finance user sees. Data access sets are configured in the ledger setup and assigned through a role — so the assignment lives in two places, which is why they are easy to get half right. Business unit access is assigned per user, per business unit, and often by a role with a data role attached. Neither is visible from the page that is failing, and that is what makes this the hardest layer to diagnose from a screenshot. WHY A REPORT THAT WORKS FOR YOU RETURNS NOTHING FOR THE CLIENT. You built it as an implementation user with access to every ledger and every business unit in the environment. Your client's accountant has one ledger and two business units.

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 2 · Security, roles and what you are allowed to see

  1. 1Roles, privileges and duties
  2. 2Data security versus function security
  3. 3Data access sets and business unit security
  4. 4The security diagnostic sequenceFree preview
  5. 5Reading the security console
  6. 6Security for reporting: the part people miss
  7. 7Custom roles: when, and how to survive an update
  8. 8Provisioning and role assignment at scale
  9. 9What breaks: the three security failures you will meet
  10. 10Lab briefing · Diagnosing three access failures