/
202505 FINAH Release Notes

202505 FINAH Release Notes

Owned by Saparnell
Last updated: May 09, 2025

Hello FINAH Developers - The below enhancements are included in the this month's FINAH Release.

Keep up with our future enhancements here: FINAH Bugs and Enhancements In Progress.

Learn more about the Financial Activity Hub in the FINAH Quick Start Guides.

Table of Contents


Schedule for February

  • 8 Thursday, end of day: release enhancements to User Acceptance Testing

  • 15 Thursday, end of day: release enhancement to Production

  • 14 Friday, end of day: delete QA models

Schedule for 2025

  • BIA is hard at work preparing for TSS go live.  This wil take the efforts of all BIA team members and require the freeze on FINAH enhancements until post TSS go live.
  • Bug fixes will continue to be resolved, all other items will be prioritized to after TSS.


Thank You Report Developers!

Special thanks to the report developers who submitted enhancement requests. 

  • Heather Sears
  • Eva Thiveos


New Views

FINAH-ContractVersion-View

BIA and the BFS Reporting Team would like to introduce the FINAH-ContractVersion-View.  The current FINAH-Contract-View includes only the current status of the most recent version.  The new view includes all historical statuses of all contract versions and a new calculated field 'Contract Version Days In Status'.

This view will be part of the FINAH Core views and go to production in June 2025.

Epic: FINAHE-1891 - Getting issue details... STATUS

SNOW ticket(s) addressed: CS2335246

Fields unique to this view:

  • Contract Version Days In Status
  • Contract Version Status
  • Contract Version Status End Date
  • Contract Version Status End DateTime
  • Contract Version Status ID
  • Contract Version Status Start Date
  • Contract Version Status Start DateTime

FINAH-ProjectUnprocessedCost-View

BIA and the BFS Reporting Team would like to introduce the FINAH-ProjectUnprocessedCost-View.  This view will allow report developers to look into the unprocessed costs table.  Unprocessed costs are created when subledgers or users create PPM transactions that cannot post as written because a data element is missing (i.e. POETAF requires a funding source and none was given) or a project is not in Active status, or the expenditure date is outside the project/task start and end dates, etc.  The transactions post to an unprocessed costs table, which transaction creators must review, make corrections, and repost the costs.  When the unprocessed costs are processed, they are removed completely from the unprocessed costs table.  

This view will be part of the FINAH Core views and go to production in June 2025.

Epic: FINAHE-1893 - Getting issue details... STATUS

SNOW ticket(s) addressed: CS2325823

Fields unique to this view:

  • Credit Transaction Chartstring
  • Debit Transaction Chartstring
  • Unprocessed Cost Alert ID
  • Unprocessed Cost Alert Type
  • Unprocessed Cost Cleared Count
  • Unprocessed Cost Cleared Date
  • Unprocessed Cost Cleared Flag
  • Unprocessed Cost Message Text
  • Unprocessed Cost Posted Count
  • Unprocessed Cost Posted Flag
  • Unprocessed Cost Transaction ID
  • Unprocessed Cost User Details


Your Requested Enhancements

Items marked with an asterisk (*) are report breaking enhancements if you have these fields in your report and you have not take the appropriate remediation steps.

Fields AddedViews ImpactedJira EpicTickets Addressed
Accounting Period Foundation Last Closed Date
Accounting Period Foundation Opened Date
Accounting Period UCSD First Closed Date
Accounting Period UCSD First Opened Date
Accounting Period UCSD Last Closed Date		FINAH-ContractInvoiceDetail-View
FINAH-UCSDGeneralLedgerBalances-View
FINAH-UCSDGeneralLedgerInterface-View
FINAH-UCSDGeneralLedgerPeriod-View
FINAH-UCSDGeneralLedger-View		 FINAHE-1926 - Getting issue details... STATUS CS2343409
Award GAEL Expenses Allowed Count
Award GAEL Expenses Allowed Flag
Award In Temporary Extension Count
Award In Temporary Extension Flag
Award OFC KR Sponsor Discrepancy Count
Award OFC KR Sponsor Discrepancy Flag
Award Temporary Extension End Date
Award Temporary Extension Start Date
KR Award Flow Through Sponsor REMS Code
KR Award Sponsor REMS Code		FINAH-Award-View
FINAH-ChartStringCombination-View
FINAH-ContractInvoiceDetail-View
FINAH-ContractRevenue-View
FINAH-ContractVersion-View
FINAH-Contract-View
FINAH-PPM-Balances-View
FINAH-PPM-TransactionDetail-View
FINAH-ProjectCostAdjustment-View
FINAH-ProjectCosts-View
FINAH-ProjectPersonnelRole-View
FINAH-ProjectUnprocessedCost-View
FINAH-Project-View
FINAH-TE-ExpenseTransactionDetail-View
FINAH-TE-RequestDetail-View
FINAH-UCSDGeneralLedgerBalances-View
FINAH-UCSDGeneralLedgerInterface-View
FINAH-UCSDGeneralLedger-View		 FINAHE-1914 - Getting issue details... STATUS

CS2325823

CS2391770

CS2343811

Contract Line Incremental AmountFINAH-ContractInvoiceDetail-View FINAHE-1949 - Getting issue details... STATUS CS2428952
Expenditure Type High Risk Flag
Expenditure Type High Risk Count		FINAH-ProjectCostAdjustment-View
FINAH-ProjectCosts-View
FINAH-TE-ExpenseTransactionDetail-View
FINAH-TE-RequestDetail-View		 FINAHE-1909 - Getting issue details... STATUS

CS2354803

CSTASK0039846

Expenditure Type High Risk Flag
Expenditure Type High Risk Count		FINAH-PPM-TransactionDetail-View FINAHE-1907 - Getting issue details... STATUS CS2354803


UAT - Customer Service Reminder

Data in UAT is not ready to be shared with end customers, is not considered completely validated and can change suddenly.  For optimal customer satisfaction, do not connect your production solutions to packages / data sources that are in UAT.  If you choose to share UAT items with end customer, be explicit that the data and report is in UAT and can change suddenly or be broken by UAT changes.

Follow our Enhancement User Acceptance Testing (UAT) Steps

Use this UAT time to adjust your reports as needed prior to the Production release where your customers will be able to see any issues these enhancements cause. 
  • Cognos: Use the packages in Cognos DEV > Student Activity Hub > Student Activity Hub Packages UAT to build your report and select Hana QA.  Do not select Hana Prod as the report will fail.  Using Hana QA will allow you to see the below enhancements with Production data. 
  • Tableau: Sign into Tableau on your Tableau desktop tool and open your report.  Add a new data source with the same name and -QA at the end of the title.  Using this data source will allow you to see the below enhancements with Production data.
  • Hana QA:  SAH data in Hana QA is production data loaded daily, just like in Hana PROD.

If you find an issue, please include in your email to busintel@ucsd.edu the following:

  • What browser are you using?
  • What environment are you using?  Cognos DEV, QA or PROD?  Or Tableau?
  • What data source / package are you using?
  • What results were you expecting? 

Reminder: QA data sources will be deleted the Friday after the enhancements are migrated to Production.