Questions on Query Masking (Doc ID 2795934.1)

Last updated on OCTOBER 22, 2024

Applies to:

Goal

1. When Query Masking is enabled why the record fields which are not listed under dataprivacy/Authorized roles are also getting masked?

2. How to figure out all the fields which are getting masked without actually defined in dataprivacy setting?

3. It looks like, to unmask the field we have to go Authorized roles and give the authorization to the field. Is there any other way to exclude the Peoplesoft delivered masked record fields from query masking? If there are more(Eg: 4000+) fields to unmask then it is quite difficult to add each and every field in dataprivacy/Authorized roles to unmask.

4. Why all fields from the record are not included in the Maintain Data Privacy Settings?(Eg: NAMES record contains the following fields only NAME, NAME_AC and NAME_DISPLAY). Do customers have to add the fields if they want other fields to unmask?

5. When add the FIRST_NAME field under Exclude Fields tab and run the Run Data Sync process, FIRST_NAME field is still getting masked. How this 'Exclude Fields' works?
Enterprise Components > Data Privacy Framework > Query Masking > Run Data Sync
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.