Oracle Apps DBA: Keeping E-Business Suite Alive · Module 9 · Users, responsibilities and access
What breaks: three access failures
Lesson 100 of 184 · 3 min
A leaver who STILL HAD ACCESS THREE MONTHS ON, a SHARED ACCOUNT NOBODY COULD ATTRIBUTE, and a responsibility GRANTED FOR ONE DAY TWO YEARS AGO. THE LEAVER WITH ACCESS IS THE ONE AN AUDITOR FINDS AND IT IS ALWAYS A PROCESS FAILURE RATHER THAN A TECHNICAL ONE. HR knew, the manager knew, and nobody told the person who administers EBS. The account was never end-dated because the request never arrived. WHICH MEANS THE FIX IS NOT IN THIS SYSTEM. Either leaver notification becomes a process that reaches you reliably, or you run a periodic reconciliation against the current staff list — and the second is the one within your control, which is why it is the one that actually happens. THE SHARED ACCOUNT NOBODY COULD ATTRIBUTE IS DISCOVERED DURING AN INVESTIGATION, WHICH IS THE WORST POSSIBLE MOMENT. Something was changed, the record names an account, and three people used it.…
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