New bargaining unit code coming to RPTP tables
The Latest:
With the implementation of the Bargaining Unit code in Banner, a few views in RPTP are being updated to include the value. If you are a user of REPORTS.ACTIVE_ASSIGNMENTS or REPORTS.N_ACTIVE_JOBS, be aware that this field will be added on September 1st, 2026.
Why it Matters:
Identifying an employee's Bargaining Unit previously required custom logic to pull, meaning reports and processes built on these views may have handled it in different ways across departments. Adding the field directly to the views gives everyone a single, consistent source for this value going forward. Anyone with reports, queries, or processes pulling from these views should plan to review them ahead of September 1st.
The Details:
Once implemented, the new field will be available on both REPORTS.ACTIVE_ASSIGNMENTS and REPORTS.N_ACTIVE_JOBS. HR is providing custom SQL to those who would like to update their processes before the implementation date. Translation from these codes to plain language can be done using the PTVBARG table.
Go Deeper:
- Contact the UA-HR-Data team (ua-hr-data@alaska.edu) for questions about the new field and its use.
- REPORTS.N_ACTIVE_JOBS SQL:
- REPORTS.ACTIVE_ASSIGNMENTS SQL:
The Bottom Line:
If you build reports off REPORTS.ACTIVE_ASSIGNMENTS or REPORTS.N_ACTIVE_JOBS, take a look at your processes before September 1st and ensure they're ready for the transition.
Published in UA News 8/10/2026