EPC/E-QR: Query Manager - When Query Masking Masks Is Enabled, When Large Number of Fields Are Selected, Query Masking Is Incorrectly Masking a Different Field. For Example, SEQUENCE Field Is Getting Masked Instead of CUST_ID Field on PS_PROJ_RESOURCE.
(Doc ID 3061545.1)
Last updated on DECEMBER 23, 2024
Applies to:
PeopleSoft Enterprise FIN Project Costing - Version 9.2 to 9.2 [Release 9]PeopleSoft Enterprise PT PeopleTools - Version 8.60 and later
Information in this document applies to any platform.
Symptoms
With query masking is enabled, if you create a query with a larger number of fields selected, sometimes the wrong fields will end up getting masked. For example, CUST_ID field on PROJ_RESOURCE table. Instead of CUST_ID field on the PROJ_RESOURCE being masked SEQUENCE field got masked. This is incorrect.
Replication steps:
- Main Menu > Enterprise components > Data Privacy Framework > Query Masking > Query Masking System Setting. Enable Query Masking turned on and save.
- Main Menu > Enterprise components > Data Privacy Framework > Maintain Data Privacy Settings. Search for PROJ_RESOURCE record and make sure CUSTID is part of the settings.
- Main Menu > Enterprise components > Data Privacy Framework > Run Query Masking Data Sync. Use Refresh Type as " Full" and run the process.
- Go to Process Monitor and make sure that the process EODP_QRYMSK ran to success.
- Main Menu > Reporting Tools > Query > Query Manager. Create a new query with PROJ_RESOURCE as record and all fields checked and run. Notice that the Sequence ID is masked as *** but Customer. (CUST_ID) has data in it. This behavior is incorrect.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |