Address Book Data Privacy Enhancements

I’d forgotten about these, but they are pretty cool.  It gives you the ability to hide certain aspects of the Address Book Data based upon the each type.  You can obfuscate TaxID, Addresses, Phone Numbers, emails date of both and gender information for JDE roles based upon the AN8 type.

This was 811 functionality that I had forgotten all about.  So don’t go implementing row security when this is going to do the job for you.  Better than row security!

Setting up Address Book data security involves these steps:
1. Selecting the Activate Personal Data Security constant in the Address Book Constants (P0000).
Personal data security is inactive unless the Activate Personal Data Security constant is selected.
2. Setting up permission list definitions.
Use the Address Book Data Permissions program (P01138) to create one or more permission lists that specify which fields in the Address Book are secured.
3. Setting up permission list relationships.
Use the Permission List Relationships program (P95922) to determine the users or roles that are subject to each permission list.
Once you have set up Address Book data security, keep in mind that users can still view their own address book information, and secured fields are not protected under these circumstances:
a. Adding new Address Book records.
b. Running reports that contain the secured fields.
c. Viewing records in the Universal Table Browser (UTB).

There is some good doco on https://support.oracle.com search for P01138.