Oracle Apps DBA: Keeping E-Business Suite Alive · Module 9 · Users, responsibilities and access
The requests you should refuse
Lesson 97 of 184 · 2 min
Sharing a login, granting an administrative responsibility "TEMPORARILY", and resetting a password over the phone. HOW TO SAY NO USEFULLY. All three are asked in good faith by people with a real problem, which is what makes refusing them a skill rather than a policy. SHARING A LOGIN DESTROYS ATTRIBUTION, WHICH IS THE ENTIRE POINT OF HAVING ACCOUNTS. Once two people use one, no record can say which of them did anything — and that is not recoverable later. The useful refusal comes with the alternative: a second account with the same responsibilities, which takes ten minutes and gives them exactly what they wanted. THE "TEMPORARY" ADMINISTRATIVE RESPONSIBILITY IS THE ONE THAT SOUNDS MOST REASONABLE AND IS NEVER TEMPORARY. Nobody comes back to remove it. Lesson 8's third failure is exactly this, two years on — and the person who granted it has usually left. SO SAY YES WITH AN…
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