As of 12/29/23, the BI Portal now includes Release 1 of the SF425 report! This report allows Grant and Contract Accounting (GCA) to pull data from Workday into the SF425 Federal Financial Report, which is required to report on a grant’s cumulative expenses. This report was developed in collaboration between the BI Portal and DATAGroup teams. Check out the SF425 report in the BI Portal to learn more!
Why is the SF425 report a big deal?
For Release 1, the report pulls data for any reporting period that ends on 7/1/23 or later and displays the results within the SF425 form, in the correct format. This saves users significant time and reduces the potential for error.
Note: As with other new financial reports, this report will follow an iterative development process and planning for Release 2 is already underway.
How will GCA use the report?
This report is expected to streamline SF425 reporting for GCA as follows:
Enter the criteria into the prompts provided. Sample Report Criteria for the SF425 Report in the BI Portal
Review the results, which are properly formatted for the SF425 form. Sample Results for the SF425 Report in the BI Portal
If the results are correct, submit the form.
Questions?
Please contact help@uw.edu with “BI Portal” in the subject line.
As of 12/5/23, the BI Portal now includes the Non-Numeric Grade Frequency Distribution dashboard! This dashboard allows users to explore trends in grading patterns, missing grades, and other non-numeric grade outliers across UW academic departments. It reflects rolling data from the last 12 quarters and is intended for advisors, registrars and academic service leaders.
These are values assigned to a student’s transcript that do not follow the standard numerical grading system (4.0 scale). The following non-numeric values are included in this dashboard:
Incomplete
Registrar Drop
Missing Grade Annotations
Satisfactory/Not Satisfactory
Pass/Fail
Credit/No Credit
Honors
High Pass
In Progress
Letter Grades (A – E)
Does the dashboard include any Personally Identifiable Information (PII)?
The dataset does not include any PII, meaning there is no student, staff or faculty-identifying data. The most granular level of data available is a specific Curriculum Code (for example, ENG) and Course Level (for example, 100, 200, etc.).
How do I use the dashboard?
The dashboard makes it really easy to look at data in different ways by using filters to refine the view, expose trends and drill into the details to investigate, as needed. The following is a typical use case.
Use Case – Investigate Missing Grades
A user would take the following steps to explore trends in missing grades and take action to resolve them.
Click Run Dashboard. The dashboard defaults to the Trends view, presenting data for non-numeric grade values in three charts for all three UW Campuses. Default View of the Dashboard
In the Grade filter, select Missing Grade Annotations. Use additional filters to refine your results, as needed. Sample Results for Missing Grade Annotations Filter
To display a detailed report of the data as a table, click Go to Details >>. “Go to Details > >” Button Default View of the Details Report
To expose all available data, drill down to the Course Level.
Hover over the Course Campus column to display the plus sign (+). Click the plus sign (+) to display the Course College column.
Repeat for the Course College column, then the Course Department column, and then the Curriculum column to display the distribution of missing grades by course level. This is the most granular level of information available in the dashboard. Course Level Drill Down on the Details Report
Optional To export the data to Excel for further analysis, click the Choose a format to download icon and then select Crosstab. Selections to Export Data to Excel
Questions?
Please contact help@uw.edu with “BI Portal Dashboards” in the subject line.
A version of this message was sent to managers of affected UW Shared Drives on November 28, 2023.
What is happening?
Because your UW Google Shared Drive exceeds the 100GB limit, we want to remind you that you’ll need to purchase additional storage space before June 11, 2024. Our contract with Google now has system limitations that will require deletion of any UW Google Shared Drive that exceeds 100GB starting November 2024.
IMPORTANT: UW Google Shared Drives that are over the maximum quota will be deleted. UW-IT is unable to delete a portion of content in order to get the Shared Drive under the quota limit.
When is it happening?
OnJune 11, 2024, all UW Google Shared Drives that are over the 100GB limit will be restricted. You will still be able to view or download content in the affected drives, but you will be unable to add, modify or update existing files.
StartingNovember 5, 2024, all restricted UW Google Shared Drives that have not chosen to upgrade to a higher tier of storage will be subject to deletion.
What do I need to do now?
Review the attached list of UW Google Shared Drives that have been identified as close to or over the 100GB limit and determine which tier(s) of storage you will need to purchase. See available storage tiers and pricing information on IT Connect.* With this information, you can then budget accordingly for the upcoming fiscal year.
If you do not wish to purchase a higher tier of storage for the over quota UW Google Shared Drives, please make plans to migrate data — so that your data is under the 100GB limit.
*For storage greater than 1TB per year, please email help@uw.edu with the subject: UW Google Shared Drive – Custom Storage Pricing Information.
Please note: If a Shared Drive is flagged for deletion, the entire drive will be deleted, not just a select amount over the 100GB limit.
How do I purchase a higher tier of storage?
In April 2024, the UW Google Changes Project Team will provide an intake form for purchasing additional storage to anyone whose Shared Drive is over quota at that time. This form will collect required information such as the department, work tag, name of the UW Google Shared Drive(s), primary contact, etc.
Once we receive this information, the specified UW Google Shared Drive(s) will no longer be subject to deletion, provided that the governance and drive deletion policy are maintained. For more information, review the UW Google Shared Drive Service Offering page.
Where can I go for help?
Please contact the UW-IT Technology Service Center at help@uw.edu or 206-221-5000.
Update: Removal of aging envelopes in DocuSign to begin November 2023
What’s happening?
The eSignatures service team has begun implementing procedures to guarantee the removal of aging envelopes in DocuSign. This work is expected to begin the week of November 27th. We will be reaching out to the account Delegated Administrators with more details when we are ready to begin working on each department’s account. For more information about why this change is occurring, see below.
What do I need to do?
If you have sent envelopes using DocuSign, now is a great time to start working with your team’s Delegated Administrator to identify and download any envelopes that you’ve sent that need to be retained for records retention purposes.
If you are a Delegated Administrator, work with your team members to ensure that any envelopes that need to be retained have been downloaded and stored in your team’s repository. Review your team’s DocuSign group(s) and identify if anyone has left but still has an active account. The eSignatures team can help transfer their materials to someone who will be able to download them.
Why is this change happening?
Since the introduction of the centralized eSignatures service (DocuSign) at the University of Washington in 2014, the eSignatures service has required individual users to retain completed envelopes and other records outside of the DocuSign system in a repository that meets state and federal standards for records storage as outlined in the Acceptable Use Requirements.
To encourage users to correctly store records, the eSignatures team will begin purging aging envelopes this fall. Enforcing a periodic purge will ensure compliance with the UW Records Management and UW Medicine Records and Information Governance guidelines and policies.
Support
If you have any questions or concerns regarding this announcement, please reach out to the eSignatures team directly at eSignatures Help.
If you have any questions regarding records management, please reach out to the UW Records Management Services team at recmgt@uw.edu. For questions regarding UW Medicine Records and Information Governance, you can reach their team at hrc@uw.edu.
Users whose UW Google storage currently exceeds 80GB have received a multiple reminders of the following information, beginning July 2022, and most recently on May 21, 2024.
What is happening?
As initially announced in June 2021, Google has implemented major changes to their Google Workspace for Education product.
Among other changes, Google has moved to a shared storage pool. We are sharing this information to encourage you to prepare and find alternative solutions for data storage. Learn more about Google’s new storage policy.
Google’s shift to shared storage for Google Workspace for Education means that every UW Google account will be subject to a 100GB storage quota, effective June 11, 2024.
As a step toward establishing the 100GB quota, on August 23, 2022, UW-IT implemented tiered storage quotas that are greater than users’ existing data storage usage.
When is this change taking place?
As of June 11, 2024, personal UW Google accounts that are over quota will be restricted and subject to deletion
· All user accounts must be below 100GB in total storage utilization before this date.
· In order to comply with the terms of Google’s new storage policy, user accounts that exceed 100GB and all associated data are subject to permanent deletion.
What steps can I take to prepare for the storage limit?
Shared Drives are available to UW employees who take active responsibility for managing data and access. Individuals may request a Shared Drive with storage capacity up to 100GB. Shared Drives larger than 100GB are subject to additional cost.
Please note that students are not eligible to manage Shared Drives and thus cannot request a Shared Drive.
What will happen to my data if I do not take action?
Starting June 11, 2024, all over quota personal UW Google accounts are subject to permanent deletion. All data associated with the account will be deleted and cannot be recovered.
Where can I go for help?
UW-IT’s service technicians stand ready to answer any questions you may have about this change, and about the different storage options available.
Please contact the UW-IT Technology Service Center at help@uw.edu or 206-221-5000.
You can also visit IT Connect to learn more about migrating your own data. Users can also work directly with their department’s IT support group for specific recommendations and more individualized help. UW-IT is currently working with vendors to determine the feasibility of providing a tool to migrate data from UW Google to an alternative repository. We will communicate about available solutions as soon as possible.
Historically, UW relied on financial org code (fin org) for HR reporting. With the introduction of Workday Finance, fin org was retired and a replacement was needed to support HR reporting going forward. A new HR Hierarchy structure that more accurately represents HR relationships was introduced to Workday. To learn more about the new HR Hierarchy, refer to https://hr.uw.edu/hrbais/hrhierarchy/.
Introducing a new HROrganization table in UWODS
The Enterprise Data Warehouse (EDW) introduced the UWODS database in July 2023, which provides HR/Payroll and Finance data sourced from Workday. The EDW recently added a new HROrganization table to UWODS that now provides HR Hierarchy data and is ready for you to query today for your own reporting needs.
Join us for Office Hours
EDW Subject Matter Experts are available during the Enterprise Reporting and Analytics (ERA) Office Hours every Friday from 9 to 10. If you have questions about the new HROrganization table or anything else related to the EDW, please drop in to ask your questions.
You can either sign up ahead of time or drop by during the session:
UW-IT works with partners across the UW to support the technology that drives teaching, learning, research and work. These partners — from distributed IT Support to departmental IT directors and leadership — are a key audience and stakeholders for UW-IT. To help deliver key information to them from UW-IT, we’ve created an IT Community guide on IT Connect. This guide contains information curated for IT partners across the UW. Over time, this IT Community guide will grow to be more comprehensive and include more information.
You can help us ensure the guide contains all the information it needs. If you have information from your division, unit, or service that you think belongs on the guide, let us know by emailing help@uw.edu with Communications & Engagement in the subject line.
IT Connect is now running the latest major version of analytics: Google Analytics 4. The legacy Universal Analytics previously used on the site stopped collecting data earlier this year, and around the end of the year Google plans to shut it down completely.
This means that historical data about site usage will be inaccessible, including information about visitors to your content on IT Connect. While the IT Connect service team has saved high-level platform data about how the site has been used from a global perspective, information about specific sections of the site cannot be saved in mass. However, if you want to save information about your content, you are enabled and encouraged to do so.
The IT Connect service team maintains a wiki with important information about the platform and service. This wiki documents roles & responsibilities, support plans, key performance indicators, a log of changes to the site, and a roadmap for what’s coming.
This wiki is open to all UW-IT to browse and learn about how the platform is managed, and what’s on the horizon for the service. If you are interested in learning more about the IT Connect service, check out the service page.
Web Content Best Practices: Set the navigation sort order
Did you know that the pages that appear in the left-side navigation of an IT Connect section can be sorted into an order that makes the most sense for your readers? While pages are ordered alphabetically by default, you have full control over the order items appear on the section-level menu.
As a best practice, set the page order in a way that makes sense for a user’s journey. For example, if you have a page about how to sign in to a tool/service, have that page ordered higher than a page about how to configure options once signed in, as a user would logically follow that order. The best order for the navigation menus is up to you as a content manager; put yourself in the shoes of your end users.
Do you need some help creating IT Connect content, another head to brainstorm content organization and layout, or want to learn how to use the features available in IT Connect? There are several ways to get help:
Content Manager Documentation: Extensive documentation, ranging from the basics of WordPress to advanced features for pages, is available on the IT Connect Content Manager Documentation.
Guide to writing documentation: Use the Getting started with documentation guide to help you start writing documentation. The guide breaks down the documentation process that will benefit your end users.
Training: One-on-one training for managing content on IT Connect is available from the IT Connect service manager, Nick Rohde, over Zoom or in person. Get tips on correctly formatting content using the tools in IT Connect or learn how to organize your content. To arrange training, fill out this intake form.
Consultation: Consultation sessions for individuals or teams are available from the IT Connect product manager, Nick Rohde. To schedule a consultation, fill out this intake form.
It’s been three months since the UW went live with Workday Finance and as the dust settles across the financial ecosystem, bumps and crevices, once hazy and undefined, are coming into focus. As users adapt to the tools and processes of the Workday era, some areas are proving to be more difficult to navigate than others—reporting is one of these areas.
The BI Portal is hoping to bridge this gap through an iterative expansion of its catalog.
Collaborating to Meet User Requirements
Teamwork makes the dream work, and while the new reports exist in the BI Portal, they would not be there without the DATAGroup’s partnership. The DATAGroup provided subject matter expertise to make sure the new finance reports are meaningful, engaged with users to understand gaps and requirements, and shared examples and feedback to support the development team. The BI Portal team leveraged the DATAGroup’s input, built reports that meet user, security, and metadata requirements, tested the reports, and deployed them to the BI Portal catalog.
Note: Data is key for building meaningful reports, so while the need for additional reports was anticipated, development could not advance until Workday production data became available in July of 2023.
Introducing the New Reports
We are excited to announce that the first three Workday finance reports are now available in the BI Portal!
Note: The BI Portal team and DATAGroup are continuously learning about requirements, so reports, especially new Finance reports, follow an iterative development process. If you check out these new reports today and they don’t have what you need, please know that this is not the final version. Additionally, if you want to share specific requirements or feedback, please email us at help@uw.edu and include “BI Portal Finance Reports” in the subject line.
Workday Variable Reporting Period Transaction Summary
This report allows users to isolate actual amounts for Grant, Award, or Award Line worktags for a specified period. It is primarily used for annual reporting to sponsors and is similar to the Legacy Variable Reporting Period Transaction Summary report; however, while the legacy report uses Financial Accounting System (FAS) data, this new report uses Workday data.
Example Output of the Variable Reporting Period Transaction Summary Report
Note: This report currently includes three worktags, but will expand to include more worktags in future releases. Additionally, this report does not work for Cost Share or Royalty Research Fund.
Workday Variable Reporting Period Budget Summary
This report displays the project period budgeted amount, encumbrances, transaction totals, and budget balances for Grant, Award, or Award Line worktags for a specified date range. It is similar to the Legacy Variable Reporting Period Budget Summary; however, while the legacy report uses Financial Accounting System (FAS) data, this new report uses Workday data.
Example Output of the Variable Reporting Period Budget Summary Report
Note: This report currently includes three worktags, but will expand to include more worktags in future releases. Additionally, this report does not work for Cost Share or Royalty Research Fund.
Find Journal Lines
This report displays journal lines and includes a number of filters to refine results, as needed.
The BI Portal report catalog now includes Workday Human Capital Management (HCM) reports!
These updates were deployed to the BI Portal on 11/1/23.
Finding Workday HCM Reports Today
Historically, the Workday HCM Report Catalog was stored in Knowledge Navigator and supported by the Integrated Service Center (ISC) to reflect all custom reports available in Workday’s HCM module.
While these reports are now available in the BI Portal, they will remain in Knowledge Navigator until 11/30/23, along with a page announcement, to give users time to adapt to this change.
Understanding the “Why” Behind this Change
The goal of BI Portal reports, cubes, and dashboards is to:
Reflect data from various subject areas: academics, advancement and alumni relations, core data, finance, human resources, property and space management, and research.
Include historical data.
Allow users to discover any report in the catalog. While a user’s Workday security role determines which reports they can run, the BI Portal allows users to discover all available reports and view security information regardless of role.
Bringing Workday HCM reports into the BI Portal aligns with the broader reporting strategy for UW Academy, which is to provide users with a one-stop-shop for all reporting needs.
Accessing Workday HCM Reports in the BI Portal
Users can find Workday HCM reports in the same way they find other resources in the BI Portal. A couple tips:
Filter by the new tag – A new Workday HCM tile is now available on the Home page to quickly drill-down to applicable reports. Workday HCM Tile on the Home Page
A Workday HCM tag is also available on the Catalog page.
Workday HCM Tag on the Catalog Page
Discover available Workday HCM reports and associated security information – In Workday, reports are assigned by security role. The security role not only determines which reports the user can run, but which reports they can discover. In the BI Portal, a user can discover any report in the catalog. While a user’s security role will still determine which reports they can run, this visibility allows users to identify potentially useful reports, check the Security Information tab to determine which roles have access, and then request elevated access, if warranted.
Note: Access to Workday HCM reports is determined by Workday HCM Security Roles. To learn more about these roles, including which HCM Security Roles you are currently assigned, refer to Workday HCM Security Roles 101.
Example of the Security Information for the R0321 Report
Questions?
Please submit questions as follows to ensure they reach the appropriate teams and get a quicker response.
If you have questions that relate to…
Then…
The actual HCM reports in Workday and associated data…
The student database (SDB) will go through a reorganization on October 21, 2023 which will cause changes in the Enterprise Data Warehouse database, UWSDBDataStore. These changes to the objects will be available in the UWSDBDataStore on October 23, 2023
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 – 10.19.23
Columns to be Added
Table
Column
DataType
SF_EDIT_DESC
SF_ED_Year_Code
smallint
SR_ADM_APPL
SEATTLE_PROMISE
char(1)
SR_TEST_SCORES
TEST_SCORE_DEC
decimal(4,1)
SYS_TBL_42_TEST_RANGE
TEST_MIN_SCORE_DEC
decimal(4,1)
TEST_MAX_SCORE_DEC
decimal(4,1)
SYS_TBL_63_NONTUIT_CHANGES
AID_REPAY_FUND
int
Columns with datatype changes
Table
Column
DataType
SR_TEST_SCORES
TEST_PCTILE
smallint
Columns to be Removed
Table
Column
DataType
SYS_TBL_63_NONTUIT_CHANGES
ON_CHRG_DB_TAG
char(12)
ON_CHRG_DB_NAME
char(12)
ON_CHRG_DB_RCAT
char(6)
ON_PAY_DB_TAG
char(12)
ON_PAY_DB_NAME
char(12)
ON_PAY_DB_RCAT
char(6)
ON_PAY_CR_TAG
char(12)
ON_PAY_CR_NAME
char(12)
ON_PAY_CR_RCAT
char(6)
Columns to be Added in SF_EVALUATION*
SF_Evaluation will be split into multiple tables post reorg, splits will be available in this page as soon as determined 10.11.23 – see table split below column adds 10.18.23
Column
DataType
SF_EVALUATION
EVAL_SPARE_36
int
EVAL_SPARE_37
int
EVAL_SPARE_38
int
EVAL_SPARE_39
int
EVAL_SPARE_40
char(4)
EVAL_SPARE_41
char(4)
EVAL_SPARE_42
char(4)
EVAL_SPARE_43
char(4)
EVAL_SPARE_44
int
EVAL_SPARE_45
int
EVAL_SPARE_46
int
EVAL_SPARE_47
int
SF_EVALUATION
FAFSA_UUID
char(36)
TRANS_UUID
char(36)
PERSON_UUID
char(36)
FAFSA_APP_SRC
tinyint
FAFSA_TRANS_SRC
tinyint
FAFSA_TRANS_TYPE
char(1)
FAFSA_TRANS_LANG
char(1)
FAFSA_PROC_DATE
datetime
FAFSA_TRANS_STAT
char(30)
FAFSA_RENEW_DATA
char(3)
FPS_CORR_REASON
char(1)
SAI_CHANGE_FLG
char(1)
SAI
int
SAI_ADJ
int
PROV_SAI
int
PROV_SAI_ADJ
int
FPS_SAI
int
SAI_FORMULA
char(1)
COMP_TYPE
char(2)
MAX_PELL_IND
char(1)
MIN_PELL_IND
char(1)
STD_ITIN
int
STD_COUNTRY
char(2)
PURS_TEACH_CERT
char(1)
PARENTS_DECEASED
char(1)
WARD_OF_COURT
char(1)
IN_FOSTER_CARE
char(1)
PERSONAL_CIRC
char(1)
UNACC_HMLS_GEN
char(1)
UNACC_HMLS_TRIO
char(1)
UNACC_HMLS_FAA
char(1)
OTHER_CIRCUMSTAN
char(1)
UNSUB_ONLY
char(1)
A_NUMBER
int
PARENT_ATTND_COLL
char(1)
PARENT_LINE_DUTY
char(1)
HS_EQUIV_DIP_NAME
char(1)
HS_EQUIV_DIP_ST
char(2)
STD_EITC_MAN
char(1)
STD_FED_HOUS_MAN
char(1)
STD_FREE_LNCH_MAN
char(1)
STD_MEDICAID_MAN
char(1)
STD_36B_CRED_MAN
char(1)
STD_SNAP_BEN_MAN
char(1)
STD_SSI_BEN_MAN
char(1)
STD_TNF_BEN_MAN
char(1)
STD_WIC_BEN_MAN
char(1)
STD_FED_BEN_MAN
char(1)
STD_1040_MAN
char(1)
STD_NON_US_MAN
char(1)
STD_JOINT_RET_MAN
char(1)
STD_RET_STAT_MAN
char(1)
STD_WK_INCOME_MAN
decimal (11,0)
STD_INTEREST_MAN
decimal (11,0)
STD_IRA_DIST_MAN
decimal (11,0)
STD_IRA_ROLL_MAN
decimal (11,0)
STD_PENSIONS_MAN
decimal (11,0)
STD_PENS_ROLL_MAN
decimal (11,0)
STD_AGI_MAN
int
STD_TAX_PAID_MAN
int
STD_DEDCT_PMT_MAN
decimal (11,0)
STD_FL_ABDEFH_MAN
char(1)
STD_SCHED_C_MAN
decimal (11,0)
STD_GRNT_SCHL_MAN
int
STD_FRGN_EXCL_MAN
decimal (11,0)
STD_CHLD_SUPP_MAN
int
STD_CASH_MAN
int
STD_INVEST_MAN
int
STD_BUS_FARM_MAN
int
STD_FTI_CONSENT
char(1)
STD_SIGNED
char(1)
STD_SIGNED_DT
datetime
SPO_FIRST_NAME
char(35)
SPO_MID_NAME
char(15)
SPO_LAST_NAME
char(35)
SPO_SUFFIX
char(10)
SPO_BIRTH_DT
datetime
SPO_SS_NO
char(9)
SPO_ITIN
char(9)
SPO_PHONE_NO
char(10)
SPO_EMAIL
char(50)
SPO_ADDRESS
char(40)
SPO_CITY
char(30)
SPO_STATE
char(2)
SPO_ZIP
char(10)
SPO_COUNTRY
char(2)
SPO_1040_MAN
char(1)
SPO_NON_US_MAN
char(1)
SPO_RET_STAT_MAN
char(1)
SPO_WK_INCOME_MAN
decimal (11,0)
SPO_INTEREST_MAN
decimal (11,0)
SPO_IRA_DIST_MAN
decimal (11,0)
SPO_IRA_ROLL_MAN
decimal (11,0)
SPO_PENS_ROLL_MAN
int
SPO_AGI_MAN
int
SPO_TAX_PAID_MAN
decimal (11,0)
SPO_DEDCT_PMT_MAN
decimal (11,0)
SPO_EDUC_CRED_MAN
int
SPO_FL_ABDEFH_MAN
char(1)
SPO_SCHED_C_MAN
decimal (11,0)
SPO_FRGN_EXCL_MAN
int
SPO_FTI_CNSNT_MAN
char(1)
SPO_SIGNED_MAN
char(1)
SPO_SIGN_DT_MAN
datetime
P1_FIRST_NAME
char(35)
P1_MIDDLE_NAME
char(15)
P1_LAST_NAME
char(35)
P1_SUFFIX
char(10)
P1_DOB
datetime
P1_SS_NO
int
P1_ITIN
int
P1_PHONE_NO
char(10)
P1_EMAIL
char(50)
P1_ADDRESS
char(50)
P1_CITY
char(30)
P1_STATE
char(2)
P1_ZIP
char(10)
P1_COUNTRY
char(2)
P1_EITC_MAN
char(1)
P1_FED_HOUS_MAN
char(1)
P1_FREE_LNCH_MAN
char(1)
P1_MEDICAID_MAN
char(1)
P1_36B_CRED_MAN
char(1)
P1_SNAP_BEN_MAN
char(1)
P1_SSI_BEN_MAN
char(1)
P1_TANF_BEN_MAN
char(1)
P1_WIC_BEN_MAN
char(1)
P1_FED_BEN_MAN
char(1)
P1_1040_MAN
char(1)
P1_NON_US_MAN
char(1)
P1_JOINT_RET_MAN
char(1)
P1_RET_STAT_MAN
char(1)
P1_WK_INCOME_MAN
decimal (11,0)
P1_INTEREST_MAN
decimal (11,0)
P1_IRA_DIST_MAN
decimal (11,0)
P1_IRA_ROLL_MAN
decimal (11,0)
P1_PENS_ROLL_MAN
decimal (11,0)
P1_AGI_MAN
int
P1_TAX_PAID_MAN
int
P1_DEDCT_PMT_MAN
decimal (11,0)
P1_EDUC_CRED_MAN
decimal (11,0)
P1_FL_ABDEFH_MAN
char(1)
P1_SCHED_C_MAN
decimal (11,0)
P1_GRNT_SCHL_MAN
int
P1_FRGN_EXCL_MAN
int
P1_CHLD_SUPP_MAN
int
P1_CASH_MAN
int
P1_INVEST_MAN
int
P1_BUS_FARM_MAN
int
P1_FTI_CONS_MAN
char(1)
P1_SIGNED_MAN
char(1)
P1_SIGN_DT_MAN
datetime
P2_FIRST_NAME
char(35)
P2_MIDDLE_NAME
char(15)
P2_LAST_NAME
char(35)
P2_SUFFIX
char(10)
P2_DOB
datetime
P2_SS_NO
int
P2_ITIN
int
P2_PHONE_NO
char(10)
P2_EMAIL
char(50)
P2_ADDRESS
char(50)
P2_CITY
char(30)
P2_STATE
char(2)
P2_ZIP
char(10)
P2_COUNTRY
char(2)
P2_1040_MAN
char(1)
P2_NON_US_MAN
char(1)
P2_RET_STAT_MAN
char(1)
P2_WK_INCOME_MAN
decimal (11,0)
P2_INTEREST_MAN
decimal (11,0)
P2_IRA_DIST_MAN
decimal (11,0)
P2_IRA_ROLL_MAN
decimal (11,0)
P2_PENSIONS_MAN
decimal (11,0)
P2_PENS_ROLL_MAN
decimal (11,0)
P2_AGI_MAN
int
P2_TAX_PAID_MAN
decimal (11,0)
P2_DEDCT_PMT_MAN
decimal (11,0)
P2_EDUC_CRED_MAN
decimal (11,0)
P2_FL_ABDEFH_MAN
char(1)
P2_SCHED_C_MAN
decimal (11,0)
P2_FRGN_EXCL_MAN
int
P2_FTI_CONS_MAN
char(1)
P2_SIGNED_MAN
char(1)
P2_SIGN_DT_MAN
datetime
STD_AFFIL_STAT
char(1)
STD_SP_AFFIL_STAT
char(1)
STD_P1_AFFIL_STAT
char(1)
STD_P2_AFFIL_STAT
char(1)
STD_CONS_GRNT_DT
datetime
SP_CONS_GRNT_DT
datetime
P1_CONS_GRNT_DT
datetime
P2_CONS_GRNT_DT
datetime
STD_TU_MATCH_DT
datetime
SP_TU_MATCH_DT
datetime
P1_TU_MATCH_DT
datetime
P2_TU_MATCH_DT
datetime
CORRECTION_APPLD
char(2)
FAA_SIGNED
char(1)
IASG_INDICATOR
char(1)
COFH_INDICATOR
char(1)
ETI_DEST_NUM
char(7)
STD_SIGNED_SRC
char(1)
SP_SIGNED_SRC
char(1)
P1_SIGNED_SRC
char(1)
P2_SIGNED_SRC
char(1)
SPEC_HAND_IND
char(1)
INCARC_APPL
char(1)
SF_EVALUATION
IP_STD_FWS
decimal (15,0)
IP_SP_FWS
decimal (15,0)
IP_P1_FWS
decimal (15,0)
IP_P2_FWS
decimal (15,0)
IP_P_PTA
decimal (15,0)
IP_P_PEEA
decimal (15,0)
IP_STD_PTA
decimal (15,0)
IP_STD_PNAAI
decimal (15,0)
IP_STD_SEEA
decimal (15,0)
IP_STAI
decimal (15,0)
IP_SCI
decimal (15,0)
IP_SAAI
decimal (15,0)
IP_SC_SAAI
decimal (15,0)
IP_A_SFS
smallint
IP_A_PFS
smallint
SF_EVALUATION
CUI_BEGIN_STRING
char(11)
CUI_STD_TAX_YEAR
smallint
CUI_STD_FILE_STAT
char(1)
CUI_STD_AGI
int
CUI_STD_EXEMPTS
tinyint
CUI_STD_DEPS
tinyint
CUI_STD_INC_EARN
decimal (11,0)
CUI_STD_TAX_PAID
int
CUI_STD_EDUC_CRED
int
CUI_STD_IRA_DIST
decimal (11,0)
CUI_STD_IRA_PYMTS
decimal (11,0)
CUI_STD_INTEREST
decimal (11,0)
CUI_STD_PENSIONS
decimal (11,0)
CUI_STD_SCHED_C
decimal (11,0)
CUI_STD_SCHED_A
char(1)
CUI_STD_SCHED_B
char(1)
CUI_STD_SCHED_D
char(1)
CUI_STD_SCHED_E
char(1)
CUI_STD_SCHED_F
char(1)
CUI_STD_SCHED_H
char(1)
CUI_STD_IRS_RESP
smallint
CUI_SPO_TAX_YEAR
smallint
CUI_SPO_FILE_STAT
char(1)
CUI_SPO_AGI
int
CUI_SPO_EXEMPTS
tinyint
CUI_SPO_DEPS
tinyint
CUI_SPO_INC_EARN
decimal (11,0)
CUI_SPO_TAX_PAID
int
CUI_SPO_EDUC_CRED
int
CUI_SPO_IRA_DIST
decimal (11,0)
CUI_SPO_IRA_PYMTS
decimal (11,0)
CUI_SPO_INTEREST
decimal (11,0)
CUI_SPO_PENSIONS
decimal (11,0)
CUI_SPO_SCHED_C
decimal (11,0)
CUI_SPO_SCHED_A
char(1)
CUI_SPO_SCHED_B
char(1)
CUI_SPO_SCHED_D
char(1)
CUI_SPO_SCHED_E
char(1)
CUI_SPO_SCHED_F
char(1)
CUI_SPO_SCHED_H
char(1)
CUI_SPO_IRS_RESP
smallint
CUI_P1_TAX_YEAR
smallint
CUI_P1_FILE_STAT
char(1)
CUI_P1_AGI
int
CUI_P1_EXEMPTS
tinyint
CUI_P1_DEPS
tinyint
CUI_P1_INC_EARN
decimal (11,0)
CUI_P1_TAX_PAID
int
CUI_P1_EDUC_CRED
int
CUI_P1_IRA_DIST
decimal (11,0)
CUI_P1_IRA_PYMTS
decimal (11,0)
CUI_P1_INTEREST
decimal (11,0)
CUI_P1_PENSIONS
decimal (11,0)
CUI_P1_SCHED_C
decimal (11,0)
CUI_P1_SCHED_A
char(1)
CUI_P1_SCHED_B
char(1)
CUI_P1_SCHED_D
char(1)
CUI_P1_SCHED_E
char(1)
CUI_P1_SCHED_F
char(1)
CUI_P1_SCHED_H
char(1)
CUI_P1_IRS_RESP
smallint
CUI_P2_TAX_YEAR
smallint
CUI_P2_FILE_STAT
char(1)
CUI_P2_AGI
int
CUI_P2_EXEMPTS
tinyint
CUI_P2_DEPS
tinyint
CUI_P2_INC_EARN
decimal (11,0)
CUI_P2_TAX_PAID
int
CUI_P2_EDUC_CRED
int
CUI_P2_IRA_DIST
decimal (11,0)
CUI_P2_IRA_PYMTS
decimal (11,0)
CUI_P2_INTEREST
decimal (11,0)
CUI_P2_PENSIONS
decimal (11,0)
CUI_P2_SCHED_C
decimal (11,0)
CUI_P2_SCHED_A
char(1)
CUI_P2_SCHED_B
char(1)
CUI_P2_SCHED_D
char(1)
CUI_P2_SCHED_E
char(1)
CUI_P2_SCHED_F
char(1)
CUI_P2_SCHED_H
char(1)
CUI_P2_IRS_RESP
smallint
CUI_END_STRING
char(11)
SF_EVALUATION1
SYSTEM_KEY
int
YEAR_CODE
smallint
PJ_STD_FILE_STAT
char(1)
PJ_STD_WORK_INC
decimal (11,0)
PJ_STD_TAXES_PD
decimal (11,0)
PJ_STD_AGI
decimal (11,0)
PJ_STD_UNTAX_IRS
decimal (11,0)
PJ_STD_IRA_PMTS
decimal (11,0)
PJ_STD_EDUC_CRED
decimal (11,0)
PJ_STD_INTEREST
decimal (11,0)
PJ_STD_EXMPTS
decimal (11,0)
PJ_STD_SCHED_C
decimal (11,0)
PJ_STD_UNTAX_PENS
decimal (11,0)
PJ_STD_IRS_RESP
decimal (11,0)
PJ_SP_FILE_STAT
char(1)
PJ_SP_WORK_INC
decimal (11,0)
PJ_SP_TAXES_PD
decimal (11,0)
PJ_SP_AGI
decimal (11,0)
PJ_SP_UNTAX_IRS
decimal (11,0)
PJ_SP_IRA_PMTS
decimal (11,0)
PJ_SP_EDUC_CRED
decimal (11,0)
PJ_SP_INTEREST
decimal (11,0)
PJ_SP_EXMPTS
decimal (11,0)
PJ_SP_SCHED_C
decimal (11,0)
PJ_SP_UNTAX_PENS
decimal (11,0)
PJ_SP_IRS_RESP
decimal (11,0)
PJ_P1_FILE_STAT
char(1)
PJ_P1_WORK_INC
decimal (11,0)
PJ_P1_TAXES_PD
decimal (11,0)
PJ_P1_AGI
decimal (11,0)
PJ_P1_UNTAX_IRS
decimal (11,0)
PJ_P1_IRA_PMTS
decimal _NON(11,0)
PJ_P1_EDUC_CRED
decimal (11,0)
PJ_P1_INTEREST
decimal (11,0)
PJ_P1_EXMPTS
decimal (11,0)
PJ_P1_SCHED_C
decimal (11,0)
PJ_P1_UNTAX_PENS
decimal (11,0)
PJ_P1_IRS_RESP
decimal (11,0)
PJ_P2_FILE_STAT
char(1)
PJ_P2_WORK_INC
decimal (11,0)
PJ_P2_TAXES_PD
decimal (11,0)
PJ_P2_AGI
decimal (11,0)
PJ_P2_UNTAX_IRS
decimal (11,0)
PJ_P2_IRA_PMTS
decimal (11,0)
PJ_P2_EDUC_CRED
decimal (11,0)
PJ_P2_INTEREST
decimal (11,0)
PJ_P2_EXMPTS
decimal (11,0)
PJ_P2_SCHED_C
decimal (11,0)
PJ_P2_UNTAX_PENS
decimal (11,0)
PJ_P2_IRS_RESP
decimal (11,0)
Columns currently in SF_Evaluation and moving to SF_Evaluation1
