MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 9 · Users, responsibilities and access

Operating units and access

Lesson 95 of 184 · 2 min

The DATA half of the question, which is where the answer usually is WHEN THE FUNCTION IS VISIBLE AND THE DATA IS EMPTY. Lesson 2 answers "why can I not see the screen". This answers the different and commoner complaint: the screen opens perfectly and shows nothing. THE OPERATING UNIT IS THE ORGANISATIONAL BOUNDARY THAT DECIDES WHICH DATA A RESPONSIBILITY SEES. An estate is divided into them — by company, by country, by business — and a responsibility is scoped to one or several. So two people with the identical responsibility name can see completely different data, and that is the design rather than a fault. WHICH MEANS "THE SCREEN IS EMPTY" IS ALMOST NEVER A PERMISSIONS PROBLEM IN THE SENSE PEOPLE MEAN. The function is granted — that is why the screen opened. The data is out of scope. AND THAT DISTINCTION IS THE WHOLE VALUE OF THIS LESSON,

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, 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 9 · Users, responsibilities and access

  1. 1Users, responsibilities and menus
  2. 2Why a user cannot see a function
  3. 3Operating units and access
  4. 4End-dating rather than deleting
  5. 5The requests you should refuse
  6. 6Password policy, and what it is worth
  7. 7Single sign-on, briefly
  8. 8What breaks: three access failures
  9. 9Lab briefing · Diagnose four access complaints
Operating units and access — Oracle Apps DBA: Keeping E-Business Suite Alive — MSAMM