Oracle Apps DBA: Keeping E-Business Suite Alive · Module 9 · Users, responsibilities and access
Users, responsibilities and menus
Lesson 93 of 184 · 2 min
The model in one lesson: HOW ACCESS IS ASSEMBLED, and where to look when it is wrong. Access in EBS is built in layers, and every access problem in this module is a question about which layer failed. A USER IS A PERSON'S LOGIN AND IT CARRIES ALMOST NO ACCESS BY ITSELF. It exists, it can sign in, and on its own it can do nothing — which is why "I created the account and they still cannot work" is an ordinary state rather than a fault. A RESPONSIBILITY IS THE UNIT OF ACCESS AND IT IS WHAT IS ACTUALLY GRANTED. It names what somebody can do and, crucially, WHICH DATA they do it to. A user is granted responsibilities; each is a role in one part of the business, and a person doing two jobs holds two. A MENU HANGS OFF THE RESPONSIBILITY AND DECIDES WHAT APPEARS. Functions and…
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.
In this module: Module 9 · Users, responsibilities and access
- 1Users, responsibilities and menus
- 2Why a user cannot see a function
- 3Operating units and access
- 4End-dating rather than deleting
- 5The requests you should refuse
- 6Password policy, and what it is worth
- 7Single sign-on, briefly
- 8What breaks: three access failures
- 9Lab briefing · Diagnose four access complaints