In PeopleSoft for the Oracle DBA (Ch11, p309) I commented on how PS/Query will automatically add effective date criteria to and EFFDT column, even if it is not a key column.
PS/Query does warn you that it has added the criteria, but it won't warn that the column is not a key column
If EFFDT is not part of the key, then it is unlikely that you will need this processing. It is unlikely to change the result of the query, and it incurs additional work.
Below is an example of the code added to a query by this one criteria. The effective date sub-query will be correlated by the key columns prior to the EFFDT column. If EFFDT is not part of the key, then all the key columns will be used for the correlation conditions. There is only one row for each EMPLID and EMPL_RCD, and the effective date sub-queries will find and return that row, and the result set will remain the same.
But how prevalent is this problem? Like most things in PeopleSoft, Queries are stored in the PeopleTools tables. And it is possible to construct a query to identify queries with effective date criteria on EFFDT columns that are not part of the key on their record.
On my HR demo database the following delivered queries have effective date criteria on EFFDT columns that are no key columns.
Now, it is possible to review these queries and manually remove the effective date processing if that is appropriate.