Skip to content

SpaceWS Release: Support for the new Space Inventory Management System

On March 31, 2021 the source system for Space Web Services (SpaceWS) successfully migrated to a new Space inventory Management System (Invision).

In order to support this migration, the Enterprise Web Services team has released an update to SpaceWS which has resulted in some fields changes.

The complete list of field changes are available on our Wiki at https://wiki.cac.washington.edu/display/EBWS/SpaceWS+v1+Source+Change

Support:

If you would like to learn more about the new Space Inventory Management System, please visit https://facilities.uw.edu/catalog/space-manager or contact uwftech@uw.edu.

For SpaceWS service related questions, please reach out to us at spacews-support@uw.edu

 

RPG Release: Filter Bug Fix on UG Transcript Course Search by Major

The Report Prioritization Group (RPG) just released a bug fix on the BI Portal report Undergraduate Transcript Course Search by Major

In this news story we provide a summary of the change. If you have any questions, please don’t hesitate to write help@uw.edu and put “BI Portal Report Question: UG Transcript Course Search by Major” in the subject line.

Change Summary:

The report was not working correctly when a user selected more than one course from the Course Number filter. Even if a user selected multiple courses, the report only ran for 1 course. This issue is now resolved!

By design, the Course Number filter is multi-select. We built it this way so that you can choose multiple courses if a program-required course is offered jointly with other courses as part of a Joint Course Loop.

 

A joint course loop is a set of sections or courses that are all offered jointly together. Joint course loops occur in both the curriculum data and in the Time Schedule.

 

In this way, the report allows advisers to look at “their majors” and see if they have taken a program-required course, even if that course is part of a loop. To be clear though, the report does not do the “loop logic” for the user. Instead, it is up to the user to know which courses are part of a loop and select them from the Course Number filter.

For Example:

In this example, I am an adviser for Marine Biology Majors (0-MARBIO-00-1-5). I want to know which of my students have taken the program-required course BIOL 250.

I first choose a quarter and Marine Biology majors using the filter selections in Green in the image above.

Next, I choose all the courses in the joint loop. I know that BIOL 250 is jointly offered with FISH 250 and OCEAN 250. In this case, the courses are not only offered from 3 different departments (i.e. Biology, School of Aquatic and Fishery Sciences, and School of Oceanography), but those departments are even in different Colleges (i.e. Arts & Sciences and Environment). Again, the report does not have clever logic to search and find all courses in a loop. It is up to you to know where these courses sit in the SDB organization hierarchy.

Finally, I choose Course Taken Indicator Yes, No, and Registered.

The report’s result set shows me that for students that are “my majors” as of Spring 2021, which ones have taken one of the three courses in the loop that meet the Marine Biology program requirements based on the Crs Taken Indicator Column.

Questions?

We published the first version of this report in May 2020. For more details on the release of this report, please read this news story in IT Connect: RPG New Report Release: Undergraduate Transcript Course Search by Major

This report references important institutional concepts like “Eligible to Register“, “Student Hold” and many others. If you have questions about the meaning of these or any other terms, please explore the links or find more detail in the Knowledge Navigator.

As always, if you have any questions, please write help@uw.edu and put “BI Portal Report Question: UG Transcript Course Search by Major” in the subject line.

RPG New Report Release: Academic Scholarship List

The Report Prioritization Group (RPG) just released the newest addition to the BI Portal: Academic Scholarship List

In this news story we explain the purpose and benefits of the new report. If you have any questions, please don’t hesitate to write help@uw.edu and put “BI Portal Report Question: Academic Scholarship List” in the subject line.

Meaning and Purpose

The new report evolved from a very specific purpose to a more general-use tool for the entire tri-campus academic user community!

  • RPG heard this request:
    • “Will you please build us a report that will help us identify undergraduate students on visas that were dropped due to low scholarship?”
  • What RPG delivered:
    • We built a more flexible report that delivers the use case above, as well as:
      • All students: graduate and undergraduate student population
      • Students with or without visas, and all visa types (not just F or J)
      • All scholarship types, including negative ones (e.g. Drop, Probation), but also positive ones (Dean’s List)

Users and Uses

The Academic Scholarship List report is based on students transcript information and allows you to select a specific (historical) quarter and pull a list of students.

For more information about specific use cases, please visit the Interpretation tab in the BI Portal, or read below.

Report Use Cases:

Easily generate a list of Dean’s List students and give recognition

  1. First, filter filter down the Transcript Quarter and Majors you are interested in
  2. In the Quarterly Scholarship Type Filter, choose ” 1 – Dean’s List”
  3. In the Visa Type filter, choose “Select All”
  4. In the Columns to Display Filter be sure to include: Student Name, UW Email, Preferred First/Last Name, and Display First/Last Name

Now when you run the report you’ll generate a list of Dean’s List students for the selected Majors and Quarters,

If you plan to send a “congratulations” email to these students, be sure you use the Display First and Last Name fields. But please note that “display names” are not guaranteed to be 100% accurate. Please validate them against the Student Name and Preferred Name fields.

Easily generate a list of low scholarship students and offer additional advising support

The report includes all Academic Scholarship Types, including low scholarship and probation. To generate a list of low scholarship students:

  1. First, filter filter down the Transcript Quarter and Majors you are interested in
  2. In the Quarterly Scholarship Type Filter, choose ” 2 – LOW”, ” 3 – PROBATION”, ” 5 – DROP”
  3. In the Visa Type filter, choose “Select All”
  4. In the Columns to Display Filter be sure to include: Student Name, UW Email, Preferred First/Last Name, and Display First/Last Name

If you plan to send a “advising support” email to these students, be sure you use the Display First and Last Name fields. But please note that “display names” are not guaranteed to be 100% accurate. Please validate them against the Student Name and Preferred Name fields.

What is Scholarship?

You may be thinking:

“Scholarship, like Financial Aid?”

No! When we say “Academic Scholarship” in the context of this report, we’re referring to the SDB Scholarship Type:

Academic Scholarship refers to the various satisfactory or unsatisfactory standings of a student as they progress toward completion of their degree. Academic Scholarship does not refer to any types of financial or award scholarships.

For more information on the meaning of this term, please visit the Definitions tab in the BI Portal!

Student Display Name: We Need Your Input

In this report we are piloting a new data element called Student Display Name. We need to hear from you if this element is meaningful and useful and if we should add it to other “list” style reports like Class List by Curriculum Course and Section. To share your input, please write help@uw.edu and put “BI Portal Report Feedback: Academic Scholarship List”

Here’s how it works:

We heard that advisers and others spend hours preparing student names for email lists. So we created the display name fields in the report based on the SDB Student Name so that you no longer have to create it yourself! This new data element relies on the SDB Student Name data and optional student-provided Preferred Name field.

  • If a student does provide a preferred name (first, middle, last), we use that as the display name (first, middle, last)
  • If a student does not provide a preferred name, we parse the SDB Student name into discrete name elements (first, middle, last) and use those.

For Example:

If a student does provide a preferred name:

  • SDB Name: Zimmerman, Robert Allen Sr.
  • Preferred Name: Bob Dylan
  • Display Name:
    • First: Bob
    • Last: Dylan

If a student does not provide a preferred name:

  • SDB Name: Zimmerman, Robert Allen Sr.
  • Preferred Name: <no preferred name>
  • Display Name:
    • First: Robert
    • Last: Zimmerman

Please Note: Parsing a single name field is not an exact science. Here’s an example:

  • We look for the string “IV” in the SDB student name to identify “the fourth”. But sometimes a person’s middle name is “Liv” and we catch that as a partial match.

As a result, we recommend you still use the SDB Name and Preferred Name fields to validate the Display Name results. However, we strongly believe that this “validation” will be faster and easier than “DIY calculation” and will save advisers and other “list report users” lots of time!

Questions?

This report references important institutional concepts like Academic ScholarshipCumulative GPA, Student Display Name, and many others. If you have questions about the meaning of these or any other terms, please explore the links or find more detail in the Knowledge Navigator.

As always, if you have any questions, please write help@uw.edu and put “BI Portal Report Question: Academic Scholarship List” in the subject line.

FWS v2 EVAL Release 2 is now available

FWS v2 Release 2 is now deployed in EVAL. Processing has been turned back on and will provide the most current P1.5 data from UW11 Workday Tenant. Check out the Release Notes here for new features, changes, and bug fixes. You can also find a link to our Release Notes and additional resources including a ‘Getting Started Guide’ to support your evaluation on our FWS v2 Support Page.

FWS v2 DEV continues to provide current P1.5 data. Note that changes are made on DEV on a daily frequency without notice. We continue to recommend EVAL if you require a more stable environment for your evaluation.

Support

  • Please submit support requests to fws-support@uw.edu with ‘FWS v2 EVAL’ in the subject line.
  • Subscribe to fws-ft-users to stay current on upcoming deployments and changes.
  • Subscribe to the FWS v2 Support page; we will be adding new resources to this page periodically.
  • We will support questions related to e.g. missing data, data structure, access/connection issues, and adding access for additional NetIds or Applications.
  • For questions regarding data quality please contact UWFT at uwftask@uw.edu.  

New PAS Data Enhancement in the EDW

Procurement Credit Card Spend Data Now Matched to True Supplier

In October of 2018, a project was initiated to capture all suppliers from the University’s Procurement Accounting System (PAS) in the Enterprise Data Warehouse (EDW). The project was comprised of three major steps:

  • First, to capture all existing Suppliers from the PAS system in EDW 
  • Second, to secure all Spend financials and diversity indicators attributed to those suppliers 
  • And last, to attribute Procurement Credit Card transactions to the true supplier, not simply the credit card merchant (JPMorganChase)

In late January 2021, this final planned enhancement to the EDW for the PAS spend and diversity data was completed. 

What’s New
Now, users who query the EDW for procurement data have the ability to see credit card (Procurement Card, ProCard) transactions attributed to the true suppliers of those transactions. Rather than the default supplier designation of JP Morgan Chase, procurement card transactions show the true supplier*.  With the true supplier designations for the majority of credit card transactions, users can easily determine which transactions were made with diverse suppliers (e.g. women-owned, veteran-owned and minority-owned businesses).

The credit card transaction data provides specific supplier information which in turn, provides details for diverse spend. The PAS data in the EDW shows:

  • Over half a million ProCard transactions assigned to the true supplier
  • Over 140,000 ProCard transactions assigned to diverse suppliers

Why This Matters
Accurate, secure and accessible data is critical for:

  • Financial Transformation
  • Regulatory reporting requirements
  • Department analysis, accountability, and decision-making
  • The University’s commitment to diversity, equity and inclusion efforts

What Can This New Data Tell You?

  • In the calendar year XXXX, how much did my department spend with diverse suppliers?
  • In fiscal year XXXX, what percentage of our credit card transactions were attributed to diverse suppliers?
  • In the last biennium, which diverse suppliers did the majority of our credit card transactions go to?
  • And more

The project to provide this much needed PAS data is the result of the successful partnership between Ann Anderson, Associate VP, UW Finance, Doug Divine, Director, DATAGroup/Global Operations Support, Financial Management and the UW-IT Information Management division.

Business Analysts can execute SQL queries to access and analyze PAS data. See Eric Elkins’ Knowledge Base Article for basic queries and additional insights into using PAS data in the EDW.

KNOWLEDGE BASE

To access EDW data, you need to be authorized via ASTRA. To get more information on accessing the EDW, click the link below.

ACCESS EDW DATA

If you have questions or need support, please send your correspondence to help@uw.edu with “EDW PAS data” in the subject line.

_____________

*Please Note: Due to some technical limitations in the data provided by JPMorgan Chase, not all true suppliers can be attributed to procurement credit card transactions.

BI Portal Update: Consolidated Budget Status Reports

Update (5/26/2021): This work is complete and now the following reports are no longer available on the BI Portal: Consolidated Budget Status Report Menu and Consolidated Budget Status Report by MyFinancialDesktop Static Budget List.


The Enterprise Reporting and Analytics team just released an update to the BI Portal Consolidated Budget Status reports. This update contributes to our goal of preparing for Finance Transformation by simplifying and consolidating reports in our BI Portal report catalog.

There are three Budget Status reports currently accessed from the Consolidated Budget Status Report Menu in the BI Portal. The updates described below apply to these 3 reports and the menu:

 

Why Should You Care?

You may currently use the Consolidated Budget Status Report Menu report as a point of access for three reports that allow you to see budget status, with breakdowns by:

  • Organization Code
  • MyFD Static Budget List
  • Parent Grant/Budget

Please Note: We are in the process of making updates to the three reports and the menu that will change how you access this information. In short, we’re trying to make it easier and clearer to get the information you need, rather than forcing you through an unnecessary “menu” report.

Change Summary:

You can now access these reports directly from the BI Portal, without having to search for the “report menu”!

In this release we made the following changes:

In the coming weeks we will make the following changes:

  • We will archive the “menu report” Consolidated Budget Status Report Menu (Yay! Fewer clicks to get where you’re going!)
  • We will archive the ‘Report by MyFinancialDesktop Static Budget List’. The BI Team will work with users of this report to help them begin using the Financial Activity Cube to replace this report.

Questions and Feedback:

For definitions of any of the concepts included in this report, please see the Definitions tab in the BI Portal or visit Knowledge Navigator.

If you have any questions or feedback about the changes to this report, please write help@uw.edu with “BI Portal Question: Budget Status Reports” in the subject line.

This work is part of our team’s effort to prepare for Finance Transformation by consolidating and simplifying BI Portal reports. We appreciate your patience and partnership!

SpaceWS EVAL Release: Support for migrating to the new Space Inventory Management System

During the last week of March 2021, the Capital and Space Management team will be migrating to a new Space Inventory Management System.

We are adapting Space Web Service (SpaceWS) to the source system changes which will result in:

  • Some field type and length changes
  • Some fields will no longer provide any data (We will NOT remove any fields at this time)

Change Details:

The list of field changes that may impact you are available on our Wiki at https://wiki.cac.washington.edu/display/EBWS/SpaceWS+v1+Source+Change


Opportunity to Evaluate:

These changes are in the SpaceWS EVAL environment and available for you to test. Please see https://wiki.cac.washington.edu/display/spacews/Environments for instructions on connecting to this environment. We are scheduled to release these changes into Production in coordination with the Capital and Space Management team on March 31, 2021

Support:

Please contact us at spacews-support@uw.edu

We will send an additional communication when these changes are in Production.

BI Portal Update: New Filters on Fiscal Year Income and Expense Summary

The Enterprise Reporting and Analytics team just released an update that combines two BI Portal Finance reports:

  • Fiscal Year Income and Expense Summary by OrgCode and Funding Source
  • Fiscal Year Income and Expense Summary by OrgCode and Function

Into one report, now called

Why Should You Care?

If you use the …by Org Code and Funding Source report you’ll notice it now has new filters and a new (shorter) name! If you use the …by OrgCode and Function report, you should now use the updated report (Fiscal Year Income and Expense Summary).

Please note:

  • If you exclusively use the …by OrgCode and Function report, in the next two weeks, it will be archived and no longer available on the BI Portal. Please take time to familiarize yourself with the updated Fiscal Year Income and Expense Summary report!
  • Update: If you exclusively use the …by OrgCode and Function report, it has been archived and  is no longer available on the BI Portal. Please take time to familiarize yourself with the updated Fiscal Year Income and Expense Summary report

Change Summary:

Previously the two reports differed mainly in the way the columns displayed – either by Function or by Funding Source. Now, you can get either view by going to a single report (Fiscal Year Income and Expense Summary) and simply selecting your preferred view in the ‘View by’ parameter (it defaults to funding source, since that’s the way most people were viewing it).

 

There are also filters to choose which funding sources and functions you’d like to include.

This update makes the Fiscal Year Income and Expense Summary by OrgCode and Function report obsolete. Since it is no longer necessary now that we’ve included all functionality in the new report, we will archive this report in the next 2-3weeks.

Questions and Feedback:

For definitions of any of the concepts included in this report, please see the Definitions tab in the BI Portal or visit Knowledge Navigator.

If you have any questions or feedback about the changes to this report, please write help@uw.edu with “BI Portal Question: Fiscal Year Income and Expense Summary” in the subject line.

This work is part of our team’s effort to prepare for Finance Transformation by consolidating and simplifying BI Portal reports. We appreciate your patience and partnership!

How To: Finance Date Functions in EDW

Do you ever get tired of building complicated date logic in your EDW queries?

The EDW now supports several finance date functions to help you simplify your queries! These functions help enterprise data users to easily convert calendar dates, months, and years to UW fiscal calendar objects. These functions are most helpful to SQL developers working on reports and visualizations that use fiscal calendar parameters/variables.

Context: 

In SQL, a function is a program that takes some input and generates a value. SQL has many built-in functions that you get out-of-the-box.  For example, one of the built-in system functions is GETDATE().  This function returns the current date and does not require an input or argument. Another example of a system function is REPLACE(), which expects to have 3 inputs, 1. The expression you want to search (i.e. column or field), 2. what you are searching for, and 3. what you want to replace it with.

The UW-IT EDW team recently added 5 new functions to the EDW. The following functions are now available to use:

Function and Syntax Description
FiscalYear(date) Returns the fiscal year as a number based on the date input you provide.
FiscalMonth(date) Returns the fiscal month as a 2-character string based on the date input you provide.
BienniumYear(date) Returns biennium year as a number based on the date input you provide.
BienniumMonth(date) Returns biennium month as a 2-character string based on the date input you provide.
LastMonthEndDate(date) Returns last date of the prior calendar month based on the date input you provide.

How you can use these functions today: 

If you ever do your own calculations in SQL to determine things like Fiscal Year or Biennium start or end dates, or create a rolling window, then you might benefit from using these functions.

These functions reside in EDWPresentaton database.  To call a function simply follow examples below:

SELECT 
EDWPresentation.dbo.FiscalYear('4/4/2018') as FiscalYear,
EDWPresentation.dbo.FiscalMonth('4/4/2018') as FiscalMonth,
EDWPresentation.dbo.BienniumYear('4/4/2018') as BienniumYear,
EDWPresentation.dbo.BienniumMonth('4/4/2018') as BienniumMonth,
EDWPresentation.dbo.LastMonthEndDate('4/4/2018') as LastMonthEndDate

Please Note:

  • When functions are used as parameters in a report or visualization, they should be set as variables.
  • Also, the BienniumMonth function returns values ranging from 01-24; however, UW accounting months are 01-25 or in previous years may even have fallen between 01-27. This happens because some transactions are entered in a new biennium, but should be attributed to the prior one. Examples below show how to use functions in variables and how to handle accounting months

Examples

SQL – if parameters are start and end dates

--Report parameters DECLARE @MyDate date = '4/4/2018' 
DECLARE @FiscalYear varchar(4) = EDWPresentation.dbo.FiscalYear(@MyDate)  DECLARE @AcctngMonth int = 
case 
   when EDWPresentation.dbo.BienniumMonth(@MyDate) = '24' 
      then '27'  
   else EDWPresentation.dbo.BienniumMonth(@MyDate) 
end DECLARE @BienniumYear varchar(4) = EDWPresentation.dbo.BienniumYear(@MyDate) SELECT @FiscalYear FiscalYear, @BienniumYear BienniumYear, @AcctngMonth AcctngMonth

SQL – if parameters are month and year

--Report parameters DECLARE @calmonth int = 9 DECLARE @calyear int = 2017 

--Converting calendar month and year to a date that can be used by functions
DECLARE @MyDate 
   date = convert(date, convert(varchar(4),@calyear) + '-' + convert(varchar(2),
       @calmonth) + '-01') 
DECLARE @FiscalYear varchar(4) = EDWPresentation.dbo.FiscalYear(@MyDate)  DECLARE @AcctngMonth int = 
case 
   when EDWPresentation.dbo.BienniumMonth(@MyDate) = '24' then '27'  
      else EDWPresentation.dbo.BienniumMonth(@MyDate) 
end
DECLARE @BienniumYear varchar(4) = EDWPresentation.dbo.BienniumYear(@MyDate)
SELECT @FiscalYear FiscalYear, @BienniumYear BienniumYear, @AcctngMonth AcctngMonth

SQL – rolling window (2 years back from end date)

--Report parameters DECLARE @EndDate date = '4/4/2018'
 --Converting end date into a 2-year rolling window  DECLARE @LastMonthEndDate date = EDWPresentation.dbo.LastMonthEndDate(@EndDate)
DECLARE @BienniumYear varchar(4) = EDWPresentation.dbo.BienniumYear(@LastMonthEndDate)
DECLARE @AcctngMonth varchar(2) = 
case 
   when EDWPresentation.dbo.BienniumMonth(@LastMonthEndDate) = '24' then '27'  
      else EDWPresentation.dbo.BienniumMonth(@LastMonthEndDate) 
end 
DECLARE @EndRollingPeriod varchar(6) = @BienniumYear + @AcctngMonth DECLARE @StartRollingPeriod varchar(6) = CONVERT(varchar(4), CONVERT(int, @BienniumYear)-2) + @AcctngMonth SELECT @StartRollingPeriod, @EndRollingPeriod

Questions:

If you have any questions about functions or how to use them in your solution, please write help@uw.edu and put “EDW Feature: Finance Date Functions” in the subject line.

Financial Activity 2019 Cube Update: New Attributes on Finance Cube

Based on input from users, we just published updates to the Financial Activity Biennium 2019 cube (finance cube). We added several new attributes to the cube that make it easier to get the finance data you need to do your work.

In addition to the cube changes, we also want you to know about some other great content we recently published!

  • Data Definitions: Finance cube data definitions are now in Knowledge Navigator
  • Training/Help Videos: We recently published a suite of videos to help you answer several common use cases with the finance cube. Check out our Finance Data Cube Resources page (EDW Access required).

Change Summary:

In this release we added several attributes to existing cube dimensions. These fields were added to support users that want to migrate from using BI Portal finance reports to the cube. If you’re tired of running a report, then exporting the data, filtering, and organizing it in the format you want, consider using the finance cube!

We added the following attributes to the Org-Budget Dimension in the “More Fields” grouping:

  • Budget Status
  • Old Budget Nbr
  • Parent Budget Nbr
  • Current Period Begin Date
  • Current Period End Date
  • Grant Tracking Nbr
  • Grant Contract Nbr
  • Total Period Begin Date
  • Total Period End Date

More Changes Are Coming:

We are currently designing a new Financial Activity Biennium 2019 cube. This new cube design will still provide you the data you need to do your work, but it will consolidate several dimensions, improve some of the dimension and attribute names, and overall make the cube easier to use!

In addition to the finance cube redesign, we are also preparing to release a new Financial Activity cube for Biennium 2021 in the next fiscal year. Please stay tuned for more information about the new cube.

If you would like to get involved with the finance cube redesign and share your feedback with the BI Team through our user review sessions, please write us at help@uw.edu with “BI Portal: Finance Cube Redesign” in the subject line.

Questions:

The finance cube references core institutional concepts like Budget Number, Account Code, and so many others. For definitions to these and other institutional terms, please explore Knowledge Navigator!

As always if you have any questions or feedback, please write help@uw.edu with “BI Portal: Financial Activity 2019 cube” in the subject line!