Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Hello FINAH Developers - The below fields are now available for you in UAT.  If you find an issue, please email busintel@ucsd.edu right away with the subject line “FINAH UAT due August 10” so we can address it prior to the Thursday, August 11, 2022 release to Production.

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

Table of Contents

Table of Contents


Thank You Report Developers!

Special thanks to the report developers who submitted enhancement requests. 

  • Cheryl Kettnich
  • Heather Sears
  • Eva Thiveos

Lived Name

As part of UCSD's transition to displaying Lived Name in all applicable tools, FINAH will display Lived Name starting in August 2022.  This means any report displaying employee Name fields will automatically display the employee Lived name where available and the Legal name where no Live name is indicated.  This will not break any reports or data integration objects, unless you are filtering for a specific name.

Epic:

Jira Legacy
serverITS PRO
serverIdebe8394f-6d75-344c-8d9c-717cb778a1eb
keyFINAHMAINT-935

SNOW ticket addressed: CS0989015

Ui expand
titleLived name is now available in the following views and column groups:
Views:
  • FINAH-Award-View
  • FINAH-ChartStringCombination-View
  • FINAH-Contract-View
  • FINAH-ContractRevenue-View
  • FINAH-PPMTransactionDetail-View
  • FINAH-Project-View
  • FINAH-ProjectCost-View
  • FINAH-ProjectPersonnelRole-View
  • FINAH-UCSDGeneralLedger-View
  • FINAH-UCSDGeneralLedgerBalances-View
  • FINAH-UCSDGeneralLedgerInterface-View

Column Groups:

  • FINAH Project Personnel Role Basic
  • FINAH Project Cost Accounting
  • FINAH Project Cost Accounting
  • FINAH Project Cost Accounting
  • FINAH Project Cost Award Project Mapping
  • FINAH Project Cost Budget Planning
  • FINAH Project Cost Budget Planning
  • FINAH Project Cost Budget Planning
  • FINAH Project Personnel Role Basic





Test 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.


Ui expand
titleProject Bill to Customer

Multiple Views

Epic:  

Jira Legacy
serverITS PRO
serverIdebe8394f-6d75-344c-8d9c-717cb778a1eb
keyFINAHMAINT-987

SNOW tickets addressed: CS0885436 and CS0692062
Added the following fields:

  • Project Bill To Customer
  • Project Bill To Customer Code
  • Project Bill To Customer Code And Name

To the following views:

  • FINAH-Project-View
  • FINAH-ChartStringCombination-View
  • FINAH-UCSDGeneralLedger-View
  • FINAH-UCSDGeneralLedgerBalances-View
  • FINAH-UCSDGeneralLedgerInterface-View



Ui expand
titleProject Bill to Customer & Task Bill to Customer

Multiple Views

Epic:  

Jira Legacy
serverITS PRO
serverIdebe8394f-6d75-344c-8d9c-717cb778a1eb
keyFINAHMAINT-989

SNOW tickets addressed: CS0885436 and CS0692062
Added the following fields:

  • Project Bill To Customer
  • Project Bill To Customer Code
  • Project Bill To Customer Code And Name
  • Task Bill To Customer
  • Task Bill To Customer Code
  • Task Bill To Customer Code And Name

To the following views:

  • FINAH-ContractRevenue-View
  • FINAH-ProjectCost-View



Ui expand
titleFINAH-PPM-TransactionDetail-View

FINAH-PPM-TransactionDetail-View

Epic:  

Jira Legacy
serverITS PRO
serverIdebe8394f-6d75-344c-8d9c-717cb778a1eb
keyFINAHMAINT-986

SNOW tickets addressed: CS0885436 and CS0692062
Added the following fields:

  • Project Bill To Customer
  • Project Bill To Customer Code
  • Project Bill To Customer Code And Name
  • Project Budget Period Budget Amount
  • Project Budget Period Funding Amount
  • Project Budget Period Unbudgeted Amount
  • Task Bill To Customer
  • Task Bill To Customer Code
  • Task Bill To Customer Code And Name
  • Transaction Source = Will be populated for "Transaction Type" 'Expenditure', 'Commitment', and 'Revenue'



Customer Service Reminder

Warning

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 Testing Steps

Tip
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 > Financial Activity Hub > Financial 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 Oracle 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 Oracle Production data.
  • Hana QA:  FINAH data in Hana QA is production Oracle 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?