Table of Contents
What is UWODS?
UWODS (University of Washington Operational Data Store) is the university's main database for HR, payroll, and some financial information. WDFinDataMart houses most of the University's financial data. UWODS was introduced in 2023 as part of UW Finance Transformation to replace the older ODS system. UWODS gets its data directly from Workday, UW's system for managing employees, finances, and organizational information.
Think of UWODS as a central warehouse where all the important university data is stored and organized so you can create reports and answer business questions.
What Data Can You Find in UWODS?
Employee and HR Information
- Employee details (names, IDs, contact information)
- Job information (titles, departments, supervisors)
- Salary and compensation data
- Organizational structure (who reports to whom)
Financial Information
- Cost centers and budget codes
- Gifts and funding sources
- How different financial codes relate to each other
- Reference information for financial reporting
Important Note About Payroll Data
While most HR information is in UWODS, payroll earnings and detailed payroll transactions are stored in a separate database called WDFinDataMart. If you need payroll payment details, you'll need to look there instead.
How to Connect to UWODS
Getting Access
Before you can use UWODS, you need proper access:
- If you already have access to HR or finance data in other UW systems, you likely have access to UWODS too
- If you're new to UW data systems, you'll need to request access through the "Request Access to Reports, Analytics, and Data" process
- Connection details: Use your NetID and password to connect to edwpub.s.uw.edu.
Tools You Can Use
- Excel: Connect directly to pull data into spreadsheets
- SQL Server Management Studio (SSMS): For writing queries
- Other database tools: Any tool that connects to SQL Server databases
See our guide on how to connect to the EDW for more information.
Understanding How UWODS is Organized
The "sec" Prefix Rule
This is the most important thing to remember: Always use table names that start with "sec."
-- Correct way to query UWODS
SELECT * FROM UWODS.sec.Person
-- Wrong way (this won't work)
SELECT * FROM UWODS.Person
The "sec" stands for "secured" and ensures you're accessing data through the proper security filters.
Data is Updated Nightly
UWODS gets fresh data from Workday every night, Sunday through Thursday. So, the information you see is typically from the previous business day.
Basic Query Examples
Finding Employee Information
-- Look up an employee by their Employee ID
SELECT DisplayName, EmployeeID
FROM UWODS.sec.Person
WHERE EmployeeID = '123456789'
Finding Active Employees
-- Get a list of current active employees
SELECT p.DisplayName, p.EmployeeID, es.PositionTitle
FROM UWODS.sec.Person p
JOIN UWODS.sec.EmploymentDetail es ON p.PersonKey = es.PersonKey
JOIN UWODS.sec.EmploymentStatus s ON p.PersonKey = s.PersonKey
WHERE s.EmployeeStatusCode LIKE 'A'
Understanding Financial Relationships
One of the most powerful features in UWODS is understanding how financial codes relate to each other:
-- What cost centers can be used with a specific gift?
SELECT AllowedWorktagName, AllowedWorktagIDValue
FROM UWODS.sec.vwRelatedWorktag_Allowed
WHERE RelatedWorktagIDValue = 'YOUR_GIFT_CODE'
AND WorktagTypeName = 'Cost Center'
Key Tables You'll Use Most Often
Employee Data
- sec.Person: Basic employee information (names, IDs)
- sec.Worker: Active employee records
- sec.Position: Job positions and titles
- sec.EmploymentStatus: Employment status information
- sec.EmploymentDetail: Detailed employment relationships
Organizational Data
- sec.CostCenter: Cost center information
Financial Data
- sec.Gift: Gift and funding information
- sec.vwRelatedWorktag_Default: Default relationships between financial codes
- sec.vwRelatedWorktag_Allowed: All allowed relationships between financial codes
Common Things to Watch Out For
Employee Names
UWODS has different name fields:
- DisplayName: The recommended field to use in UWODS.sec.Person
- PreferredName fields: Only shows preferred names (might be blank)
Sensitive Payroll Information
Some payroll details require special permissions. If you see blank/null values where you expect data:
- Look for alternative fields (like PayComponentGroup instead of PayComponentEarning)
- Contact your supervisor about requesting additional access
Keys and IDs Are Different from the Old System
If you used the previous ODS system, be aware that the internal ID numbers (keys) are completely different in UWODS. Don't assume an employee's "PersonKey" will be the same between systems.
What's Different from the Old ODS System
If you previously used the ODS system:
Major Changes
- Payroll and financial data now in WDFinDataMart: Payroll earnings and all financial transactions have moved to WDFinDataMart (previously in BudgetActivityDetail table in ODS)
- More detailed reference tables: Information that used to be combined is now in separate, more specific tables
- Different key values: Internal ID numbers are completely different
- Must use "sec" prefix: All queries must use secured views
Better Workday Alignment
UWODS reflects how Workday actually stores data, making it more accurate and up-to-date with UW's actual business processes.
Getting Help
When You Need Support
- Technical problems (can't connect, queries not working): Email edw-help@uw.edu with 'UWODS' in the subject line
- Questions about your data (what does this mean, how should I use this):
- Office hours: EDW experts are available every other Friday 9-10 AM for drop-in questions. Link to the meeting can be found here.
Staying Updated
Join the uwods-ft-users email list to get notifications about:
- System maintenance and downtime
- New features and changes
- Important updates about data
Tips for Success
- Start simple: Begin with basic SELECT statements on single tables
- Use the "sec" prefix: Always remember UWODS.sec.tablename
- Filter your results: Use WHERE clauses to limit results, especially on large tables
- Ask for help early: Don't struggle alone - use the support resources
- Check the documentation: Look at the Data Concepts and Sample Queries for your specific area (HR, Finance, etc.)