Oracle Apps DBA: Keeping E-Business Suite Alive · Module 9 · Users, responsibilities and access
End-dating rather than deleting
Lesson 96 of 184 · 2 min
Why a leaver is END-DATED, what still works afterwards, and THE AUDIT CONSEQUENCE OF THE ALTERNATIVE. The instinct on a leaver is to delete the account, and EBS does not really let you — which is correct rather than a limitation. THE ACCOUNT IS ATTACHED TO EVERYTHING THEY EVER DID. Every record they created or updated carries their id. Delete the user and either the history breaks or the id becomes a number that resolves to nobody — and an audit trail that cannot name who did something is not an audit trail. Module 5's reasoning about what you can and cannot remove, applied to people. SO END-DATING IS THE MECHANISM: THE ACCOUNT EXISTS, THE HISTORY RESOLVES, AND ACCESS STOPS. Sign-in is refused from that date; the record remains for as long as the data does. AND END-DATE THE RESPONSIBILITY GRANTS AS WELL AS THE ACCOUNT, because they are separate.…
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