Does anyone have/use a record in HCM that is populated with future-dated JOB data, but doesn't auto-join any security records?
At CU, our future-dated JOB data rows cannot be queried from the JOB record. (OK, sometimes that isn't the case, but for newly hired employees it usually is). They only become available on JOB once the current date exceeds the Effective Date of the first row. Therefore, our DBAs have created a view-record that only returns future-dated rows in JOB. When we create queries, we often include JOB on the Top Level and the view-record on Union 1 to capture all of the existing data.
The problem: both JOB and JOB_FUTR_VW auto-join to PSQuery's security record(s). That usually limits returned data to just the Dept that entered the rows. And if an employee is active in more than one Job in a different Depts concurrently (often the case at CU) none of the Depts can see each other's data.
We have another workaround view-record that includes 88 fields from the JOB record but doesn't auto-join to any security records. Great. Everybody can see everything here. But we don't have anything similar for future-dated rows in JOB. We are currently reviewing options for filling this void.
I'm curious to know about your experience. How is your system set up? Do you also have these issues? What solution(s) have you implemented?
------------------------------
Scott Frey
Connected Campus CoP Member - Senior Data Analyst-HR Info Systems
University of Colorado System
------------------------------
Message from the HEUG Marketplace:------------------------------
Find, Review, and Engage with Higher Education-focused solution providers, products, and services using the
HEUG Marketplace.
------------------------------