Oracle Apps DBA: Keeping E-Business Suite Alive · Module 16 · Environments: what test must not have
Masking, and its limits
Lesson 164 of 184 · 3 min
What CAN be masked, what CANNOT without breaking the test, and THE HONEST TRADE between realism and exposure. Masking replaces sensitive values with plausible substitutes, and it is the answer to Lesson 2's third item — with limits worth stating rather than glossing. WHAT MASKS EASILY IS ANYTHING NOBODY CALCULATES WITH. Names, addresses, contact details, national identifiers, bank account numbers. Replace them with realistic-looking generated values and every test still works, because nothing depends on the actual characters. WHAT IS HARDER IS ANYTHING PARTICIPATING IN ARITHMETIC OR IN A RELATIONSHIP. Salaries feed payroll calculations, so masked values must still produce plausible results — and a random substitution produces a payroll run nobody can sanity-check. And the same value appearing in several tables has to be masked consistently, or the data no longer joins and half the application stops working. AND WHAT CANNOT BE MASKED WITHOUT BREAKING THE TEST IS THE…
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.