Skip to content

RADDataStore Reorg on July 27, 2026

RADDataStore Reorg on July 27, 2026

 

The Office of Research Information Services (ORIS) RADDB database will go through a reorganization on July 27, 2026, which will cause breaking changes in the Enterprise Data Warehouse database, RADDataStore.  These changes to the objects will be available in the EDW RADDataStore on July 28, 2026. However, data on the new objects will be available as soon as the Data Custodian submits security role definitions.  

Last Updated: 7/15/2026

Status ORIS Schema.Object EDW Object Note
Removed UW_rpt.vSPA_AwardTrends UW_rpt_vSPA_AwardTrends All 33 fields listed to be removed 
Changed Format UW.vItemComments.ItemType UW_vItemComments.ItemType nvarchar(20) to (30)
Added Fields UW.vNonAwardAgreement UW_vNonAwardAgreement
Added Fields UW.vPersonRoleItemBridge UW_vPersonRoleItemBridge
Added New Objects UW.vAA_AdminActionSubtype UW_vAA_AdminActionSubtype  
UW.vAA_Other UW_vAA_Other
UW.vAwardLineSpecialCondition UW_vAwardLineSpecialCondition
UW.vAwardSpecialConditionType UW_vAwardSpecialConditionType
UW_rpt.vAwardActivity_InProgressRequests UW_rpt_vAwardActivity_InProgressRequests
UW_rpt.vAwardTrends UW_rpt_vAwardTrends

 

More details can be found in the following ORIS RADDB changes (version 3.0)

UW Schema – Complete List of Views and Fields

 

Summer 2026 Data Center Network Refresh

This summer, UWIT will replace the end-of-support core and aggregation network infrastructure in the UW Tower and 4545 data centers. These data centers support critical services across the University, and the work is planned to be completed before the Autumn Quarter.

Why This Matters

The current data center core and aggregation network equipment is aging and due for planned lifecycle replacement.

This means:

  • No further security patches or vendor fixes
  • Increased operational and security risk over time
  • Higher likelihood of avoidable service disruption if the equipment remains in place
  • Reduced ability to maintain a reliable and resilient data center network

This refresh addresses one of our largest avoidable infrastructure risks.

Planned Timing

Work will occur during coordinated Sunday maintenance windows from mid-July until September 20th, before the start of the Autumn Quarter.

The schedule is intentionally aligned with summer break to reduce impact.

Expected Impacts

  • Core and aggregation work may briefly impact each data center, generally seconds to under a minute.
  • Each rack migration should cause a service impact of roughly 15 to 20 minutes.
  • Some customers may experience additional impact if applications are dependent on other services or systems as those are migrated.
  • UWIT is creating a Data Center Rack Migration Matrix to map available rack, customer, contact, and maintenance window information. Partner teams will be asked to verify the data, identify missing contacts, and flag special timing, validation, or dependency considerations.
  • No direct hospital or patient care impact is expected, though academic and campus services that UW Medicine relies on may be affected.
  • Our goal is to minimize disruption while completing necessary lifecycle replacement work

What We Need from Leaders and Colleagues

  • Support from senior leaders and partners will help ensure affected teams engage with UWIT during planning.
  • Please reinforce that this work is necessary to reduce risk, maintain reliability, and complete the refresh before the Autumn Quarter.
  • Because rack, subnet, and billing records are manually maintained and may not reflect current contacts, UWIT will rely on campus partner IT teams to verify the matrix.

Questions?

Please share your feedback, questions, or concerns with us via this form.

Launch of the New RADDataStore Database in EDW

 Announcement: Launch of the New RADDataStore Database in EDW

A new database, RADDataStore, has been introduced in EDW to provide Research Administration Data views.  These views are sourced from the RADDB database designed and maintained by the Office of Research Information Services (ORIS), where data from the SAGE system and related Workday datasets are integrated using Research-defined business rules and logic. 

This database is a direct copy of the ORIS RADDB data, with only minor changes to the view names.  The mapping from the ORIS RADDB to EDW RADDataStore is provided below and may be useful for campus users who are already familiar with and using the RADDB on the ORIS server.  

 

ORIS RADDB (Schema: “UW”) EDW RADDataStore
UW.vAbstract sec.UW_vAbstract
UW.vApplication sec.UW_vApplication
UW.vApplicationAwardBridge sec.UW_vApplicationAwardBridge
UW.vApplicationCountry sec.UW_vApplicationCountry
UW.vAward sec.UW_vAward
UW.vAwardAdvanceExtensionRequest sec.UW_vAwardAdvanceExtensionRequest
UW.vAwardAdvanceRequest sec.UW_vAwardAdvanceRequest
UW.vAwardLine sec.UW_vAwardLine
UW.vAwardModificationRequest sec.UW_vAwardModificationRequest
UW.vAwardModificationRequestCategory sec.UW_vAwardModificationRequestCategory
UW.vAwardRequestReturn sec.UW_vAwardRequestReturn
UW.vAwardSetupRequest sec.UW_vAwardSetupRequest
UW.vCompliance sec.UW_vCompliance
UW.vCostCenter sec.UW_vCostCenter
UW.vDate sec.UW_vDate
UW.vFundingAction sec.UW_vFundingAction
UW.vGrant sec.UW_vGrant
UW.vGrantHierarchy sec.UW_vGrantHierarchy
UW.vHold sec.UW_vHold
UW.vItemComments sec.UW_vItemComments
UW.vNonAwardAgreement sec.UW_vNonAwardAgreement
UW.vPerson sec.UW_vPerson
UW.vPersonRoleItemBridge sec.UW_vPersonRoleItemBridge
UW.vResearchRole sec.UW_vResearchRole
UW.vSAGESubrecipient sec.UW_vSAGESubrecipient
UW.vSponsor sec.UW_vSponsor
UW.vSubaward sec.UW_vSubaward
UW.vSubawardRequest sec.UW_vSubawardRequest
UW.vWDSubrecipient sec.UW_vWDSubrecipient

 

ORIS RADDB (Schema: “UW_rpt”) EDW RADDataStore
UW_rpt.vActiveConvertedAwards sec.UW_rpt_vActiveConvertedAwards
UW_rpt.vAdvancementProposal sec.UW_rpt_vAdvancementProposal
UW_rpt.vApplication sec.UW_rpt_vApplication
UW_rpt.vASRs sec.UW_rpt_vASRs
UW_rpt.vAward_OpenItems sec.UW_rpt_vAward_OpenItems
UW_rpt.vAward_PostFT sec.UW_rpt_vAward_PostFT
UW_rpt.vCurrentReturnedAwardRequests sec.UW_rpt_vCurrentReturnedAwardRequests
UW_rpt.vMODs sec.UW_rpt_vMODs
UW_rpt.vNonAwardAgreement sec.UW_rpt_vNonAwardAgreement
UW_rpt.vSPA_AwardTrends sec.UW_rpt_vSPA_AwardTrends
UW_rpt.vSubawardRequest sec.UW_rpt_vSubawardRequest
UW_rpt.vSubawardRequestDean sec.UW_rpt_vSubawardRequestDean

 

Definitions for the views and columns will be made accessible in the Knowledge Navigator soon.

 

Questions?

Please contact edw-help@uw.edu with “RADDataStore” in the subject line.

 

Improving Access to Student Emergency Contact Information

The UW collects emergency contact information to support student safety and facilitate timely communication during serious or unexpected situations. All active students are required to designate two emergency contacts, so the University may reach appropriate individuals if urgent circumstances arise, such as a significant illness, injury, or other critical event.

While the purpose of emergency contact information is clear, the process for keeping it current and making it available when needed has not always been simple. This article highlights the collaborative work across UW that helped improve that process for both students and authorized staff.

The Challenge

Until recently, maintaining and accessing emergency contact information was not always as straightforward as it needed to be. The Office of the Vice President for Student Life, the primary stakeholder for Student Emergency Contacts, found that family contact data in the Student Database was often outdated, missing, or incomplete.

Historically, students were prompted to provide this information during pre-registration, which was not always the ideal time for thoughtful review. Although updates could later be made in Student Personal Services (SPS), it was not easy for students to find where to do that. It was also not explicit that the emergency contact could be any person the student chose.

In addition, the previous system had several limitations: it allowed only one contact, did not include email addresses, did not support international phone numbers, and did not let students indicate their relationship to the contact. Because the central system could not capture all the information units needed, some offices maintained additional contact details in separate systems. In urgent situations, that made it harder for staff to quickly find the most current information.

A Collaborative Solution

Addressing this issue called for coordinated work across multiple teams to improve the student experience, strengthen data flows, support secure access, and reinforce a clearer campuswide process for maintaining emergency contact information.

  • The Office of Student Life and the Office of the University Registrar: Served as co-project sponsors. The Academic Data Domain Lead led three stakeholder summits to help define requirements, and the Office of the University Registrar’s Academic Data Management team reviewed the solution and supported communication about the change.
  • Student & Educational Technology Services (UWIT): Worked with stakeholders to translate requirements into validated design proposals for a more visible student-facing experience and a report that would meet staff needs in emergencies. Built an app students can access from their MyUW profile page to verify and update emergency contacts and updated impacted UWIT applications to use the new data source.
  • Data Integrations (UWIT): Integrated emergency contact data from the new student-facing application into the Enterprise Data Warehouse, replacing the SDB dataset, which held more limited information. The team also worked with the University Registrar to define and implement appropriate security roles.
  • Reporting & Analytics (UWIT): Built the Student Emergency Contact report in the BI Portal, providing approved stakeholders with a secure way to retrieve the information they need.

Exploring the Solutions

Student Emergency Contact App

Students can review their emergency contact information at any time through their profile page in MyUW. To launch the app and edit their information, they just need to click Edit emergency contacts from this page.

A screenshot of the Student Profile screen in MyUW. The two Emergency Contacts fields are highlighted.

 

The Student Emergency Contacts app displays the student’s current emergency contacts and allows them to edit or remove them.

A screenshot of the Emergency Contacts App.

 

When the student clicks Edit, a popup prompts them to enter the required information in the appropriate format.

A screenshot of the popup window where users can update their emergency contacts.

 

Student Emergency Contact Report – BI Portal

Approved staff are able to retrieve student emergency contact information using the Student Emergency Contact Report in the BI Portal.

A screenshot of the Student Emergency Contact Report in the BI Portal.

Accessing This Report

Emergency contact information is used only when necessary to respond to emergency situations involving a student. Access to this information is restricted to authorized University personnel and handled in accordance with University privacy standards.

If you need access, follow the special permission process outlined on the Interpretation tab for the report.

Recent Examples of Impact

  • The Emergency Contact Report has already proven essential in several student emergencies.
  • Students have benefited from a more visible and accessible way to review and update their emergency contact information each quarter, including the ability to provide more complete details.
  • The process for updating and approving access to the report prompted the teams involved to clarify standard operating procedures, decision-making, and documentation.

UWSDBDataStore Reorg on May 2, 2026

UWSDBDataStore Reorg on May 2, 2026

The student database (SDB) will go through a reorganization on May 2, 2026 which will cause changes in the Enterprise Data Warehouse database, UWSDBDataStore. These changes to the objects will be available in the UWSDBDataStore on May 4, 2026
However, data on the new objects will be available as soon as the Data Custodians submit the security role definitions and the SIS team loads the data.

Last Updated – 4.17.26

Columns to be Added

Table Column DataType
NSLDS_DATA N_LOAN_LIM_EXC_FG CHAR(1)
N_DISB_DT_FLG CHAR(1)
N_LIFETM_LOAN_TOT DECIMAL(15,0)
N_G_COMB_LIM_FLGA CHAR(1)
N_P_COMB_LIM_FLGA CHAR(1)
N_PLUS_LIMIT_FLG CHAR(1)
N_LIFETIME_MAX_FG CHAR(1)
N_AGGR_GRAD_BAL DECIMAL(15,0)
N_GRAD_CONS_BAL DECIMAL(15,0)
N_AGGR_GRAD_PEND DECIMAL(15,0)
N_AGGR_GRAD_TOT DECIMAL(15,0)
N_GRAD_CONS_TOT DECIMAL(15,0)
N_GRAD_AWARD_YR SMALLINT
N_GRAD_DEP_IND CHAR(1)
N_AGGR_PROF_BAL DECIMAL(15,0)
N_PROF_CONS_BAL DECIMAL(15,0)
N_AGGR_PROF_PEND DECIMAL(15,0)
N_AGGR_PROF_TOT DECIMAL(15,0)
N_PROF_CONS_TOT DECIMAL(15,0)
N_PROF_AWARD_YR SMALLINT
N_PROF_DEP_IND CHAR(1)
N_GRAD_LN_LIM_FLG CHAR(1)
N_PROF_LN_LIM_FLG CHAR(1)
N_AGGR_STD_PL_FLG CHAR(1)
N_UG_AGGR_SUB_OPB DECIMAL(15,0)
N_UG_AGGR_UNS_OPB DECIMAL(15,0)
N_UG_AGGR_COM_OPB DECIMAL(15,0)
N_UG_AGGR_CON_OPB DECIMAL(15,0)
N_UG_AGGR_SUB_TOT DECIMAL(15,0)
N_UG_AGGR_UNS_TOT DECIMAL(15,0)
N_UG_AGGR_COM_TOT DECIMAL(15,0)
N_UG_AGGR_CON_TOT DECIMAL(15,0)
N_UG_AWARD_YR SMALLINT
N_UGRAD_DEP_IND CHAR(1)
N_PO_GP_SUB_OPB DECIMAL(15,0)
N_PO_GP_UNS_OPB DECIMAL(15,0)
N_PO_GP_COMB_BAL DECIMAL(15,0)
N_PO_GP_CONS_BAL DECIMAL(15,0)
N_PO_GP_AG_S_TOT DECIMAL(15,0)
N_PO_GP_AG_US_TOT DECIMAL(15,0)
N_PO_GP_AG_CN_TOT DECIMAL(15,0)
N_PO_GP_AG_UN_TOT DECIMAL(15,0)
N_PO_GP_AWARD_YR SMALLINT
N_PO_GP_DEP_IND CHAR(1)
N_LOAN_LIM_EXC_CH CHAR(1)
SA_ACCOUNT_INSURANCE_DATA INSUR_TYPE CHAR(1)
SA_TRANSACTION ECSI_PROCESS_IND CHAR(1)
ECSI_PROCESS_DT DATETIME
SF_EVALUATION** ENROLL_WORK_FORCE CHAR(1)
SF_EVALUATION1 UW_UNMET_NEED_NIL INT
ISIR_VERSION_FLAG CHAR(1)
SF_FEES SFF_MAJOR CHAR(6)
SFF_FULL_FEE_AMT INT
SF_HISTORY OVRD_LOAN_LIM_EXC CHAR(1)
LOAN_LIMIT_EXC_DT DATETIME
STUDENT_1 REGID CHAR(16)

Data Type Changes

Table Column Data Type (Old) Data Type (New)
NSLDS_DATA N_AGGR_SUB_BAL INT DECIMAL(15,0)
N_AGGR_USUB_BAL INT DECIMAL(15,0)
N_AGGR_COMB_BAL INT DECIMAL(15,0)
N_AGGR_CONS_BAL INT DECIMAL(15,0)
N_AGGR_TEACH_BAL INT DECIMAL(15,0)
N_SUB_PEND_DISB INT DECIMAL(15,0)
N_USUB_PEND_DISB INT DECIMAL(15,0)
N_COMB_PEND_DISB INT DECIMAL(15,0)
N_AGGR_SUB_TOT INT DECIMAL(15,0)
N_AGGR_USUB_TOT INT DECIMAL(15,0)
N_AGGR_COMB_TOT INT DECIMAL(15,0)
N_AGGR_CONS_TOT INT DECIMAL(15,0)
N_TEACH_LN_TOT INT DECIMAL(15,0)
N_PERK_DISB_AMT INT DECIMAL(15,0)
N_PERK_CURRYR_AMT INT DECIMAL(15,0)
N_AGGR_TCH_UDISB INT DECIMAL(15,0)
N_AGGR_TCH_GDISB INT DECIMAL(15,0)
N_SPARE7 INT DECIMAL(15,0)
N_SPARE8 INT DECIMAL(15,0)
N_SPARE9 INT DECIMAL(15,0)
N_SPARE_10 INT DECIMAL(15,0)
N_SPARE_11 INT DECIMAL(15,0)
N_SPARE_12 INT DECIMAL(15,0)
NSLDS_DATA_PELL_DATA N_PELL_SCHED_AMT INT DECIMAL(15,0)
N_PELL_PD_TO_DT INT DECIMAL(15,0)
N_PELL_AWARD_AMT INT DECIMAL(15,0)
NSLDS_DATA_TEACH_DATA N_TEACH_SCHED_AMT INT DECIMAL(15,0)
N_TEACH_PD_TO_DT INT DECIMAL(15,0)
N_TEACH_AWARD_AMT INT DECIMAL(15,0)
N_TEACH_SCHOOL_YR TINYINT SMALLINT
NSLDS_DATA_LN_DATA N_LN_OUT_BAL INT DECIMAL(15,0)
N_LN_LST_DISB_AMT INT DECIMAL(15,0)
SA_ACCOUNT_INSURANCE_DATA INSUR_SPARE_1 CHAR(6) CHAR(12)

 

Table Key Changes

Table Old Primary Key New Primary Key
SF_FEES SFF_YEAR_CODE
SFF_TERM
SFF_CAMPUS
SFF_CLASS
SFF_CREDIT_HOURS
SFF_YEAR_CODE
SFF_TERM
SFF_CAMPUS
SFF_CLASS
SFF_MAJOR* (new PK field)
SFF_CREDIT_HOURS

 

New Table – SF_COD_DATA

Table Column DataType Primary Key
SF_COD_DATA SYSTEM_KEY INT Y
COD_YEAR SMALLINT Y
LOAN_ANNUAL_CRDS DECIMAL(5,1)
LOAN_ANNUAL_PRCNT SMALLINT
LOAN_ANNUAL_FT_CR TINYINT
LOAN_GRADE_LEVEL TINYINT
LOAN_INST_LIMIT CHAR(1)
LOAN_LIMIT_EXP CHAR(1)
PROG_ATND_BEG_DT DATETIME
PROG_PUB_LNGTH DECIMAL(6,3)
PROG_REM_LNGTH DECIMAL(6,3)
WRK_FRC_PELL_ELIG CHAR(1)
WRK_FRC_PELL_FEES INT
ENRL_INT_S_SUM SMALLINT
ENRL_INT_S_AUT SMALLINT
ENRL_INT_S_WIN SMALLINT
ENRL_INT_S_SPR SMALLINT
ENRL_INT_U_SUM SMALLINT
ENRL_INT_U_AUT SMALLINT
ENRL_INT_U_WIN SMALLINT
ENRL_INT_U_SPR SMALLINT
ENRL_INT_G_SUM SMALLINT
ENRL_INT_G_AUT SMALLINT
ENRL_INT_G_WIN SMALLINT
ENRL_INT_G_SPR SMALLINT
ENRL_INT_P_SUM SMALLINT
ENRL_INT_P_AUT SMALLINT
ENRL_INT_P_WIN SMALLINT
ENRL_INT_P_SPR SMALLINT
ENRL_STS_S_SUM DECIMAL(3,1)
ENRL_STS_S_AUT DECIMAL(3,1)
ENRL_STS_S_WIN DECIMAL(3,1)
ENRL_STS_S_SPR DECIMAL(3,1)
ENRL_STS_U_SUM DECIMAL(3,1)
ENRL_STS_U_AUT DECIMAL(3,1)
ENRL_STS_U_WIN DECIMAL(3,1)
ENRL_STS_U_SPR DECIMAL(3,1)
ENRL_STS_G_SUM DECIMAL(3,1)
ENRL_STS_G_AUT DECIMAL(3,1)
ENRL_STS_G_WIN DECIMAL(3,1)
ENRL_STS_G_SPR DECIMAL(3,1)
ENRL_STS_P_SUM DECIMAL(3,1)
ENRL_STS_P_AUT DECIMAL(3,1)
ENRL_STS_P_WIN DECIMAL(3,1)
ENRL_STS_P_SPR DECIMAL(3,1)

Table Removal – Empty & No Usage

Table
SR_DEC_RESULTS

Due to the field add in SF_Evaluation the following field will move to SF_Evaluation1

FOREIGN_STUDY_AMT

New Workday Reports Enhance Grant Visibility and Financial Insights

Six new Workday reports are now available to support grant reporting and financial analysis for research deans, academic and administrative leaders, and department managers. Together, these reports provide leaders in research colleges and schools with a high-level view of sponsored program activity that was not previously available.

Developed by DATAGroup as part of the Awards Improvement and Development Effort (AIDE), these reports reflect strong cross-campus collaboration, with key contributions from finance and data leaders in the Office of Research, Office of Research Information Services (ORIS), and School of Medicine, as well as project support from UWIT. This work advances AIDE’s goal to enhance reporting capabilities for the UW research community.

A More Powerful Way to View Grant Data

Delivered as a suite, these reports provide multiple ways to explore and analyze grant administration data, making it easier to track budgets, expenses, and trends.

What’s New

  • Sponsor Hierarchy for Federal Funding – View summarized financial data at each level of the Federal sponsor hierarchy, which enables meaningful rollups and analysis of funding patterns. Example: Federal Sponsors → Department of Health and Human Services (DHHS) → National Institutes of Health (NIH) → National Cancer Institute.
  • Direct and Indirect Costs by Object Class – Analyze spending by object class or drill down into direct costs to see each category’s contribution to total expenses.
  • Year-Over-Year Comparisons – Compare awarded budgets vs. actuals over time by sponsor type or object class, with flexible date ranges.
  • Awarded Budgets vs. Actuals Summaries – View by PI, award contract owner, or sponsor type.
  • Robust Report Prompts – Use prompts to refine results. For more details, refer to the Workday Report Prompt Glossary.

Report Highlights

Learn more about each report below!

Tip: Need some help with Workday reporting basics before exploring these reports? Check out these resources:

R1211 – Year Over Year Direct and Indirect Expenditures by Sponsor Type

A screenshot of the R1211 report. The "Federal Sponsors" category is highlighted.

A screenshot of the R1211 report. The National Institutes of Health sponsor category is highlighted.

Use this report to:

  • Track year-over-year trends for direct, indirect, and total costs by Federal and non-Federal sponsors.
  • Compare financial allocations across sponsor types.
  • Assess potential impacts of changes to Facilities & Administration (F&A) rates on Federal awards.
  • View how Federal funding is distributed across primary sponsors and their associated agencies.
  • Analyze funding trends by each sponsor within NIH.

Access this report in Workday: Year Over Year Direct and Indirect Expenditures by Sponsor Type R1211.

R1212 – Year Over Year Expenditures by Object Class

A screenshot of the R1212 report. The "Direct Expenditures" category is highlighted in the "Object Classes" column.

Use this report to:

  • Compare year-over-year trends of indirect costs to direct costs by object class.
  • Analyze the percentage breakdown of direct costs by object class relative to total costs, across multiple years.

Access this report in Workday: Year Over Year Expenditures by Object Class R1212.

R1215 – Life to Date Award Budget to Actuals by Principal Investigator

A screenshot of the R1215 report.

Use this report to:

  • Review a high-level summary of financial activity by Principal Investigator and their research contributions.
  • Drill down to view details by individual grant.

Access this report in Workday: Life to Date Award Budget to Actuals by Principal Investigator R1215.

R1215.1 – Life to Date Award Budget to Actuals by Contract Owner

A screenshot of the R1215.1 report.

Use this report to:

  • Review a high-level summary of financial activity by the award contract owner and their individual research contributions.
  • Drill down to view details by individual award or grant.

Access this report in Workday: Life to Date Award Budget to Actuals by Contract Owner R1215.1.

R1216 – Life to Date Award Budget to Actuals by Top Level Sponsor

A screenshot of the R1216 report with two views. In one view, the "Federal Sponsors" category is highlighted. In the other view, the "Non-Federal Sponsors" category is highlighted.

Use this report to:

  • Review a high-level summary of budgets to actuals and remaining balances by Federal and non-Federal sponsors.
  • Track spending to date and current balances for Federal and non-Federal sponsors.
  • Drill down to view financial allocations by Federal Primary Sponsors and their associated agencies (for example, DHHS → NIH → National Cancer Institute).

Access this report in Workday: Life to Date Award Budget to Actuals Top Level Sponsor R1216.

R1217 – Award Lines by Lifecycle Status

A screenshot of the R1217 report.

Use this report to:

  • Review a high-level summary of award-line funding by lifecycle status.
  • Understand where funds are within the award lifecycle to identify potential issues in the administrative process.

Access this report in Workday: Award Lines by Lifecycle Status R1217.

Learn More

You can also learn more about these new reports at two upcoming events:

Monthly Research Administration Meeting (MRAM) – A Subject Matter Expert (SME) will provide a brief overview of the report suite and highlight key features and use cases.

Reporting & Analytics Office Hours – A SME will demo each report and answer questions.

 

Upcoming EDW Data Updates Related to Procurement Roll Forward (PRF) Journal Cleanup

WHAT: Duplicate Roll Forward Encumbrance journals were inadvertently created and will need to be deleted. 

WHO: Customers extracting EDW data into downstream systems, please note you may need to remove these journals on your end. 

WHEN: Fix will be seen in EDW on 3/17, cleanup can be asynchronous 

Hello EDW Users, 

We want to inform you about upcoming changes to EDW data related to cleanup duplicate Procurement Encumbrance Roll Forward (PRF) journals within Workday. The University Controller’s Office (UCO) and Financial Accounting & Management (FAM) are canceling certain encumbrance journals in Workday to resolve issues where duplicate Roll Forward Encumbrance journals were inadvertently created. 

This update will affect only encumbrance journals, also known as the Obligation Roll Forward journal source in the Encumbrance Ledger. Approximately half of the affected journals are from FY25 and half from FY26. A similar cleanup process was performed at the close of FY24. 

Customers extracting EDW data into downstream systems, please note you may need to remove these journals on your end. This action can be performed independently at any time and does not require coordination with the Workday or EDW updates. 

 What’s Happening in Workday

UCO and FAM are: 

  • Unposting and then canceling a set of duplicate PRF journals. 
  • This cleanup will result in Workday containing some journals as posted even though they are canceled. 
  • This behavior is expected as part of correction effort. 

What This Means for EDW

To ensure that EDW remains consistent and accurate: 

  1. Removal of Impacted Journal Lines 

EDW will: 

  • Delete all journal lines and journal objects for the set of affected journal WIDs provided by UCO/FAM. 
  • All deleted journal lines and objects will be added to the EDW Delete Audit table for downstream traceability. 
  1. Cleanup of Related References

Some posted journals contain Reverses or ReversedBy references pointing to the journals being removed.
EDW will: 

  • Remove invalid references in these columns where the linked journal is deleted. 

This cleanup affects: 

  • ~25,000 Procurement Journals 
  • ~73,000 Journal Lines 
  1. Data Sync Expectations

As a reminder: 

  • EDW may temporarily be asynchronous from Workday during this cleanup. 
  • This behavior is consistent with similar cleanup efforts performed after FY24 closing. 

Timeline

  • 3/9 – Fix executed and published in EDW TEST 
  • 3/12 – Workday production cleanup 
  • 3/16 – EDW will perform the production journal cleanup 
  • 3/17 – Cleaned data published in customer-facing EDW environments 

An example of what will happen: 

  • Journal A: FY25 journal (reversed by B) – not duplicated 
  • Journal B: Roll Forward (reverses A) – duplicate will be deleted 
  • Journal C: Roll Forward – duplicate will be deleted 
  • Journal D: Cancel PO (reverses B) – not duplicated, this is a normal process to clear encumbrance roll forward balance when PO is cancelled 
  • Journal E: Fix task cancel (cancels B) – duplicate will be deleted 

Questions or Support 

If you have questions about the upcoming changes or notice unexpected behaviors in your EDW reports, please reach out to the EDW Team via edw-help@uw.edu. 

Thank you for your patience as we ensure the accuracy and consistency of financial data across our systems. 

Enterprise Data Warehouse (EDW) Team 

EDW Breaking Changes March 11, 2026

EDW Breaking Changes March 11, 2026

Summary of changes, details to follow below.

JIRA Database Table Notes
EDW-25564 UWODS sec.EmploymentStatus Logic change, existing logic avaialble in new table sec.EmploymentStatusWorkerType
EDW-25654 UWODS sec.CustomerRefund Column Removals
EDW-25590 SpaceDataStore sec.BuildingInteriorSpace Data type changes
sec.EmployeeInSeat
sec.FunctionalUse
sec.PIsToRooms
sec.SharedSpace
sec.SpaceWorktag

EmploymentStatus Logic Change – EDW-25564

A new table UWODS.sec.EmploymentStatusWorkerType has been created to replace the existing UWODS.sec.EmploymentStatus. The table currently named UWODS.sec.EmploymentStatus can show multiple statuses for the same person when they have worked under multiple worker types. The new table name better respresents this behavior and avoids confusion.

Table Notes
sec.EmploymentStatusWorkerType New table (already available), replacing existing sec.EmploymentStatus.
sec.EmploymentStatus Existing table, no change to column structure. Going forward will return one record instead of multiple when cases of multiple statuses for the same person.

If you are in need of multiple statuses for the same person – please migrate from UWODS.sec.EmploymentStatus to UWODS.sec.EmploymentStatusWorkerType

CustomerRefund Column Removals – EDW-25654

Table Column Notes
sec.CustomerRefund RefundStatusKey Replace with RefundStatus_DocumentStatusKey
RefundStatusWID Replace with RefundStatus_DocumentStatusWID

SpaceDataStore Data Type Change Details – EDW-25590

Table Column Existing Data Type New Data Type
sec.BuildingInteriorSpace Usable No data type change, currently showing sq ft. Will change back to Yes/No
Assignable
sec.SharedSpace BuildingKey varchar(max) nvarchar(50)
FloorKey varchar(max) nvarchar(50)
SpaceID varchar(max) nvarchar(50)
ShortName varchar(max) nvarchar(25)
AllocationAssignmentKey varchar(max) nvarchar(50)
RoomPercent varchar(max) numeric(10,2)
sec.EmployeeInSeat EmployeeID varchar(max) nvarchar(9)
PrimaryRoom varchar(max) boolean
BuildingKey varchar(max) nvarchar(50)
FloorKey varchar(max) nvarchar(50)
SpaceID varchar(max) nvarchar(50)
ShortName varchar(max) nvarchar(25)
sec.FunctionalUse FunctionalUse varchar(max) nvarchar(6)
RoomPercent varchar(max) numeric(10,2)
AllocationAssignmentKey varchar(max) nvarchar(50)
BuildingKey varchar(max) nvarchar(50)
FloorKey varchar(max) nvarchar(50)
SpaceID varchar(max) nvarchar(50)
ShortName varchar(max) nvarchar(25)
sec.PIsToRooms EmployeeID varchar(max) nvarchar(9)
PIPercent varchar(max) numeric(10,2)
BuildingKey varchar(max) nvarchar(50)
AllocationAssignmentKey varchar(max) nvarchar(50)
FloorKey varchar(max) nvarchar(50)
SpaceID varchar(max) nvarchar(50)
ShortName varchar(max) nvarchar(25)
sec.SpaceWorktag WorktagID varchar(max) nvarchar(10)
WorktagName varchar(max) nvarchar(255)
WorktagPurpose varchar(max) nvarchar(100)
CostCenter varchar(max) nvarchar(10)
EmployeeID varchar(max) nvarchar(9)
AllocationAssignmentKey varchar(max) nvarchar(50)
PrimaryRoom varchar(max) boolean
BuildingKey varchar(max) nvarchar(50)
FloorKey varchar(max) nvarchar(50)
SpaceID varchar(max) nvarchar(50)
ShortName varchar(max) nvarchar(25)

UWSDBDataStore Reorg on January 31, 2026

UWSDBDataStore Reorg on January 31, 2026

The student database (SDB) will go through a reorganization on January 31, 2026 which will cause changes in the Enterprise Data Warehouse database, UWSDBDataStore. These changes to the objects will be available in the UWSDBDataStore on February 2, 2026
However, data on the new objects will be available as soon as the Data Custodians submit the security role definitions and the SIS team loads the data.

Last Updated – 1.29.26

Columns to be Added

Table Column DataType
SF_EVALUATION** STD_ISIR_EMAIL char(50)
STUDENT_1 EO_MODCAMP_ID char(8)
EO_MODCAMP_DT datetime
STUDENT_2_CERTIFICATE_INFO CERTIF_YR smallint
CERTIF_QTR tinyint
CERTIF_BRANCH tinyint
CERTIF_MAJOR_ABBR char(6)
CERTIF_PATHWAY tinyint
CERTIF_LEVEL tinyint
CERTIF_TYPE tinyint

Columns to be Removed

Table Column
SR_DEC_RESULTS SR_DEC_NAME
SR_DEC_DOB
SR_DEC_SSN
SR_DEC_SPARE_1
SR_DEC_SPARE_2
SR_DEC_SPARE_3
SR_DEC_SPARE_4
SR_DEC_SPARE_5
SR_DEC_SPARE_6
SR_DEC_BOOLEAN_1
SR_DEC_BOOLEAN_2
SR_DEC_BOOLEAN_3
SR_DEC_BOOLEAN_4
SR_DEC_BOOLEAN_5
SR_DEC_BOOLEAN_6
SR_DEC_BOOLEAN_7
SR_DEC_BOOLEAN_8

Change to Primary Key

Table New PK Column
SF_FEES SFF_TERM

**Moving from SF_Evaluation to SF_Evaluation1 due to the column addition:
HEAL_LOAN_FLG

Discovering New Academic Possibilities with DawgPath’s Topically Similar Majors Feature

Since 2021, DawgPath has been a key tool for improving a Husky’s academic journey. Now, a new feature—Topically Similar Majors—makes it even easier for UW students to explore programs that share common themes, topics, and subject matter.

Whether a student is facing capacity-constrained major admissions, rethinking their academic interests, or still deciding on a direction, this tool offers a curated list of majors that align with a student’s interests. It’s designed to spark new ideas, highlight alternative pathways, and support informed decision-making.

Advisers across all three UW campuses can also use this feature to guide students toward programs that fit their aspirations. With Topically Similar Majors, DawgPath continues its mission to support every Husky in discovering relevant, rewarding academic options.

Note: The Topically Similar Majors project was sponsored in part by a grant from the Student Tech Fee Committee.

Below is a screenshot that shows majors that are similar to Biology, filtered by admission type.

A screenshot of the DawgPath application that shows majors that are similar to Biology, filtered by admission type.

How does it work?

DawgPath uses advanced language-based semantic modeling to uncover meaningful connections between academic programs by analyzing multiple data sources. The dataset includes comprehensive textual information for each major offered across UW campuses—such as degree titles, credential codes, program and option descriptions, and course details. Each major is represented by a unified document that also incorporates enrollment-restricted courses and the top 50 frequently taken courses by students in that major and option.

Note: Suggested majors are presented as exploratory samples rather than ranked recommendations and should be considered alongside personal goals and guidance from academic advisers.

For more information, refer to DawgPath Overview.

Cross-unit collaboration

This project leveraged expertise across the Data & Applications division of UW-IT, including Data Scientists and Engineers from Reporting and Analytics, Application Engineers and a Service Manager from Student Educational Technology Services, and User Experience Designers from Coordination & Design.

How to access

Anyone with a NetID, including graduates and applicants, can access DawgPath at https://dawgpath.uw.edu/.

Questions

If you have any questions or ideas for similar DawgPath features, please contact help@uw.edu with “DawgPath” in the subject line.